Your Chargers Show "Online" But Drivers Keep Calling Support

What Does OCPP Actually Tell You?

OCPP gives you machine data about the charger's technical state. It does not tell you whether the driver successfully completed a charging session. That distinction matters more than most operators realize.

Here is what your OCPP backend reports reliably:

• → Online/offline status. The charger's heartbeat tells you whether the unit is communicating with your central system.
• → Power delivery. Meter values show voltage, current, and energy transferred during active sessions.
• → Connector state. Available, occupied, faulted, or reserved. Clean machine states.
• → Error codes. Hardware faults, ground faults, communication failures between the charger and its CSMS.

Here is what OCPP does not capture: whether the driver understood which connector to use. Whether the charging app authorized successfully from the driver's perspective. Whether the driver expected 150 kW and got 30 kW because of a cold battery. Whether the process was confusing enough that the driver gave up and called you instead. None of that shows up in your dashboard. All of it shows up in your support queue.

Why Is There a Gap Between "Online" and "Usable"?

A charger can be technically functional and still generate support calls. You already know this. Your uptime score says 98%. Your support team's experience says otherwise.

The gap lives in the space between what the machine reports and what the human experiences. A driver pulls up to your station. The connector is available. The charger is online. Everything on your end looks perfect. But the driver has never used a CCS2 connector before. They try to plug in the Type 2 cable because it looks similar. It does not fit. They assume the charger is broken.

Or the driver's charging app times out during authorization. The charger never sees a failed transaction because the failure happened on the eMSP side, not yours. But the driver is standing at your station, looking at your brand on the charger, and calling your number.

Or a first-time fast charger user expected the full advertised rate and does not understand why they are getting 30 kW on a 150 kW charger. Their battery is cold. Their car is limiting the intake. Your charger is delivering exactly what the vehicle requests. But the driver sees slow charging and blames the hardware.

What Do Your Support Calls Actually Look Like?

If you have spent any time listening to Level-1 support recordings, you already recognize these patterns. The calls that dominate your queue are not about hardware failures. They are about confusion.

• → "How do I start charging?" The driver does not know whether to tap a card, scan a QR code, or use an app. Your charger supports all three. The signage says RFID. The driver does not have an RFID card.
• → "Which plug do I use?" Two cables, one CCS2 and one CHAdeMO. The driver has never seen either. They try the wrong one. It does not latch. They call.
• → "It says communication error." The driver's phone lost signal during app-based authorization. Or the driver started the session before plugging in. The charger is fine. The sequence was wrong.
• → "How do I pay with this app?" Your station works with five different eMSPs. The driver has none of them installed. They do not understand roaming. They want to tap their credit card. Your charger does not support contactless yet.
• → "Why is it so slow?" The driver expected DC fast charging speeds. They plugged into an AC outlet on a dual-standard unit. Or their battery is at 85% and the car is tapering. Your charger is doing exactly what it should.

These are not hardware problems. They are knowledge problems. And every one of them costs you the same as a real fault call: agent time, hold-queue capacity, OPEX that scales with your network instead of shrinking with reliability improvements. You can drive your hardware fault rate to near zero and still see your support costs climb, because the calls were never about hardware in the first place.

How Do You Deflect Level-1 Support Calls?

The pattern is clear: drivers call support because they do not have a self-serve alternative at the moment they need it. Not on your website. Not in a PDF manual. Right there at the station, while they are standing in front of the charger with a cable in their hand.

The fix is giving them a path to self-resolution before they reach for the phone. That means:

• → Step-by-step troubleshooting at the station. A QR code on the charger that links to visual, problem-specific guidance. Not a generic FAQ page. Guidance that starts with what the driver sees ("charger says communication error") and walks them through the fix in 30 seconds.
• → Connector identification. Clear visual guidance on which plug fits their car. Most new EV drivers have never seen a CCS2 connector up close. They do not know that the top portion is the AC plug and the bottom pins are DC. They just see two cables and guess.
• → Payment method walkthroughs. Which apps work at your station. How to start a session with RFID versus QR code versus contactless. The driver needs to know this before they call your 0800 number.
• → Expectation setting for charging speed. If drivers understand that a cold battery charges slower, or that AC charging tops out at 22 kW, or that power tapers above 80%, they do not call you about "slow" charging. The charger is not slow. Their expectations were wrong.

The goal is simple: the driver solves the problem themselves in 30 seconds instead of waiting on hold for 5 minutes. Your support agents handle real faults. Your OPEX per station drops. Your uptime score finally tells the same story as your support metrics.

What Is the Bottom Line for CPOs?

Your chargers work. Your OCPP data proves it. But OCPP was never designed to tell you whether the human standing at the station understood the process. That gap between "online" and "usable" is where your support costs live.

Closing that gap does not require more hardware, better signage design, or a bigger support team. It requires giving the drivers who use your stations access to self-serve troubleshooting at the moment they need it.