An AI phone agent for the calls your solar company cannot take from a roof

A solar company's phone rings hardest when nobody can answer it. Prospects call during working hours — exactly when the owner is bidding a job and the crew is on a roof. Customers mid-project call for status the moment their permit sits in review or their utility interconnection stalls. Installed customers call when the monitoring app shows a fault code at 7 p.m. on a Sunday. Every one of those calls matters, and most solar operations are structurally unable to pick them up.

ThunderPhone gives a solar installer an AI phone agent that works in both directions: inbound coverage for the leads, status calls, and service reports you receive, and outbound campaigns for the calls your team never has time to place — survey confirmations, project-status updates, install-day reminders, post-installation check-ins. Outbound calling on ThunderPhone is built for your own customers and your own consented leads; it is not a cold-calling tool, and this page does not describe one.

The agent does not give electrical or roofing advice, quote savings, or promise incentives. You define what it may say, what it must collect, and when it must escalate — qualification questions, status scripts, and service triage rules come from the company, and the agent executes them exactly.

What a solar phone agent can handle

Answering the lead that calls while you are on a roof

Speed matters most on the first call, and the first call almost always arrives when the team physically cannot answer. The agent picks up every inbound inquiry immediately — during install hours, over lunch, after hours, on weekends — greets the caller in your company's voice, answers approved questions about your services and process, and moves straight into your intake script. A prospect who would have hit voicemail instead gets a real conversation and a booked next step; your team gets a structured record instead of a missed-call log.

Lead qualification intake — your questions, collected not judged

Solar qualification follows a script your sales team already knows: is the caller the homeowner, what type of property, what is the address and utility provider, roughly what does the monthly electric bill run, what is the roof like, what is the decision timeline, any interest in battery backup. Those are examples — the agent asks whatever questions you configure, conversationally, and records the answers as a structured lead that lands in your CRM by webhook or API. It collects; your sales team judges. A caller whose answers fall outside the script gets a transfer or a scheduled callback, never a guess about whether their home "qualifies."

Site-survey scheduling and prep confirmations

The site survey is the first physical commitment in the pipeline, and a missed one wastes a truck roll. The agent can offer survey slots from a connected calendar and book on the first call, then an outbound campaign can confirm each visit the day before: the date, the arrival window, who is coming, and your prep instructions — a recent utility bill handy, access cleared to the attic and the main electrical panel. A caller whose time no longer works can reschedule on the spot, and every outcome — confirmed, rescheduled, unreachable — is delivered to your systems by webhook before the surveyor loads the van.

Project-status calls in both directions

Between contract signing and permission to operate, a solar project passes through design, permit review, installation, inspection, and utility interconnection — and much of that timeline sits with the permitting authority and the utility, not with you. That is exactly when customers start calling. Inbound, when the agent is connected to a system that exposes project status, it can look up the caller's project mid-call and give a real answer — where the project is, what stage comes next — from the data your system returns, instead of taking a message. Outbound, a campaign can proactively call your active customers at the milestones you choose: permit approved, inspection scheduled, interconnection submitted, PTO granted. Proactive status calls to your own project customers are an inexpensive way to stop the "any update?" calls before they start.

Installation-day coordination

Install day involves the customer, the crew, and sometimes an inspector, and one missed handshake can idle a crew for a morning. A day-before confirmation call can verify the homeowner will be available, repeat the arrival window and your prep instructions — vehicles out of the driveway, pets secured, panel access clear — and capture a conflict early enough to refill the slot. Day-of, a configured outbound call can deliver a delay or arrival update from your dispatcher without pulling anyone off a ladder.

Post-PTO onboarding, check-ins, and review requests

After permission to operate, the relationship goes quiet by default — and quiet is where referral business dies. Outbound campaigns to your own installed customers can walk through system onboarding (how to read the monitoring app, what to expect in the first billing cycle, whom to call about what), place a check-in call after the first month, and — where your customer relationship and local rules permit — invite a review or referral using your script. These are your customers, your list, your cadence; the agent simply never gets tired of the polite follow-through.

Service, monitoring, and warranty intake

Post-install phone work clusters around a handful of patterns: the homeowner whose app shows zero production, the inverter fault code, the panel-cleaning request, the warranty claim. The agent runs your service-intake script — what the customer sees, when it started, which error message or indicator appears — and creates a structured, timestamped ticket your operations team can triage before rolling a truck. You decide the red flags: reports your script flags as urgent — for example, a burning smell, visible sparking, or a tripped main breaker, if those are on your list — skip the queue and follow your configured escalation path immediately. Because every report becomes a documented record, the paper trail that warranty claims and maintenance obligations depend on builds itself.

Waiting on hold so your coordinator does not have to

Some of a solar office's worst phone hours are spent on the other side's automation — a utility interconnection line, a permitting office, a distributor. On calls your team configures, the agent can navigate keypad menus and wait on hold at a flat reduced rate, then hand off to your coordinator when a human picks up.

Multilingual homeowner communication

ThunderPhone supports 47 voice languages. Set a primary language and additional languages for your market, and the agent can switch mid-call when a caller changes to one of the selected languages — the same qualification, status, and escalation rules in every configured language, with a transcript of every call for the team to review.

After-hours and overflow capture

After hours is when a phone agent earns its keep, because the alternative is voicemail. An evening prospect gets qualified and booked instead of lost; a weekend service report gets a structured ticket and, if it trips your red-flag list, your on-call escalation path. During the day, the same agent takes overflow when the office line is busy, so the coordinator returns to a clean queue instead of a message light.

Sample solar call flow

Agent: Thank you for calling Meridian Solar. Are you calling about getting solar for your home, an existing project, or service on an installed system?

Caller: We just moved in and our electric bill is huge. I want to see if solar makes sense.

Agent: Happy to help with that. Are you the homeowner, and is this a single-family house?

Caller: Yes and yes.

Agent: Great. Roughly what does your monthly electric bill run, and who is your utility provider?

Caller: Around $280 a month, with Valley Power.

Agent: Thank you. The next step is a free site survey — one of our surveyors looks at the roof, attic, and electrical panel. I have Thursday at 10 a.m. or Friday at 2 p.m. available. Would either work?

Caller: Friday at 2.

Agent: You're booked for Friday at 2 p.m. Please have a recent utility bill handy and clear access to your attic and main electrical panel. Our team will confirm the day before.

If the caller asks what the system would cost or save, the agent gives only the company's approved answer — typically that pricing follows the survey — and never improvises an estimate. A service caller reporting anything on the company's urgent list is escalated on the configured path instead of booked.

Features that matter in a solar company

CRM and project-system connections

Agents can use connected apps, HTTP APIs, or MCP tools during a call — create a lead, book a survey slot, look up project status, or file a service ticket when the receiving system exposes the action. Webhook deliveries are HMAC-signed and retried automatically, so a briefly unavailable endpoint does not lose a lead.

Knowledge grounded in your documents

Attach your process explainer, service-area list, financing-options overview, warranty terms, and FAQ — as text or PDF/DOCX uploads (up to 5 MB per text file and 50 MB per PDF or DOCX), or imported directly from a page on your website. The agent searches those documents mid-call instead of relying on a generic answer, and each agent uses only the documents you scope to it.

Your numbers, your telephony

Bring your company's existing numbers through a supported VoIP connection or SIP configuration; verified numbers handle inbound and outbound calling. A web voice widget can put the same agent on your website, so a visitor comparing installers can ask a question by voice without dialing.

Human handoff

Cold transfers are available for immediate routing. Warm transfers are available on eligible production VoIP or SIP numbers that can place an outbound leg: the caller waits while the agent privately briefs your closer or on-call tech, then connects only if the recipient accepts — the right shape for a hot lead or an urgent service report.

Compliance posture

ThunderPhone's public compliance posture is GDPR and HIPAA compliant. Your company still controls the workflow: limit the agent to necessary information, attach only approved documents, choose recording and disclosure settings deliberately for your jurisdictions, and define where call data may be sent.

Testing before homeowners hear it

Use a browser mic test for quick iteration, then run AI-caller simulations for the scenarios that worry you: a price-shopping prospect pushing for a number, an angry where-is-my-PTO call, a service report that should trip the urgent path, a renter asking about panels. Simulations create transcripts and grading so the team can tighten the prompt before deployment, and graded scenarios can be kept as a regression suite so a prompt change never quietly breaks the escalation script. When two scripts seem equally good, an A/B experiment on live traffic settles it. Every production call leaves a transcript, and a recording when recording is enabled.

Guardrails the company controls

• Outbound compliance is yours. Solar calling is heavily regulated and heavily enforced. ThunderPhone campaigns call the list you load with the script you approve; your company is responsible for consent, calling-hour restrictions, and do-not-call compliance in its campaigns — including honoring revocations. Use it for your own customers and your own consented leads, never cold outreach or purchased lead lists.
• No technical or sales improvisation. The agent does not give electrical advice, estimate production, quote prices, or promise incentives or tax outcomes. Approved answers come from the prompt and scoped knowledge base; anything unanswered routes to a person.
• Qualification is intake, not judgment. The agent collects the answers to your questions; your sales team decides what qualifies.
• Escalation is configured, not improvised. Urgent-service triggers, transfer targets, and after-hours paths are set by the company and exercised in simulation before launch.

What would this cost each month?

Suppose a solar company handles 1,000 AI-assisted calls per month, averaging 4 minutes each:

1,000 calls × 4 minutes = 4,000 minutes per month

• Spark: 4,000 × $0.02 = $80/month
• Bolt: 4,000 × $0.05 = $200/month
• Storm: 4,000 × $0.09 = $360/month

That is illustrative base engine usage, not a quote — pay as you go, with no subscription. Premium voice or language paths can add up to 3¢ per minute, and phone-number or carrier charges depend on the telephony setup. Hold time bills a flat 2¢ per minute; voicemail and phone-menu minutes bill at the engine rate. Optional add-ons such as verbal acknowledgements, call supervision, and long prompts carry their own published surcharges. The agent builder shows the current all-in rate before calls are placed.

Frequently asked questions

Can a ThunderPhone agent qualify solar leads?

It can run your qualification script — homeownership, property type, utility, bill range, roof, timeline, battery interest, or whatever fields you configure — and deliver each answered script as a structured lead to your CRM by webhook or API. It collects and records; qualification judgments stay with your sales team.

Can we use it to cold-call purchased lead lists?

That is not what ThunderPhone outbound is for. Campaigns are built for your own customers and your own consented leads — survey confirmations, project updates, service follow-ups, post-install check-ins. Consent, calling-hour, and do-not-call compliance for any campaign is your company's responsibility, and solar telemarketing is one of the most heavily enforced calling categories in the United States. If a list's consent is in doubt, do not load it.

Can it tell customers where their project stands?

Yes, in both directions. Inbound, when connected to a system that exposes project status, it answers from the data your system returns. Outbound, a campaign can call your active customers at milestones you choose — permit approved, inspection scheduled, PTO granted. Without a connection, it takes a structured message for your project coordinator.

Can it handle monitoring alerts and service calls?

It can run your service-intake script, create structured tickets for production drops, fault codes, cleaning requests, and warranty claims, and escalate immediately on any report your script flags as urgent. It does not diagnose systems or give electrical advice — triage rules and red-flag lists come from your operations team.

Is ThunderPhone compliant?

ThunderPhone's public posture is GDPR and HIPAA compliant. A solar company must still configure access, recordings, disclosures, integrations, retention, and agent instructions for its own obligations — including the telemarketing rules that govern its outbound campaigns.

Can one agent speak both English and Spanish?

Yes. Configure one as the primary language and the other as an additional language, and the agent can switch mid-call when the caller changes language, provided the selected voice supports both. The same applies across ThunderPhone's 47 supported languages.

How do we test it before homeowners hear it?

Test in the browser first, then run AI-caller simulations of the calls that worry you — a pushy price shopper, a stalled-permit complaint, an urgent service report. Simulated calls are graded against your criteria and can be re-run as a regression suite whenever the prompt or knowledge base changes.