Solar workflow · Intake and estimate
Solar Lead Response Automation for Consults, Quotes, and Follow-Up
Move a solar inquiry toward a truthful next step: a site assessment, a design consult, an installation estimate, or a clear scope answer without promising energy or savings outcomes.
Quick answer
Respond with a useful next step, not a generic acknowledgement.
Solar lead response automation should preserve the customer’s description, establish the property, utility, and service-area context, separate immediate property-safety language from routine sales qualification, and route the record to a designer, estimator, installation coordinator, or clear decline. It should never promise a specific energy bill, payback, production figure, utility approval, or incentive amount, quote an unapproved price, or imply that an installation was scheduled before the authoritative people and process confirm it.
01 · Customer journey
Design around the request the customer is trying to complete
A solar customer may be comparing options, checking roof suitability, asking about financing, or preparing for installation. The journey is considered and consultative rather than urgent. The intake path should collect useful property, utility, and timing context without making promises about production, bill savings, payback, or incentives that only a qualified review and verified data can support.
1. Preserve what the customer observes
Capture the customer’s own description: interest in solar, roof type and age if known, shading, orientation, recent utility use, financing interest, or a question about installation. Ask whether there are active roof issues or safety concerns, but do not assess the roof, electrical system, utility agreement, or incentive eligibility.
2. Establish property and service fit
Confirm the service address, property type, homeownership or authorized-request status, roof and electrical context if known, utility provider if known, and whether the business serves that location and scope. Ask only questions that change routing.
3. Choose the next operational action
A consultation may enter a design-review path, a quote request may enter an estimator path, and an existing or new installation may enter a coordination path. The workflow should expose expectations only when policy and capacity support them. Utility, permit, and incentive questions require careful human handling.
4. Keep continuity through the sale
Record every promise and state change: received, duplicate merged, human accepted, consult requested, assessor scheduled, design review, estimate prepared, contract signed, install scheduled, completed, declined, or unresolved. Follow-up stops or changes when the customer replies, asks for a person, opts out, or reaches an owned next step.
02 · Workflow contract
Give every stage an action, evidence, and exception path
Solar sales are consultative, data-heavy, and longer-running. A durable workflow collects durable lead context, separates observable facts from projections, applies service and policy rules, and keeps ownership visible across a longer cycle. Production, savings, payback, incentives, and approval promises stay with qualified people and verified sources of truth.
| Stage | Required action | Evidence retained | Exception path |
|---|---|---|---|
| 1. Capture | Receive the form, call summary, email, message, or ad lead and claim one durable intake record. | Source, receipt time, address, customer wording, attachments, deduplication key. | Merge likely duplicates for review without losing the original messages or sending repeated acknowledgements. |
| 2. Property and safety screen | Check reviewed phrases for active roof damage, leaks, electrical concerns, or unsafe access. | Exact phrase, policy version, approved message, escalation route. | Stop ordinary sales questions and route property or safety concerns to the appropriate qualified review. |
| 3. Fit and request class | Confirm service area, property type, ownership or authorization, roof and electrical context, utility context, and existing-customer state. | Address result, customer-supplied facts, request class, unknowns, match reason. | Route boundary addresses, unsupported properties, and uncertain identity to review. |
| 4. Next action | Select an approved acknowledgement, design consult, estimator review, site assessment request, or clear decline. | Decision reason, owner or queue, requested timing, message version, promised update. | Do not claim booked status, production, savings, or incentives without authoritative confirmation. |
| 5. Human acceptance | Require the designer, estimator, or sales coordinator to accept the record and its unresolved questions. | Owner, acknowledgement time, fallback, contact attempt, next customer update. | Escalate unattended records and suppress competing follow-up once a person owns the conversation. |
| 6. Outcome and follow-up | Update the record from consult, design review, estimate, signed agreement, scheduled install, completed, declined, or unresolved. | Verified state, timestamps, correction reason, source attribution, final stop state. | Keep estimates, signed agreements, and completed installs separate. Never infer a sale or production from an inquiry. |
03 · Human handoff
A notification is not ownership
The estimator or designer should receive one coherent record even when the customer called, submitted a form, and sent photos. The packet should show the original wording, address and service-area result, property and roof context, utility and ownership context, attachments, existing-customer match, messages already sent, preferred timing, the route reason, and the exact expectation set with the customer. The record becomes owned only when a person or governed queue accepts it.
Observed facts
Customer wording, address, property type, roof, shading, electrical, and utility context supplied, safe attachments, source, contact preference, and known timing.
Workflow decision
Service-area result, request class, unresolved question, assumptions avoided, and messages already sent.
Consult ownership
Designer, estimator, or coordinator, acknowledgement target, fallback, requested timing, scheduling state, promised update, and follow-up stop condition.
04 · Guardrails
Write stop conditions before message templates
Solar intake sits near energy projections, financing, incentives, permits, and high-value contracts. Automation should organize evidence and reduce duplicate work, not act as a designer, engineer, utility, financier, or incentive adviser. Every route needs an authority limit, and every customer-facing promise needs a verified source of truth.
- Never promise a specific production figure, bill reduction, payback period, utility outcome, incentive, or financing result from intake text or photos. Keep such statements with qualified review and verified data.
- Never assess roof condition, electrical capacity, or installation feasibility from intake text or photos. Preserve the customer’s information and route it to a qualified person.
- Never claim a quote, agreement, permit, or installation is scheduled without an authoritative person and process confirming it.
- Never imply that photos or a utility estimate replace an on-site site assessment where one is required by company policy.
- Honor opt-outs and requests for a person across every channel. Stop scheduled prompts when a coordinator accepts the lead or the customer clearly closes the request.
- Test duplicate inquiries, service-area boundaries, property type exclusions, scheduling failures, and owner fallback before launch.
05 · Measurement
Measure ownership and verified progress
A solar workflow should be evaluated on accountable progress from inquiry to a verified consult, estimate, signed agreement, or clear resolution. Message volume and form completion do not show whether the customer received useful help. Keep consult requested, consult completed, design review, estimate prepared, agreement signed, install scheduled, install completed, declined, and closed states distinct, then review the path by source, request class, service area, and owner.
| Metric | Definition | Decision supported |
|---|---|---|
| Receipt to useful action | Time from verified intake to an approved acknowledgement or accepted human owner. | Does the customer know what happens next without receiving a false promise? |
| Duplicate consolidation | Repeated contacts linked to one reviewable lead without losing source evidence. | Is outreach creating duplicate work or conflicting messages? |
| Context completion | Records with enough customer-supplied property, utility, and timing facts to route the next consult. | Are questions supporting routing rather than delaying response? |
| Owner acknowledgement | Time until a designer, estimator, or governed queue accepts responsibility. | Do alerts become accountable consult work? |
| Verified consult and estimate state | Consult requested, completed, estimate prepared, agreement signed, install scheduled, installed, or cancelled as separate events. | Where does the longer sale cycle lose continuity? |
| Exception and correction rate | Blocked promises, route corrections, delivery failures, unsupported property types, and unresolved ownership. | Which policy, capacity, or integration needs attention? |
Missed-lead revenue
See what a slow response costs your Solar business.
Estimate the revenue leaking from unanswered and slow-to-answer Solar inquiries, then decide where a faster workflow is worth it.
Verified sources
Use authoritative service context without inventing outcomes
The sources below provide neutral U.S. Department of Energy context on solar technologies and research. They do not verify a specific property, production figure, incentive, or payback and do not support revenue claims for Inqari. Use them to ground accurate technology language, then rely on qualified local professionals for design, engineering, financing, permits, and incentives.
More industries
Related lead response workflows
Every trade and practice qualifies leads differently. These related workflows share the same intake, routing, and human-handoff foundations as solar.
Continue the workflow
Related Inqari guides
FAQ
Solar lead response automation questions
Can solar lead response automation book consultations?
It can request or confirm a consult only when it uses an authoritative scheduling source and approved rules. If availability is not authoritative, collect preferred timing and route it to a coordinator without presenting an unconfirmed slot as booked.
Can the workflow estimate energy savings or production?
No. It should not promise a specific bill, production, payback, or incentive amount. Those belong to a qualified review with verified system design, roof, utility, and incentive data.
What should a solar inquiry ask before handoff?
Ask only what changes the next action: service address, property type, ownership or authorization, roof and electrical context if known, utility context if known, financing interest, timing, and contact preference. Keep unknown details unknown.
Does Inqari replace solar CRM or quoting software?
No replacement is assumed. Inqari focuses on intake, qualification, routing, follow-up, and evidence before syncing an approved record or task into the tools the business already uses.
How should roof or electrical safety language be handled?
Use the business’s approved message and route to a qualified review. The workflow must never assess the roof or electrical system from intake text or photos or promise a feasibility outcome.
Map the real workflow
Turn the next solar inquiry into an owned consult and estimate decision.
Inqari maps your channels, service-area rules, property and utility context, consult handoff, scheduling source, follow-up, and measurement before proposing automation.
Request a lead audit