
Lead qualification
Roof type, ownership, location, and urgency get qualified before sales spends real time.
Catches evening and weekend PV enquiries, qualifies before the site visit, follows up on open quotes, and routes monitoring alarms to dispatch — instead of letting leads sit in voicemail while installers are on the roof.
Solar installation inquiry
Outage report — system barely producing
Five recurring moments where the agent qualifies first — so sales and operations spend time on real projects.

Roof type, ownership, location, and urgency get qualified before sales spends real time.

Qualified interest turns into consultation slots while the buyer is still engaged.

Site visits get scheduled with the right context, so the installer is not driving for nothing.

Project status and document questions stop pulling operations into every call.

Late-day questions are captured cleanly so the next morning starts with a clear list.
Enter your number — your phone rings within 30 seconds.
A clear path, visible relief at each step — and a team that quickly sees what the agent is for on a busy Saturday afternoon.
01
You choose the 1–2 call types that block the team most — new PV enquiries, quote follow-up, monitoring alarms, wallbox or heat-pump combi requests.
Visible within days: where leads drop and where the team loses time.
02
You decide what the agent may say, what it captures into the CRM, and when it routes the call to sales, project lead, or dispatch.
Consistent answers, clean handoff — funding advice and fault diagnosis stay with people.
03
The pilot runs on real evening, weekend, and follow-up calls. Each week the numbers show what works and where to fine-tune.
Four weeks of controlled operation — no annual contract.
What changes
Captured leads after hours
Evening and weekend enquiries that turn into a lead in the CRM, not a voicemail.
Site-visit booking rate
Qualified enquiries that turn into a booked site visit on the technician calendar.
Quote follow-up coverage
Share of open offers called back on day five with notes written into the CRM.
Service intake separation
Monitoring alarms and fault calls routed straight to dispatch instead of mixing with new business.
Happy to support the rollout too — from the first call type to going live across regions and service. Book a short demo and we'll show you how it would look in your installer business.
And anything else with an API. We connect to your systems — you don't switch.
and many more
FAQ
Calls run on GDPR-aligned infrastructure. The data flow — what is captured, where transcripts live, who can read them, how long they're kept — is documented for your DPO before the pilot starts. Your CRM stays the source of record.
PV*SOL, Aurora Solar, OpenSolar, plus the inverter and storage portals from SMA, Fronius, SolarEdge, Enphase, sonnen, and SENEC connect through their existing interfaces. Heat-pump and wallbox portals (Viessmann ViGuide, KEBA, Wallbox) connect the same way. Anything else with an API — your CRM, your dispatch tool — connects through that.
Weekend and evening calls arrive structured by category — new PV enquiry, storage retrofit, wallbox request, monitoring alarm, funding question — sorted by your rules. Sales walks into a qualified queue, dispatch into a separate one. Not a voicemail list.
The agent recognises funding questions and routes them to the person on your team who handles them. It does not give funding advice — that line is hard. Same posture as a service advisor at the front desk: capture the question, name a time for a callback, hand off cleanly.
The agent captures plant ID, symptom, and contact, separates the call from new business, and routes it to your service dispatch — where the call should land in the first place. It does not interpret fault codes; technicians do that.
Four weeks of pilot operation, success criteria agreed up front, no annual lock-in. If captured leads and quote-follow-up coverage don't move, you decide against the rollout — and keep what you learned about your call mix.
GDPR in the call path. Voice tuned for EU/DACH. Calls tied to outcomes, tasks, and audit — without your team gluing it together.
Goal, knowledge, handoff rules, and provider choices are written down before live traffic. The rollout has an owner, a path, and an end date — not just a kickoff deck.
Scope, goals, owners
Knowledge + providers
Quality review
Production traffic
Multi-carrier routing, monitored failover, and runtime observability — so transfers actually go through and call records stay intact when traffic spikes.
99.95% uptime
Same agent logic across English, German, French, Italian, Spanish, and 45+ more — with per-workflow language pinning and regional accent handling when it matters.
+ 45 more languages
Optimized WebRTC and SIP infrastructure — callers hear no delay, anywhere in Europe.
Reviews, follow-up tasks, and handoffs all tie back to the source conversation. No re-reading transcripts in a spreadsheet to figure out what to do next.
Hear how voice AI sounds in your industry — and where it delivers impact first.