Question 1

What fleet details should a CPO include in a depot support workflow?

Accepted Answer

Include only the fleet details needed to identify the charging context and select the approved next step. The workflow may need the depot or site, vehicle or asset reference, assigned charger, connector, driver or fleet account, current session, and the time the vehicle is expected back in service. The exact fields depend on the CPO's programme and systems. A shared pool vehicle may follow a different path from an assigned route vehicle. The team should also define who may request a connected action, which identifiers can move with an escalation, and what happens when the caller cannot supply the required vehicle or charger reference.

Question 2

How should shift timing change the way a fleet charging call is routed?

Accepted Answer

Shift timing should change priority and ownership only according to rules the CPO and fleet customer approve. A vehicle needed for an upcoming route may require a different receiving team from one parked until the next day, but the voice flow should not invent a dispatch priority. It should collect the required ready time, vehicle context, charging state, and completed steps, then apply the agreed threshold. The escalation route may lead to fleet operations, depot management, Level 2 support, field service, or another owner. If timing information is missing or the situation falls outside the rule, the flow should state the uncertainty and use the designated fallback.

Question 3

Can fleet charging support use vehicle and charger information from the CPMS?

Accepted Answer

It can use information an approved CPMS interface makes available after the fields, permissions, responses, and purposes are reviewed. EVCalls does not connect directly to the charging station or execute OCPP commands. The CPMS remains responsible for charger communication. The technical and operations teams decide which site, station, connector, session, account, or other fleet programme references may be read during the call. Vehicle assignment data may sit in another system and should not be assumed available. Each source needs a clear owner, access boundary, and fallback. The flow should distinguish information retrieved from information the caller supplied and avoid treating either as confirmation of a result.

Question 4

When should a depot charging issue move to field service?

Accepted Answer

Move it to field service when the approved workflow identifies work that requires physical inspection, maintenance, or repair at the depot. Examples can include visible damage, a site condition, repeated equipment behaviour that the technical owner assigns to inspection, or another issue that cannot be settled through permitted guidance and connected context. The CPO defines the threshold, not the voice agent. Safety reports follow the urgent route before routine troubleshooting continues. The field handoff should include the depot and charger references, the caller's description, available system information, steps already completed, urgency rule, and the specific reason a physical owner is receiving the case.

Question 5

How should support handle a driver who is not authorised for the assigned charger?

Accepted Answer

Follow the CPO's access policy and route the exception to the owner who can make an authorisation decision. The flow can identify the driver or fleet account, vehicle, depot, assigned charger, and available session context using the fields the programme approves. It can explain existing access steps, but it should not grant permission, change an assignment, or bypass a policy unless an authorised connected workflow explicitly allows that request. If the caller, vehicle, or charger cannot be matched, the flow should stop account specific guidance. The case then moves to fleet operations, depot management, or another designated owner with the missing or conflicting information stated clearly.

Question 6

What should a CPO test before adding another fleet depot to the support programme?

Accepted Answer

Test whether the existing workflow remains correct when the depot, schedule, charger labels, fleet account, receiving teams, and system context change. A new site should not inherit another depot's instructions or escalation contacts by default. The review should cover vehicle and charger identification, access questions, failed starts, connected information, permitted requests, result confirmation, urgent reports, shift timing, unavailable systems, and failed transfers. The CPO and fleet customer should agree on pass or fail conditions before calls are evaluated. Add the new depot only after its normal path and exceptions reach the correct owners with the approved context and no unsupported assumption about availability or priority.

AI Support for EV Fleets Needs to Know Which Vehicle, Charger, and Shift Come Next

The Same Charger Symptom Can Affect Two Vehicles Differently

A Depot Call Isn't Only About Whether Energy Is Flowing

Six Inputs Put the Call Inside the Right Fleet Programme

Depot and charger

Vehicle and assignment

Ready time

Driver and account

Session and system

Receiving owner

Five Operating Paths Separate Access, Timing, Technical, and Safety Calls

Access or assignment

Session will not start

Charging interrupted

Vehicle needed soon

Physical or safety issue

The CPMS Supplies Approved Charging Context and Remains Charger Facing

The workflow stops instead of guessing

Frequently Asked Questions

Start With One Depot, One Call Reason, and One Ready Time Rule

Plan a Working Demo