Enquiries and pipeline
A solar CRM that follows the enquiry all the way to the job.
Capture every enquiry with the details a solar sale depends on, assign it, log every call, and know exactly who follows up next. When the customer says yes, the enquiry carries its history straight into survey, quotation and delivery.
What does the enquiries module do? It holds every solar enquiry in one pipeline with roof, bill and project details, an owner, a next follow-up date and a full call and activity history, so no lead depends on one person’s phone or memory.
- SalesFirst callConnected · monthly bill and roof type noted
- SurveyorSite survey bookedSite engineer assigned
- Sales headProposal discussionCustomer asked for a call back
- ProjectsWon and convertedHistory moves to the customer and project
From first call to won job
Four steps, one record.
The same enquiry record is used by sales, the site engineer and the project team. Nothing is re-entered when it moves on.
Capture
Record the customer, city, monthly electricity bill, roof area and type, property type and whether the job is on-grid, off-grid, hybrid or micro-inverter. Note if subsidy or a bank loan is needed.
Qualify and follow up
Move the enquiry through solar-specific statuses, set priority, and schedule the next follow-up. Every call and note stays on the record.
Survey and quote
Assign a site engineer from the enquiry. The survey and the priced quotation attach to the same record.
Convert
When the customer commits, the enquiry converts to a customer and a project. Calls, notes, documents and the survey carry across.
What it does
Built for how solar enquiries are actually worked.
A pipeline made for solar
Eighteen built-in statuses cover the real journey, from contacted and site survey to feasibility, proposal, committed and won, plus cold, on hold, not feasible and existing solar.
- Priority and lead score
- Residential and commercial types
Duplicate protection
Phone numbers are normalised and matched on entry and on import. A user with permission can override a match, and the reason is saved on the enquiry.
- Alternate phone numbers
- Override reason recorded
Bulk import with preview
Upload a sheet from a campaign, an expo or a partner. Review every row before saving, then group the result as a list by source.
- Ready, invalid and duplicate rows flagged
- Lists by source and default manager
Assignment and collaboration
Give each enquiry an owner, a manager and a site engineer. Add colleagues as collaborators with view, work or manage access.
- Bulk assignment
- Managed by a person or a role
Call and WhatsApp logging
Call or message from a shared phonebook and record the outcome. The log keeps the status before and after, and the next follow-up date.
- Connected, busy, wrong number, call back later
- Recordings attached to the enquiry
Internal follow-up requests
Ask a colleague to act on an enquiry with a reason, a priority and a note. They respond on the same record, so nothing is lost in chat.
- Request, response and clarification
- Notes, email and meeting history
Clean data from day one
Import a whole campaign without importing the duplicates.
Expo sheets, campaign lists and partner files arrive messy. HelioLattice shows what will happen to each row before anything is saved, so your pipeline stays clean and your team does not call the same customer twice.
- Preview every row before the import runs
- Duplicates inside the file and against existing enquiries are flagged
- Each import becomes a list tagged by source
- A default manager can be set for the whole list
Example preview with illustrative rows.
Referrals
Every referral reviewed before it reaches the pipeline.
Channel partners and your own staff can submit referrals. Your team reviews each one, checks it for duplicates, declines it with a reason or converts it into an enquiry. A partner can see where each of their referrals stands.
- Referral numbers and a clear review status
- Duplicate check before conversion
- Decline reason and manager notes saved
- Commission status tracked for each referral
Example flow with illustrative entries.
Who uses it
Each person sees the enquiries that are theirs.
Permissions and data scopes decide who can create, assign, view or convert an enquiry. A sales executive can be limited to their own enquiries while a sales head sees the whole team. See how access control works.
Sales executive
Works assigned enquiries, logs calls and sets follow-ups.
Sales head
Assigns in bulk and keeps every enquiry moving.
Site engineer
Sees booked surveys and records them against the enquiry.
Owner
Reads pipeline and source reports across the whole team.
Questions
About enquiries and the pipeline.
What is a solar CRM?
How does HelioLattice stop duplicate enquiries?
Can we import enquiries from a campaign, an expo or a spreadsheet?
How are enquiries assigned to the sales team?
Does it log calls and WhatsApp conversations?
Can channel partners send us enquiries?
See your own enquiries in the pipeline.
Bring a recent expo sheet or a list of open enquiries and we will show how they are imported, assigned and followed up.