Depot chargers your fleet can count on every morning
A vehicle that did not finish charging overnight is a route you have to re-plan before 6am. GridLink watches your depot chargers while nobody is there, finds the cause, and clears what it can through your existing charging software. When the fix needs hands, it texts whoever is on shift and walks them through it, so the state of charge is where the schedule assumed it would be.
The shift that matters happens while the depot is empty
Depot charging has one hard deadline and no spare capacity around it. If a port drops off the network at midnight, nobody finds out until a driver walks up to a vehicle at 60% and the route gets rebuilt on the spot.
Your yard crew can close more than you think, at 4am, without a call-out
Depot charging is one of the few places where someone is usually near the hardware. When a fault is physical but simple, that is worth more than any remote command: GridLink texts the person on shift and walks them through it, so the port is back before the schedule notices.
Cleared remotely
Resets, retries, and configuration changes run through the management system you already have. The charger is checked before the ticket closes.
Nobody involved
Cleared by whoever is already there
When the fix is physical but simple, GridLink texts the person who reported it and walks them through it, step by step, any hour. This works on chargers with no network connection at all.
Breaker reset at 03:40, port charging by 03:47
Dispatched, already diagnosed
When it genuinely needs parts or hands, the ticket carries the cause, the evidence behind it, and the part when there is one. Your technician starts at the fix.
One visit, not a diagnostic trip
Which conversations run is set by your team and approved in advance. Anything outside them goes to a person, and every message and action is written back where your team already works.
45% of fixes across deployments happen outside business hours. For a depot that is not a statistic about response times. It is the difference between a full battery and a re-planned route. Which steps your crew gets walked through, and which faults skip straight to a technician, is set by your team in advance and reviewable afterwards.
The first month is an observation window. Otto reads every signal your depot produces, learns how your specific chargers fail, and builds the workflows before it acts on anything. If you also host chargers for staff or tenants at those buildings, the site hosts page covers that side.
Whatever is installed at the depot, and whatever software is running it.
Questions fleet operators ask
Most of what stops a depot charger overnight is not mechanical. Connectors stay locked after a session ends, authorizations time out, and units keep charging at a fraction of their rated power. Those clear remotely through your charge point management system. Tripped breakers and chargers that have gone quiet do not, so GridLink texts whoever is on the yard and walks them through it instead. Across GridLink deployments, 60% of tickets are resolved without anyone being dispatched, and 45% of fixes happen outside business hours.
Otto watches your depot chargers continuously, so a fault at 2am is diagnosed and cleared at 2am rather than found by the first driver at 5am. When a fault genuinely needs hands on the unit, the escalation goes out with the root cause attached so the morning is spent fixing it, not diagnosing it.
It runs alongside the charge point management system you already have and acts through its API. Deployments run on Monta, Ampeco, Ampcontrol, Driivz, and EV Connect, and the hardware side covers ABB, Autel, Kempower, ChargePoint, Blink, BTC Power, and anything else that is OCPP compliant.
Tell us what your depot looked like this morning.
Thirty minutes on your charger mix, your overnight window, and the vehicles that keep coming up short. The reliability calculator is a faster first look if you want numbers before a call.