PLANNING GUIDE · SNAPSHOT COMING SOON
Solar Lead Engine
A solar lead system should give the sales team enough project context to arrange a useful conversation. Separate a new inquiry from a confirmed consultation, a site assessment and an actual proposal.
Review the setup checklist →Plan the build before choosing the assets
This snapshot is planned and has not been built yet. Use this guide to decide which intake fields, routing rules, booking paths and follow-up your business needs. The diagrams and checklists describe a proposed system.
Proposed customer journey
- 01Capture property location and project interest
- 02Review coverage and project context
- 03Assign a consultation owner
- 04Confirm the consultation or assessment
- 05Record the proposal decision and stop obsolete follow-up
Components to review before setup
Use this checklist to compare the installed build with your requirements. These are proposed components to consider for your build.
| Component | Proposed role | Configuration to verify |
|---|---|---|
| Project intake | Property location, project interest, ownership or decision-maker context and contact preference | Document required fields and send incomplete requests to human review. |
| Sales handoff | A named owner, intake summary and next action | Set assignment rules and a fallback when the primary owner is unavailable. |
| Consultation calendar | Availability and appointment-type selection | Separate consultation, site assessment and installation scheduling. |
| Proposal follow-up | Reminders tied to a proposal that was actually sent | Require a proposal status and stop on acceptance, decline or a request to pause. |
| CRM stages | Inquiry, reviewed, consultation confirmed, proposal sent and decision | Define which team member or verified integration owns each transition. |
Setup checklist
- Capture the source snapshot version and its actual asset inventory before migration or installation changes.
- Define supported service areas and which project types the team accepts.
- Map project fields and callback preferences to the contact record.
- Assign consultation owners and connect the correct calendar for each appointment type.
- Define the signal that means a proposal was sent; do not start reminders from an inquiry alone.
- Review copy so it does not promise savings, eligibility, incentives or financing approval without a verified basis.
- Run the acceptance checks with synthetic contacts before activating live delivery.
Acceptance checks before launch
Use these checks when your system is built. Test with synthetic contacts before connecting live channels, and record whether each expected outcome occurs.
| Test case | Expected outcome |
|---|---|
| Complete new inquiry | A single opportunity reaches an owner with the supplied project context. |
| Incomplete or out-of-area inquiry | The request reaches review; no eligibility or appointment guarantee is sent. |
| Consultation rescheduled | The old reminders stop and the new time is reflected in the record. |
| Proposal not yet sent | Proposal follow-up remains inactive. |
| Proposal accepted or declined | Decision-specific handling replaces generic proposal reminders. |
| Contact asks to pause or opts out | The affected follow-up stops and the preference is recorded. |
When is this ready for a client?
Only after the installed inventory is verified, required integrations are connected, business-specific settings are configured, and every critical customer path has a recorded passing test. Keep evidence of branches, cancellation behavior, opt-outs and human handoffs alongside the setup notes.
Read the industry intake guide →
Review HighLevel-to-Votel migration planning →
Editorial guide reviewed September 19, 2026 by All Things Votel. Snapshot status: planned build; not yet available.