A useful solar handoff gives the adviser a starting point: why the homeowner enquired, what they have already answered and whether they want to talk now. The homeowner should not have to repeat the conversation when the adviser picks up.

That is the job we designed an AI voice agent for solar to do. This article walks through our tested installer qualifier and the rollout improvements we recommend. The design has not been rolled out on real enquiries.

What this workflow is based on

We have built outbound home-energy follow-up and tested a separate solar-installer qualifier. The useful lesson across both is the handoff: establish why the person enquired, collect the few details an adviser needs and pass the conversation on with its context intact.

For a rollout, the callback process and reporting need the same attention as the qualification questions.

The practical lessons behind it

A greeting needs reliable lead data. An empty calendar needs a callback route. And an unanswered adviser line needs a fallback, rather than leaving a homeowner waiting. Those are the details that turn a promising voice demo into a usable follow-up system.

The solar-installer qualification flow

For a New Jersey installer, we designed and tested an enquiry qualifier around the questions that determine a useful adviser conversation. The diagram also labels the recommended route for a missing or unclear bill answer.

Wrong number ordo-not-callVoicemailYesBad timeNot interestedYesRenterYesExplicit yesYesNoNo or unclearDial and ask: isthis the namedperson?Right person?Apologise andendHang upSay it is an AIand why it iscallingGood time totalk?Record acallback requestEnd politelyHomeowner?Not eligible: endthe callElectricity billover the cut-off?Warm transferwith a spokenbriefAdviserreached?Record thetransferRecommended:record theanswer and offera callback or slot
Flow 1: The solar-installer qualification flow. A numbered text explanation follows.
  1. The agent asks "is this" the named person first. A wrong number or a do-not-call request ends the call with an apology. Nothing else is asked.
  2. It says it is an AI and why it is calling. A bad time becomes a callback request. "Not interested" ends the call.
  3. It asks whether the person owns the home. In the tested flow a renter is not eligible and the call ends. That is how this flow treats renters; your own business rules decide.
  4. It asks whether the electricity bill is over about $100. That cut-off belongs to the tested flow. Yours should be set with your own team.
  5. Only an explicit yes to the bill question triggers a warm transfer in the tested design, with a short spoken brief for the adviser. For a rollout, also confirm that the person wants to speak now. If the transfer fails, the tested design promises a callback; that promise needs a staff task behind it.
  6. On voicemail it hangs up without leaving a message.

After each call the tested flow stored four fields: eligibility, transfer, callback and do-not-call. Its bill check specified the route for an explicit yes. We recommend recording any clear no accurately, leaving uncertainty unknown and offering an appropriate next step instead of forcing either answer into a transfer.

Let the person's intention control the next step

Illustrative example — not a client transcript.

AI assistant: I'm the installer's AI assistant, calling about your recent enquiry. Is now a good time for two quick questions?

Prospect: I own the house, but I don't have my bill in front of me.

AI assistant: That's fine. I'll note the bill as unknown. Would you rather arrange a time with an adviser, or have someone call you back?

The useful facts are that the person owns the home and wants a later conversation. Inventing a bill figure to fill a field would make the record worse. Pushing a live transfer would ignore what they said. An approximate bill stays approximate, and neither answer entitles the agent to promise a price or suitability. The adviser owns those conversations.

Give an unanswered transfer a clear next step

A transfer request can go out without anyone answering. Agree a primary destination, suitable backups and a point at which the agent stops trying. If no one answers, save a callback request to a named team with the context collected so far. Only promise a callback the team has agreed to fulfil.

During office hours, a person who wants to talk now can be offered the transfer chain. After hours, we recommend the agent checks the consultation calendar or records a callback request. Either way, the schedule should follow the business's own time zone and opening hours.

Report outcomes separately

"Transferred" hides several outcomes. We recommend reporting them apart:

Outcome What it establishes
Transfer attempted The system tried the handoff
Transfer answered There is evidence a person received the call
Qualification completed The needed information was actually collected
Appointment booked The calendar confirmed a booking
Callback requested Follow-up now sits with a named team

If the system cannot tell whether a human answered, the record should say the answer status is unknown.

A useful acceptance check deliberately makes every adviser unavailable. The call should follow the agreed fallback, explain the next step and leave staff a task with the context attached. The report should record the callback request accurately.

Where this workflow fits

This workflow fits an installer that wants a more consistent first conversation and a better-prepared adviser handoff. It needs a named team behind the transfer and a clear owner for callbacks. Installation advice, suitability and the sale remain with the solar team.

Bring your qualification questions and adviser availability to Custom Voice Agent. We'll map a first call your solar team can continue.