J.D. Power’s 2023 U.S. Electric Vehicle Experience Public Charging Study found that about one in five visits to a public charger ended without the driver getting a charge. One in five. No other consumer service survives a failure rate like that without becoming a punchline, and public charging did become one: the Reddit threads, the PlugShare check-ins that read like accident reports, the local news segments where a reporter drives to four stations and gets two to work. That is the reputation environment every EV charging company operates in, whether it runs 40 stalls or 4,000.
The odd part is that the reputation problem is easier to fix than the reliability problem, and the two are not the same thing. A network at 97 percent uptime with no review strategy reads worse online than a network at 94 percent that answers every complaint the same day and publishes its own numbers. Reputation management for EV charging companies is the work of making reliability visible, owning the failures in public, and giving drivers a reason to report the good sessions as often as the bad ones. This is how that is done.
Reliability is the reputation
Read a hundred reviews of charging stations on Google Maps and PlugShare and the pattern is obvious within ten. Nobody complains about the kilowatt price. Nobody complains about the app’s color scheme. They complain that the charger was dead, that the screen was blank, that the card reader failed and the app failed and the phone number rang out, that the session stopped at 12 percent, that the stall was blocked by a gas car, that the location was dark and the cable would not reach. Every one of those is a reliability or site problem showing up as a reputation problem.
This has a consequence most charging companies miss. Your reputation strategy is downstream of your operations data, and the two teams need to be the same team or at least the same Slack channel. When a site goes down, the review is coming within hours. When a site is fixed, the review is not being updated unless someone asks the driver to update it. The gap between “fixed” and “known to be fixed” is where reputations die.
Drivers are also unusually organized about this. PlugShare check-ins, the r/electricvehicles and r/evcharging communities, and brand-specific owner forums function as a distributed inspection service, and a station that fails a check-in gets flagged to every driver routing through the area. Google Maps reviews of individual stations feed both the map pack and the AI assistants that drivers now ask for “reliable fast charging near me.” A network that is not monitoring PlugShare and station-level Google reviews is flying blind on the two sources that matter most.
The Uptime Ledger
Here is the framework, and it is built to close the gap between fixed and known-to-be-fixed. The Uptime Ledger is a public, station-level record of three numbers, updated on a schedule the company commits to and keeps.
The first number is measured uptime for the trailing 30 days, per site, using the definition the federal NEVI program adopted, which excludes scheduled maintenance and counts a port as down when it cannot deliver a charge. Publishing per site is the point. A network-wide 98 percent means nothing to a driver who uses one location, and it reads as marketing. A site-level 91 percent, published, reads as honesty, and it makes the 99 percent sites credible.
The second number is mean time to repair, per site, for the trailing quarter. Drivers forgive failure. They do not forgive a charger that has been dead for six weeks with a “we are aware” sticker on it. A published repair time tells them which outcome to expect.
The third number is the open-fault count, right now, with the date each fault was logged. This is the one that changes the review conversation, because a driver who arrives at a dead stall and finds it already listed on the ledger with a repair ETA leaves a different review than one who thinks they discovered the problem.
Put the ledger on a page on your site, link it from the app, and post the monthly update on LinkedIn and in the owner forums where your drivers already are. The companies that do this become the reference point when reporters, fleet buyers, and site hosts compare networks, because they are the only ones with numbers anyone can check. Everyone else is quoting a press release.
The ledger also solves an AI visibility problem. When someone asks ChatGPT or Perplexity which charging network is most reliable in a region, the model needs a source it can cite. A published, dated, station-level uptime page is exactly that source. A network with no public numbers gets described by its Reddit threads instead.
Answering the driver who could not charge
Every one-star review of a charging station is a support ticket that went public because the private channel failed. The reply, then, has to do what the support channel did not, and it has to do it where the next driver will read it.
The reply names the station and the stall. It states the fault as the driver experienced it, without hedging: “Stall 3 at the Route 9 site had a failed contactor from the evening of the 14th until the morning of the 16th.” It states the repair and the date. It states the refund or credit if a session was charged and failed. And it states the change, if there is one: “That site is now on daily remote diagnostics and the fault would have been caught before the driver arrived.” Under 120 words. Within 24 hours. Posted by a named person, not “the team.”
Never reply with “please contact support at” and a phone number. The driver already tried. The reply is read by the next thousand drivers deciding whether to route to your site, and a reply that pushes the complaint into a private channel tells them the problem is not being handled.
Then close the loop with the driver in private, and ask them to update the review if the fix holds. A meaningful share of drivers will, because EV owners are invested in the network working and they respond to being treated as partners in fixing it rather than as complainers. An updated review that says “the company fixed it in two days and refunded the session” is worth more than a new five-star, because it shows the failure and the recovery in one place.
Do the same thing on PlugShare, where check-ins are the currency. A company account that responds to failed check-ins with the fault, the fix, and the date builds a reputation among the most active drivers, who are also the ones writing the forum posts and answering the “which network should I use” questions that shape everyone else’s opinion.
Blocked stalls, dark sites, and cables that do not reach are site-host problems more than charger problems, and the reply should say so without blaming the host. “We have asked the property to add signage and are working with them on lighting” is honest and tells the driver that someone is on it.
Drivers are not the only reviewers. Site hosts talk to each other, and a property manager who had a charging company go quiet after a unit failed tells the next property manager at the regional real estate association meeting. Fleet operators post in their own forums about which networks honored uptime commitments and which sent invoices for sessions that never delivered. Municipal staff who administer NEVI awards compare notes across state lines. Reputation management for EV charging companies has to cover those audiences too, and the tool is the same: a named person, a fast reply, a fault stated plainly, a fix with a date. The difference is that these conversations happen in rooms the company cannot see, which is why the public ledger matters. A site host who can point their boss to a page showing the site’s uptime and repair history does not have to defend the choice of network from memory.
Then there is the local news segment, which every network eventually faces. A reporter drives to four stations, two fail, and the story airs with the network’s logo behind the anchor. The companies that come through those segments intact are the ones whose spokesperson calls the reporter back within the hour, gives the fault and the repair date for each failed unit, and points to the ledger. The companies that send a statement about their “commitment to reliability” become the segment’s villain, and the segment lives on YouTube for years, where ChatGPT can find it.
What ChatGPT says about your network
Ask an AI assistant to recommend reliable fast charging along a specific highway corridor and watch what it does. It names networks, it cites reliability reporting where it can find it, and it often repeats the reputation each network has in driver communities, because that is what it was trained on and what it retrieves. A network that has been the subject of a viral Reddit thread about dead chargers may find that thread paraphrased in the answer. A network with published uptime data may find the data cited.
That makes reputation management for EV charging companies an AI search problem as much as a review problem. The inputs are the same: station-level reviews on Google, PlugShare activity, forum sentiment, local news coverage, and whatever the company has published about itself in a form the model can verify. The Uptime Ledger feeds the last one. The reply discipline feeds the first two. Local news coverage comes from pitching the ledger itself, because a charging company that publishes its own failure rates is a story in any market where the local station chased a reporter’s “we tested four chargers” segment.
There is a practical sequence here. Month one: claim the Google Business Profile for every station, which most networks have never done, so that the replies come from the company rather than from nobody. Set up alerts for the network name on Reddit and the major owner forums. Assign one named person to reply. Month two: publish the first Uptime Ledger with the trailing 30 days, even if the numbers are worse than the marketing has claimed, because the honesty is the point and the improvement will be visible from a baseline. Month three: pitch the ledger to the local business press and the EV trade outlets as a story about a network that publishes its own failure rates, and offer the operations lead as a source for the next reliability story in the region.
Run your network name through the AI Citation Checker on this site and see what the assistants say today. Then set a monthly check and watch it move as the ledger and the reply discipline take hold, because the assistants update their picture of a company as the sources change, and reliability that is visible compounds while reliability that is private does not.
Within a few years the networks drivers trust will be the ones that told them the truth about uptime first, and the ones still quoting a network-wide percentage will be explaining themselves in someone else’s Reddit thread.