'The app says zero again'
A customer rings: the app has shown nothing for a week. Almost certainly, the broadband provider sent a new router and the inverter lost its wifi connection. Reconnecting it takes ten minutes on the phone, with the customer in the garage reading out lights and codes. It happens several times a week, for systems from three different inverter brands, each with a different reconnection process.
Sometimes it is not wifi at all, and a real fault waited in the queue behind the router calls.
Why these calls never stop
- Customers change routers, broadband providers and passwords.
- Each inverter brand reconnects differently, and instructions are buried in manuals.
- Customers cannot tell a wifi dropout from a fault.
- The office talks each customer through it by phone.
- There is no record of which customers had which issue.
What app calls cost
Office and engineer time on something most customers could do themselves with the right instructions. Real faults delayed behind wifi calls. Visits booked for problems that were a password. And customers who feel their system is unreliable when it is fine.
Guided self-help, by brand
- The customer's page, or a link in a text, identifies their inverter from your job records, so they only see instructions for their model.
- Step-by-step reconnection instructions with photos of their model's screen or lights, written in plain English.
- Where the monitoring platform has an API, the system checks whether the inverter came back online and tells the customer.
- If it does not reconnect, or the inverter shows an error code rather than a network issue, the customer is routed to the office with the steps they tried and any codes already recorded.
- The office sees these as a list with the details, rather than as phone calls starting from scratch.
- Recurring issues are recorded, which shows which brands or setups cause most calls.
Instructions cover reconnecting the monitoring. Anything beyond that, including anything inside the electrical installation, goes to your engineers.
What the customer and office see
| Situation | Customer | Office |
|---|---|---|
| New router | Guided reconnect, confirmed | Nothing to do |
| Reconnect fails | Told the office will be in touch | Case with steps tried |
| Error code on inverter | Told an engineer will check | Case with code and system details |
Calls for the problems that need a person
Most wifi issues are fixed by customers in minutes. Real faults reach engineers faster. The office handles cases with details already gathered. And customers learn their system is working, even when the app went quiet.
Setting up monitoring well at handover
Many app calls can be prevented at install. If the monitoring is connected to the customer's own account rather than an installer login, if the customer knows which app to use, and if the wifi reconnection steps for their model are sent to them at handover, the first router change becomes something they can handle.
The self-help page supports that. Customers who have it from day one learn where to look when the app goes quiet, and the office only hears about it when something genuinely needs an engineer.
Recording which setups cause the most calls also helps you decide on things like wired connections or wifi extenders at install, where your engineers think it is sensible.
Is this your support line?
- Customers ring about apps showing zero.
- You talk customers through wifi reconnections by phone.
- Real faults wait behind wifi calls.
- You have visited to fix a wifi password.