Illustrative reference signals only. Not live settlement or regulated dispatch.
REFERENCE INDEX€8.1425
REFERENCE LATENCY42ms
REFERENCE INDEX€8.1425
REFERENCE LATENCY42ms
Contact

Contact CitizenSolar

CitizenSolar uses a simple, static-site contact model: prepare a direct inquiry for pilot, partner, technical, Labs, or general contact without pretending there is backend CRM automation where none exists.

Contact Routing

Use the contact surface to route inquiries cleanly, then continue into pilot, partner, standards, or resource pages as needed.

Use the current contact path for pilot discussions, partner conversations, technical interoperability questions, Labs and research outreach, or general release inquiries.

Pilot inquiry
Partner inquiry
Technical and interoperability inquiry
Labs and research inquiry
General contact

Best For

Pilot, partner, finance-fit, orchestration-partnership, technical, orchestration-readiness, research, and general public inquiries.

Default Flow

Start in the Site Guide, then switch to the inquiry form only when the discussion becomes concrete.

Output

This route prepares a structured email draft rather than submitting to a live backend service.

Guided Inquiry

Site Guide And Inquiry

Start with the site guide for route guidance, product and solution context, and scope-aware next steps. Use the Inquiry Form when you want to prepare a structured pilot, partner, finance-fit, technical, research, or general email draft.

Guided Conversation

The assistant stays inside the current site scope: navigation, product and solution context, pilot path, trust posture, and current-release maturity framing.

Suggested Prompts

Prompt Set: Contact

CitizenSolar Guide

I can help you navigate the current CitizenSolar release from the Contact surface. Ask about products, solutions, Storage Bank, Community Energy Bank, pilot options, trust posture, or the difference between commercial and Labs.

Site-grounded guide only. Press Enter to send. Move into the Inquiry Form for deployment-specific commercial, partner, technical, or Labs questions.

Recommended Routes

Contact

Contact and inquiry entry point with pilot, partner, technical, and Labs pathways.

/contact

Pilot Program

Pilot phases, archetypes, deliverables, and next-step engagement model.

/pilot-program

Partners

Partner categories, rollout models, and collaboration paths.

/partners

Resources

Architecture, standards, security, privacy, FAQs, and public product briefs.

/resources

Scope Discipline

The assistant is grounded in the current public CitizenSolar release. It explains the live site structure, maturity framing, products, solutions, partner paths, trust posture, and pilot routes. It does not claim undocumented market operation, certification, or Labs features as commercial products.

Next Action

Use the quick prompts for a fast start, or ask a direct question and I will point you to the best route and next step.

Inquiry Paths

The public release prepares a direct email draft from a browser-based contact flow. That is the intended working model for a static site until a documented intake system exists.

Pilot requests should include site, region, deployment scope, and timing
Partner requests should identify counterpart type and objective
Technical requests should list systems, interfaces, and questions
Labs requests should stay separate from commercial-now deployment language

Response And Scope

This release does not promise CRM automation, guaranteed SLAs, or fully staffed support operations. It presents a clear inquiry route and expects operators to maintain the configured inboxes and response process.

Keep contact mailbox targets current before deployment
Treat security issues as private disclosure first
Use the public route for commercial and informational requests only
Document future intake automation before claiming it publicly