App, account, and first charge
Guide the caller through the CPO's approved app discovery, sign in, account, wallet, and first session steps.
For CPO customer experience and support teams
EV Charging Customer Support Should Turn Every Call Into the Right Operator Action
Identify what the caller can see, choose the approved issue path, check the available evidence, and keep every exception with a known owner.
CPO workflows only24/7 call availabilityMultilingual call supportHuman escalation for exceptions
The first call decision
A Symptom Is the Starting Point, Not the Diagnosis
01What can the caller see?
02Which network and site is involved?
03Which account, station, connector, or session applies?
04What do the approved systems confirm?
05Who owns the next decision?
One caller, several possible systems
The Call Has to Find the Failure Point Without Inventing One
EV charging customer support starts with the problem the caller can describe, then connects it to the CPO's approved operating context. A failed start can involve the app, account, wallet, authorisation, connector, charger, communications link, or management platform. The first symptom does not prove which layer owns the problem.
We build questions that narrow the path without asking the caller to diagnose the network. The flow identifies the required references, follows the operator's current guidance, uses reviewed connected context when available, and stops when a person or another team owns the next decision. We map each start attempt from the last confirmed step through the next approved action, result check, and escalation.
This service is built for charging operators designing support across their customer journeys. The CPO defines its customer policies, system access, technical ownership, field routes, and emergency process, and we configure the call workflow around those decisions.
Issue lanes need different rules
Six Common Call Types Shouldn't Share One Troubleshooting Script
Each lane needs its own identifiers, guidance, connected context, decision owner, and fallback.
Session will not start
Separate what the caller can see from app, account, authorisation, connector, station, communication, and backend context.
Wallet, receipt, and refund
Explain approved account steps, then move refunds, disputes, and financial exceptions to the authorised owner.
Connector release
Use the reviewed identification, safety, CPMS request, and result confirmation path before describing an outcome.
Damage and safety
Stop routine troubleshooting and use the operator's urgent route for physical damage, smoke, fire, exposed parts, or another defined risk.
Unclear or unresolved
Transfer the issue with the permitted caller context, references, completed steps, and the decision the next team owns.
From symptom to known next step
Five Evidence Checks Keep the Conversation Grounded
Start with the symptom
Record what the caller can see or hear without turning that first description into a technical diagnosis.
Locate the charging context
Use the site's labels and the operator's required account, station, connector, or session references.
Select the decision path
Match the situation to the approved guidance, connected information, permissions, and stopping rules.
Check the available result
Separate an instruction given or request submitted from a change the agreed evidence confirms.
Close with a known owner
Explain the confirmed next step or transfer the unresolved decision to Level 2, finance, field service, or the urgent route.
Connected context has a boundary
The CPMS Can Supply Evidence Without Giving the Voice Agent Direct Charger Control
EVCalls can use an available CPMS API or webhook after the interface, fields, permissions, responses, and failure paths are reviewed. It doesn't connect directly to charging stations or execute OCPP commands. The CPMS remains the charger facing system.
An approved request still needs an approved confirmation. Our CPMS integration process separates information read, request submitted, response received, and result confirmed so the caller isn't told more than the evidence supports.
Five conditions stop the normal path
- The site, station, connector, account, or session cannot be identified as required
- The connected system is unavailable or its response does not confirm the outcome
- The caller reports physical damage, fire, smoke, exposed electrical parts, collision, or medical risk
- The request involves a refund, disputed charge, policy exception, or another financial decision
- The available instructions do not match the caller's situation or the approved workflow
Closure is an operational state
A Call Can End Correctly Even When a Human Owns the Answer
The support record should show whether guidance was completed, a result was confirmed, a transfer was accepted, a field route was selected, an urgent path was followed, or a fallback was required. That is more useful than calling every conversation resolved or unresolved.
The operator approves what context follows a transfer. The confirmed starting set is the caller's name and phone number when needed, the reason for the call, and the steps already completed. Additional station, connector, account, or session references depend on the workflow and available interface. The call escalation path also defines what the caller hears and what happens when the receiving route doesn't answer.
Our CPO support ownership model connects each ending to the team that accepts the next decision.
Review one ending at a time
01Guidance completed
02Connected result confirmed
03Level 2 transfer accepted
04Financial owner received the decision
05Field or urgent route selected
06Fallback recorded with the missing evidence
CPO workflow questions
Frequently Asked Questions
Practical answers about identification, issue separation, connected requests, financial boundaries, and call closure.
Get Started
Plan a Working Demo
Bring one common call reason and the way your team handles it today. We'll use those details to prepare a practical demonstration.
Built around one real support workflow
Multilingual call support scoped to your network
CPMS access reviewed before integration
A focused pilot with agreed test conditions