Add up a single field visit honestly — technician time, travel, vehicle, the part carried just in case, and the hours of lost sessions before anyone arrived — and most Indian operators land somewhere between ₹2,500 and ₹6,000 per dispatch. At a hundred chargers with two incidents each per month, that is a line item large enough to decide whether a site is profitable.
The uncomfortable finding, when networks start tagging their dispatches by outcome, is that between 40% and 60% of visits end with no part replaced. The technician arrived, power-cycled the unit, watched it come back, and drove away. Every one of those is a visit that a disciplined remote triage could have avoided.
A triage ladder, in order
The point of a ladder is that nobody skips to the van because they are busy. Each rung is cheap, each takes minutes, and each eliminates a class of cause.
- 01Read the state. Is the connector Faulted, Unavailable, or merely SuspendedEV because the car stopped the session? The last one is not a fault at all, and it is the single most common false dispatch.
- 02Read the fault code, including the vendor-specific field. Ground fault, over-temperature, communication loss to the power module and cable-lock failure each imply completely different actions.
- 03Check the message log around the failure. A session that failed at Authorize is a platform or connectivity problem; one that failed after StartTransaction is hardware or vehicle.
- 04Change availability. Setting the connector Inoperative and back to Operative clears a surprising share of stuck states without a full reset.
- 05Soft reset. Restarts the charger application; sessions are ended cleanly.
- 06Hard reset. Power-cycles the controller. This is the one the technician would have done on site.
- 07Pull diagnostics. If the ladder has not fixed it, collect the log bundle before dispatching, so the technician arrives knowing what they are looking for.
Only after all seven does a van get booked — and it goes out with a diagnosis and, ideally, the right spare already in the vehicle.
The three faults worth special handling
Communication loss
Usually the SIM, the router, or the local network at the host site rather than the charger. Before dispatching anyone, check whether other chargers at the same site went quiet at the same moment — if they did, the problem is the site’s uplink and a charger technician is the wrong person to send.
Ground fault
Never clear this remotely more than once. A genuine ground fault is a safety condition, and a unit that trips repeatedly needs an electrician, not a reset. A single spurious trip after heavy rain is common; a second trip in a week is a dispatch.
Meter values that stop arriving
This is a billing incident disguised as a technical one. If MeterValues stop mid-session but the transaction continues, the session will close with a wrong energy figure and you will refund it. Detect the gap, not just the failure — a charger that is silently under-reporting is more expensive than one that is plainly dead.
What changes when you measure dispatches
Tag every dispatch with its outcome: part replaced, reset only, no fault found, site issue, vehicle issue. Within two months the distribution tells you where to invest. Heavy "reset only" means your remote ladder is not being followed. Heavy "no fault found" means your alerting is firing on transient states. Heavy "part replaced" concentrated in one model is a procurement decision.
The networks with the best economics are not the ones with the best hardware. They are the ones that stopped sending vans to reset chargers.
Stock the depot, not the warehouse
The last mile of this is inventory. If the diagnosis is right but the part is three days away, the remote triage bought you nothing. The parts that fail are predictable — cables and guns first, contactors second, payment terminals third, and communication modules fourth — and they should sit where the technician starts their day.