Solar customer service after install is mostly the same handful of questions, asked again and again: why is my production low, what does this alert mean, why is my utility bill still high, and is that stain on the ceiling from the panels. A good setup answers the routine ones from your own documents, books service visits for anything physical, and sends warranty and money questions to a person. Your customers get clear answers drawn from your own materials, and your team stops spending the day on the same five calls.
This post is for solar installers whose phones keep ringing long after the crew has left the roof. It covers what customers call about, how answers should come from your own materials, and what should always go to a person. For the general idea of answering from your own files, see our guide to an AI knowledge base for small business.
What do solar customers call about after install?
They call about production, alerts, bills and the roof. Most of those calls have a known answer that lives in your documents, and a few need a technician or the owner. Battery or panel add-on questions are sales leads hiding in service calls.
The usual list:
- "My production looks low." Often weather, shade from a growing tree, seasons, or a dirty array. Sometimes a real fault.
- "I got an alert from my monitoring app." A lost connection, a single panel offline, or a system that stopped reporting.
- "Why is my utility bill still so high?" Net metering credits, billing cycles, and true-up months confuse almost everyone.
- "Is my roof leaking because of the panels?" A stain or a drip near a mount.
- "What does my warranty cover?" Panels, inverters, workmanship and roof penetrations often have different terms.
- "Can I add a battery or more panels?" A sales lead hiding in a service call.
Why should the answers come from your own documents?
Answers should come from your own documents because every installer's equipment, warranties and utility rules are different. A generic answer can be wrong for your customer, and a wrong answer about a bill or a warranty causes real trouble. When the answer is not there, the AI takes the details and flags a person.
The AI should answer only from what you give it:
- Your post-install welcome packet.
- Your monitoring app guide, in your words.
- A plain explanation of net metering for the utilities you work with. In Missouri, the Net Metering and Easy Connection Act (opens in a new tab) requires retail electric suppliers to offer net metering to customers who make their own power, up to a set cap.
- Your service visit policy.
- Your warranty summaries, so it can tell a customer which kind of question they have and route it.
It is built to answer only from your approved information. When the answer isn't there, it takes the details and flags a person.
How should a solar company handle monitoring alerts?
A solar company should sort monitoring alerts by what they mean and who needs to act. Some alerts fix themselves; others need a visit. A lost connection gets your reconnect guide, one panel offline goes to the service team, and a whole system down is flagged to your service manager the same day.
A simple flow:
- Connection lost. Often a home internet change. The AI can share your step-by-step reconnect guide, from your documents.
- One panel or optimizer offline. Logged for your service team to review and schedule.
- Whole system down. Flagged for your service manager the same day.
- Anything involving smoke, burning smells, sparks or damage after a storm. The only instruction is to call 911, and your on-call person is alerted. The AI gives no safety advice.
The AI never tells a customer to open an inverter, touch wiring or climb on the roof.
Can solar customer service keep the personal touch?
Yes, if the routine answers are handled quickly and the important calls still reach your people. A good setup should feel like a well-trained front desk, not a wall. Our guide to AI customer service shows how that split works in any small business.
We can set up the Customer Agent, our AI receptionist, to answer your solar customers' calls, texts and website chat, explain production dips and net metering from your own documents, walk them through reconnecting a monitoring app, and book a service visit on your calendar when something needs a technician. The Customer Agent is one of our six Starter Upgrades, each one set up around a real stack of daily work. If a customer asks about adding a battery, the agent can hand that lead to sales; our post on solar follow-up covers what happens next.
Every call and text opens with a short line saying it is the business's AI assistant, and asking for a person always works.
Can an automated answering service for solar panels book service visits?
Yes. It can collect the address, the system details on file and the problem in the customer's words, then offer open service windows and book one. Roof leak worries always become a service visit, and your crew decides the cause on site.
A good booking asks:
- What the customer noticed and when it started.
- Whether the monitoring app shows an alert.
- For a roof concern, where the stain or drip is and when it appeared.
- A photo from inside the house, if they have one. The AI never asks anyone to get up on a ladder or the roof.
Roof leak worries always become a service visit, not a phone diagnosis. Your crew decides the cause on site.
Only text people who contacted you or gave you permission, and make opting out easy, in line with the FCC's rules on automated texts (opens in a new tab). Our guide to AI phone answering for small business covers the basics of how calls flow.
What stays with your people?
Warranty decisions, billing disputes and refunds stay with your people, along with any promise about production or savings. Roof leak causes and repairs, upset customers and anything about safety also go to a person, while the agent sticks to routine answers from your documents and booking visits.
The agent answers routine questions and books visits. People handle the rest:
- Warranty decisions. Whether something is covered is a person's call.
- Billing disputes and refunds.
- Promises about production or savings.
- Roof leak causes and repairs.
- Upset customers and complaints.
- Anything about safety.
Same team. Same jobs. More capacity. Your service team spends time on real problems, not on explaining the same bill line one more time.
A low-production week, start to finish
This is an illustration, not a customer story.
A homeowner texts a solar company on a Monday. Their monitoring app shows production well below last month, and their utility bill came in higher than they expected.
The Customer Agent replies right away and says it is the company's AI assistant. It asks if the app shows any alert. No alert. It shares the company's own note on how shorter days and a few cloudy weeks lower production in the fall. Then it explains, from the company's net metering guide, that this month's bill reflects the billing cycle, not a problem with the panels.
The homeowner then mentions a small stain on an upstairs ceiling near where the panels were mounted. The agent does not guess. It asks for a photo from inside, offers two service windows, and books Thursday. It sends the service manager a summary with the photo and a note that the customer's roof work warranty question should go to the office.
On Thursday, the technician checks the roof and makes the call. The office answers the warranty question that afternoon.
Frequently asked questions
Can the agent read our customers' monitoring data?
It depends on your monitoring platform and what access you allow. Where it can connect, the agent can see the alerts you choose. Each agent gets only the access its job needs, following the security principle of least privilege (opens in a new tab), and it is built so each action is logged in a record that shows any later edit.
What if a customer asks for a refund or a credit?
The agent passes the request to a person with the full conversation. Refunds, credits and billing changes are always decided by your team. The agent never promises a credit or says whether one is likely.
Will it give wrong answers about utility bills?
It is built to answer only from your approved information. When the answer isn't there, it takes the details and flags a person. Keeping your net metering guide current is the most important step.
Can it handle calls in the evening and on weekends?
Yes. It is built to answer day and night, and evenings are when many customers check their apps and bills. Urgent issues still reach your on-call person.
Next step
If post-install calls are swamping your service team, book a free workflow consult. We are based in the Kansas City metro and meet owners in person or by video. We will look at the questions your customers ask most, the documents you already have, how monitoring alerts reach you today, and how service visits get booked.
About the ScaleAlphaAi team
We are a Kansas City company that designs and builds AI agents and custom software for small businesses, trades and growing firms. We write these guides from our work with owners and office teams: what AI handles well, what stays with your people, and how to start with one workflow.
Meet the team
