Why do generic helpdesks struggle at solar companies?
A solar customer is not a single ticket. One homeowner stays with you for months before the system runs and for decades after it does, and most of the waiting is controlled by someone outside your company. Helpdesks built around short, self-contained requests lose that thread.
- The project outlives the ticket. Between contract and switch-on sit a site survey, design, permits, the install, a city inspection and the utility's sign-off. Berkeley Lab's 2026 study of distributed energy interconnection found that more than half of projects under 30 kW received permission to operate within 90 days of applying between 2020 and 2025, a span that includes construction and inspection. That is a long time for one homeowner to write in, and each message needs the current project stage beside it.
- Outside parties own the delays. The building department, an HOA, the utility and the lender all hold steps your staff cannot speed up. A generic helpdesk has nowhere to record who the project is waiting on.
- Sales promises surface in support. Homeowners quote what the salesperson said about savings, timelines or payments. Those threads need the signed proposal attached and a path to sales leadership, not a standard queue.
- Service means a truck roll. A leak or an inverter fault often ends in a site visit, so the ticket has to carry equipment serials, roof type and photos to dispatch, and stay open until the technician closes the job.
- Money questions come from three directions. Cash buyers, lease and PPA customers, and loan borrowers each have a different counterparty, and a lender's payment schedule can start before the system produces anything.
- Systems change hands. Home sales transfer leases and warranties, so records keyed only to the person who signed break.
How should a solar installer set up its customer service inbox?
Route by project stage first, then by topic, and put an owner and an SLA on each queue. The SLA figures below are example starting points to tune after a month of your own data, not industry benchmarks.
| Queue | What lands there | SLA target | Owner |
|---|---|---|---|
| Pre-install projects | Survey, design, permit and install-date questions from signed customers | First reply in 4 business hours | Project coordinator for that territory |
| Interconnection and PTO | Installed systems waiting on inspection, utility approval or a meter swap | 1 business day; stays open until PTO is logged | Interconnection specialist |
| Urgent safety and leaks | Water inside, smoke, sparks, burning smell, storm damage | Callback in 30 minutes, on-call route after hours | Service manager on duty |
| Service and monitoring | Offline systems, error codes, low production, battery faults | 1 business day; remote check before any truck roll | Service desk technician |
| Customer finance | Lease and PPA billing, loan questions, payment start dates, buyouts | 1 business day | Customer finance lead |
| Complaints and cancellations | Cancel requests, sales disputes, regulator or attorney mentions | Same business day, owner named in the first reply | Customer care manager |
| Home sale transfers | Buyers, sellers and real estate agents asking about a system | 2 business days, tagged with the closing date | Transfer coordinator |
| Dealers and partners | Sales dealers and subcontracted crews in Slack Connect | 4 business hours | Partner operations |
Routing rules worth writing on day one
- Read the project stage from your project platform on every new conversation and add it as a column, so a view of "installed, no PTO" is one filter away. Aftersales Inbox shows company and custom fields as filters and columns.
- Keywords such as leak, water, smoke, sparks or burning jump straight to the urgent queue on any channel, phone included.
- Words such as cancel, attorney, contractors board or attorney general move the thread to complaints and post a note to the care manager in Slack.
- Messages from dealer and crew Slack Connect channels go to partner operations, never to a homeowner queue.
- Use side conversations to ask the permitting team, finance or a field lead a question without leaving the homeowner's thread, and use a workflow to open a Jira issue when a monitoring app or firmware defect affects many homes.
What reply templates does a solar customer care team need?
These are the conversations where tone matters most. Each one names who owns the next step and when the homeowner will hear back. Replace the bracketed parts.
Utility approval taking longer than expected
Hi [first name], your system passed its final inspection on [date] and is now with [utility] for permission to operate. That approval is the utility's step, so I can't give you a firm date, but I've asked them for an update today and I'll write to you by [day] with what they say. Please keep the system switched off until you receive the approval email; your utility requires its approval before the system runs.
Roof leak reported
Hi [first name], thank you for telling us straight away. If water is near any electrical equipment or you notice smoke or a burning smell, please stay away from it and call 911. Otherwise, place a container under the drip and, only if it is safe, send a photo of the ceiling and the area of roof above it. [Name] from our service team will call you within 30 minutes to arrange a visit, and once we find the cause we'll confirm in writing what your workmanship warranty covers.
"My system makes less than you promised"
Hi [first name], I've compared your output since [date] with the monthly estimate in your proposal. [Month] came in at [x] kWh against an estimate of [y] kWh. Some of that gap is normal for the season, but I don't want to guess, so I've booked a remote check of every panel and the inverter for [date]. I'll send you the results, and if we find a fault we'll schedule a technician at no cost to you.
Loan payments started before the system is on
Hi [first name], I understand how frustrating it is to pay for a system that isn't running yet. Your loan is with [lender], so the payment schedule is set by them, not by us. I've sent you their customer service details, and our finance lead, [name], will call you by [day] to go through your contract with you and what we can do on our side while we finish [remaining step].
Request to cancel after a sales dispute
Hi [first name], I'm sorry the project hasn't matched what you were told. I've passed your request and your notes about the sales conversation to [name], our customer care manager, who has the authority to review your contract. They will call you by [day]. Until then, nothing further will be installed or billed without your agreement.
Tax credit question after the 2025 cut-off
Hi [first name], we can't advise on your taxes, but here is what we can share. Your system was placed in service on [date], and the IRS states that the Residential Clean Energy Credit is not available for property placed in service after December 31, 2025. I've attached your paid invoice and inspection record. A tax professional can tell you whether any other credit or incentive applies to you.
How should a solar company staff customer service through the year?
Most installers do best with project pods that own a homeowner from contract to PTO, a separate service desk for installed systems, and a small finance and complaints group. Staff to the install calendar and the weather, not to a flat weekly average.
- Pods by territory. One coordinator per region knows that region's building departments and utility, which shortens every status reply. Pair each pod with an interconnection specialist who files and chases utility applications.
- Service desk. Technicians who can read monitoring data and run remote checks before dispatching a crew. Keep one person on call evenings and weekends for the urgent queue.
- Hours. Crews start early, so open the install-day phone line before the first truck leaves. Evenings bring status and app questions that can wait for the morning or go to AI on the portal chat.
- Seasonal peaks. In cold-climate markets installs cluster between spring and autumn, so pre-install volume rises then. Winter brings low-production worries as days shorten and snow covers panels. Storms bring leak and outage calls in bursts, so keep a storm macro set ready.
- Policy deadlines. Incentive cut-offs pull demand forward and leave a backlog behind them; the end of the federal residential credit for systems placed in service after 2025 is a recent example.
Where does AI help a solar customer care team?
AI fits two places in a solar care team: drafting and summarizing for coordinators on the hard threads, and answering the routine status questions so coordinators have time for those threads.
- Summaries. A project thread can run for months across email, texts and calls. Copilot summarizes it before a coordinator calls back, so nobody rereads forty messages to find the last promise made.
- Drafts that cite sources. Copilot drafts replies from your Knowledge and the project record and shows where each fact came from, which matters when the topic is a warranty term or a utility rule.
- Translation. Copilot translates in 31 languages, including right-to-left scripts, so one coordinator can serve homeowners in several languages.
- Agent for the routine share. "Where is my project?", install-date confirmations and app reconnection steps can go to Aftersales Agent, which hands off with what it already checked. See AI customer service for solar companies for its scope and guardrails.
- Quality on every conversation. Insights Monitors score every conversation instead of a sample. Helio Energy saw quality scores rise 14 points after Monitors replaced sampling.
Which customer service metrics should solar companies track?
Measure the project, not only the ticket. Stage timing and contacts per project explain most of a solar team's volume. Set targets from your own history; the guidance column says how to read each metric, not what a good number is.
| Metric | Formula | Target guidance |
|---|---|---|
| Install-to-PTO days | Date PTO logged minus final inspection date, per utility | Track the trend by utility; use it to set what coordinators tell homeowners |
| Stage-age breaches | Open projects past your limit for their stage ÷ open projects | Review weekly; each breach should have a named owner |
| Status contacts per project | Status-tagged conversations ÷ active projects | Falling means proactive updates are working |
| Remote resolution rate | Service tickets closed without a site visit ÷ service tickets | Raise it with better remote checks, without delaying needed visits |
| Urgent callback time | Median minutes from leak or safety report to first call | Measure against the SLA you set for the urgent queue |
| CSAT by stage | Satisfied responses ÷ responses, split by project stage | Find the stage where satisfaction drops |
| Cost per conversation | (Seats + Agent resolutions + channel costs) ÷ conversations | Compare month on month as AI takes more routine volume |
Track finance complaints separately. The CFPB's issue spotlight on solar financing found that some lenders add markups and fees that raise the loan principal by 30 percent or more above the cash price, which is why disputed payment amounts deserve their own tag and a regular review with your finance partners. For definitions of resolution rate and how AI affects it, see our resolution rate guide.
How do solar companies switch helpdesk software?
Many installers start with a shared email inbox, a phone system and a CRM, sometimes alongside a solar-specific project management platform. Others run Zendesk, Freshdesk or Salesforce Service Cloud. Whatever you use now, the project platform stays the system of record and the helpdesk reads from it.
- List your stages and owners. Write down each project stage, who owns it and what it waits on. These become your queues, tags and views.
- Connect the project platform. Pull project stage and dates into conversations through the Aftersales API or webhooks. Confirm specific connectors on a call.
- Move history and macros. Import open tickets and your existing macros. Most teams finish migration in an afternoon, and we run the migration with you on Growth and Scale.
- Port channels one at a time. Start with email, then SMS and portal chat, then phone numbers per brand or region.
- Add sales and field staff as Lite seats. Free on Growth (20) and Scale (50).
- Or keep your helpdesk. Teams staying on Zendesk, Freshdesk or Salesforce Service Cloud can run Agent inside it with no seats and no migration.
Compare plans on our pricing page, or read how options compare in the best help desk software for small businesses.