Drivers do not arrive at a charger with survey expectations. They arrive with the ones your network created: the help route printed on the unit, the support entry in your app, the hours your site page states. Customer support for a charging network is therefore a promise-keeping exercise — publish only the support you actually staff, and build the system that lets a stranded driver reach someone who can see the session.
Key Takeaways
- Driver expectations are set by the network’s own published promises — at the charger, in the app, on the site page.
- Each promise needs a system behind it and a record that proves it: contact log, outage record, case ageing.
- Complaint categories come from your own log; repeat categories are fixes, not staffing arguments.
- Support hours are the operator’s own staffed decision — except where programme rules write the duties down.
Expectations Are the Promises You Published
| The promise, as the driver meets it | The system behind it | The record that proves it |
|---|---|---|
| A help route at the charger itself — a number or code on the unit, not only inside an app | A staffed or monitored channel behind that route, covered for the hours the site is open | The contact log per site: when, which unit, what outcome |
| Honest status: a unit known to be down is shown as down, in the app and at the site | Platform status data, plus a rule for marking units out of service | The outage record per port — the same file uptime duties are argued from |
| Session help that can see the session | Agent access to session records: start, authorisation, energy delivered, billing state | Contacts categorised in the log: start failure, payment, billing, site condition |
| Billing answers with a receipt and a stated route for disputes | Account and transaction records the agent can open; refund terms published in advance | The billing-contact log, with resolutions noted against the transaction |
| Follow-through: the case ends with an answer, not silence | Case tracking until resolved, or handed to field service with a reference | Open-case ageing, read from the log on a fixed rhythm |
Your Own Log Sets the Categories
No published league table of driver complaints exists to plan from, and none is needed: your contact log, reviewed on a rhythm, shows what your drivers actually meet, by category and by site. A unit that keeps generating start-failure contacts is not a support problem — it is a hardware ticket wearing a support costume, and the fix is a visit, not more agents. A site that generates billing questions after every price change has a signage problem. How a station takes payment varies by site and setup, as our guide to whether charging stations take credit cards sets out — so an agent’s answer must come from that site’s own arrangement, not a network-wide script.
Hours and Staffing: Your Decision, Your Evidence
The hours decision is the operator’s own, made from the sites’ usage pattern. The exception is funded corridors: U.S. NEVI stations must stay open 24/7, accept contactless payment with no membership, and average above 97% uptime under 23 CFR Part 680 — and support is part of how those duties are evidenced. Whether the desk is in-house or contracted matters less than its specification: session-record access, the published hours, the case log, and an audit rhythm. A cheap desk that cannot see sessions answers nothing.
Support Starts With Hardware That Reports
A network can only keep these promises on hardware that reports its state. The EV-AC03201T dual-connector AC station (two Type 2 connectors, up to 43 kW shared, OCPP 1.6J, RFID, IP54) and the EV-RHDC30K-L compact DC charger (22 kW DC, OCPP 1.6J, IP54) both state OCPP 1.6J, so faults and session states reach the operator’s platform — often before the driver calls. The AC03201T’s touchscreen is a display on the unit, not a payment terminal; payment and billing live in the operator’s platform arrangement. EVDANCE, a Shenzhen manufacturer founded in 2011, offers no platform of its own. Operators can start through our commercial EV charging team or contact us.
Frequently Asked Questions
Do drivers expect 24/7 phone support?
They expect the hours you published. Set them from your sites’ usage and any programme duties you carry, print them at the charger, and staff them. An unstaffed round-the-clock claim is the worst option — it converts a small failure into a broken promise.
Should network support be in-house or outsourced?
Either can work. What decides is the specification: agents who can open session records, work the published hours, and log cases in your file. Judge bids against those three, not against a price per ticket.
What should a network measure about its support?
Its own log: contacts per category per site, repeat categories on the same unit, and how long cases stay open. No external benchmark describes your network; the trend in your own records does.
Related Reading
- How Do Commercial EV Charging Stations Work?
- Do EV Charging Stations Take Credit Cards?
- OCPP Explained: What Charge Point Operators Need From EV Charger Hardware
