Solar lead response: give each enquiry a clear next step

What should happen when the lead arrives?

• Search for an existing customer before adding another record.
• Retain the source, original enquiry time, requested system and preferred contact channel.
• Assign the owner for the actual opportunity and record the next action.
• Check contact permission and the applicable calling window before outreach.

Sources: [1][4]

How should you handle a SolarQuotes enquiry?

SolarQuotes describes matching customers with up to three installers and delivering leads by API, email or SMS. Preserve the supplied requirements and source reference. An API delivery option does not establish that your particular CRM connection is configured.

In ArcSolar, customer records connect the source and owner with calls, quotes and delivery history. Verify the saved record and assignment before the rep starts follow-up.

Sources: [5][1][2]

Example: three different response clocks

Illustrative enquiry: received at 9:00 am, saved at 9:03, assigned at 9:04, first call attempted at 9:10 and a conversation started at 9:18. First-attempt response is 10 minutes; two-way contact is 18 minutes. A receipt at 9:03 does not make either result three minutes.

Sources: [2][3]

What does a fast response prove?

It proves a contact event, not a sale. Keep failed calls, sent messages, delivered messages and customer replies distinct. Review unowned enquiries and after-hours work as separate groups; an average can hide a queue that nobody is working.

Sources: [2][1]

Follow one enquiry through the customer record

Use a fictional lead to inspect its source, owner, conversation and next task in an ArcSolar demo. Agree the response standard your team can actually staff.

• Assign leads without losing accountability →
• Review useful quote SMS templates →