App, account, or authorisation
Find where the attempt stopped before treating a sign in, wallet, RFID, payment, or start problem as charger failure.
For CPOs serving highway and corridor fast charging
Highway Fast Charging Support Has to Find the Right Next Step Before the Journey Stalls
Identify the exact asset, use only confirmed evidence, and keep every unresolved call moving to a known owner.
CPO corridor focus24/7 call availabilityMultilingual call supportConfirmed outcomes guide the call
A mid-journey call needs three certainties
The Right Charger, the Known Result, and the Next Owner
Asset certainty
Direction, site, station, charger, connector, account, and session
Result certainty
Caller observation, CPMS evidence, request state, and confirmed outcome
Ownership certainty
Guidance, Level 2, network operations, field, finance, site, or urgent route
Travel pressure makes wrong assumptions more expensive
Start With the Details That Change the Support Route
Highway fast charging support has to place the driver at the correct corridor site before the CPO can trust the next step. Similar stop names, opposite travel directions, several chargers, multiple connectors, and different account paths can turn a partial location into the wrong workflow.
We gather the direction, public labels, charger and connector, account or authorisation method, vehicle context requested by the operator, session state, and visible message. Then we apply the guidance, connected request, evidence rule, and escalation path approved for that exact issue.
The service is built for CPOs with an approved operating relationship. It isn't a public route planner or a direct charging line for networks where EVCalls has no site records, system access, or escalation agreement.
The symptom decides which evidence comes next
Seven Corridor Call Reasons Shouldn't Collapse Into “Charger Not Working”
Each call type has different identifiers, stop rules, system evidence, and receiving owners.
Session will not start
Use the approved sequence for cable state, connector choice, authorisation, charger message, CPMS context, and stop conditions.
Observed charging speed
Record what the driver, vehicle, charger, and reviewed systems show without promising a rate or guessing the cause.
Connector will not release
Apply the exact identity, permission, safety, connected request, and confirmation path approved by the CPO.
One or more unavailable chargers
Separate one occupied, blocked, faulted, or offline connector from a site-wide condition only when the evidence supports it.
Payment, receipt, or refund
Keep account guidance separate from the financial decision that belongs to the authorised payment or refund owner.
Damage or urgent condition
Stop routine troubleshooting for smoke, fire, heat, exposed parts, collision, severe damage, or another urgent report.
Build the location from the road inward
Four Identity Layers Prevent Support From Acting on the Wrong Connector
The public sign and the CPMS asset name may not use the same words. The workflow records both and stops when they cannot be matched.
Corridor and direction
Which route, direction of travel, exit, service stop, or site name the caller can see
Parking and station
The charging area, stall, station, cabinet, charger, connector, and public labels
Network and account
The app, account, RFID, wallet, roaming, or other authorisation path approved by the CPO
Vehicle and session
The vehicle context requested by the workflow, cable state, session reference, screen message, and observed result
“Slow” is an observation, not a diagnosis
Charging Speed Complaints Need Comparable Evidence Before a Technical Owner Takes Over
We ask for the charger, connector, session, displayed charging value, vehicle message, battery information included in the CPO's workflow, and the available CPMS context. That gives the receiving team a record of what was seen and where.
We don't promise a charging rate or declare that the charger, vehicle, battery, site power, or another condition caused the result without evidence. The CPO defines the threshold for guidance, Level 2 review, network operations, or field inspection.
A useful speed record separates
- What the driver sees on the charger
- What the vehicle displays
- What the approved system reports
- When each observation was made
- What the workflow has already checked
- Which cause or result remains unconfirmed
A remote request has more than two outcomes
Submission Is Not Success, Even When the Driver Is in a Hurry
EVCalls can submit an authorised request through a reviewed CPMS API or webhook. We don't connect directly to the charging station or execute OCPP commands.
The operator defines the required identity, permission, safety check, interface response, and proof of outcome. If the system stops at submitted or accepted, the call follows the unconfirmed result route instead of telling the driver the charger changed.
Our connected request review tests each state and records what the caller can hear at that point.
Permitted
The CPO has approved this request for this call reason, caller context, asset, and safety state.
Submitted
The reviewed CPMS API or webhook received the request from EVCalls.
Accepted
The interface accepted the request, but that alone may not prove the charger changed.
Confirmed
The approved response or another agreed signal proves the outcome the caller can be told.
One unavailable charger isn't automatically a closed site
Onward Guidance Needs an Approved Source, Not a Guess About the Next Stop
The call first separates a single occupied, blocked, faulted, or offline connector from several affected assets or an uncertain site-wide condition. The driver description and CPMS context need to agree before the workflow broadens the scope.
If the CPO provides an approved same-site option, location source, or onward process, we can follow it and say exactly what that source confirms. We don't invent nearby availability, promise another charger will work, or replace the driver's route planning.
Before the call changes sites, ask
- 01
Can the caller and system context identify the correct corridor side and site?
- 02
Is one connector affected, several known assets affected, or is the scope still uncertain?
- 03
Does the CPO provide an approved same-site charger or queue instruction?
- 04
Is there a reviewed network source for onward guidance, and what does it actually confirm?
- 05
Which Level 2, operations, field, site host, or urgent owner receives the unresolved condition?
Time pressure doesn't expand financial or safety authority
Refunds, Physical Work, and Urgent Reports Keep Their Own Routes
We can explain the approved app, wallet, top up, receipt, payment, or account steps without collecting payment card details. Refunds, disputed amounts, reimbursement, and exceptions remain with the human or financial owner selected by the CPO.
Physical inspection and repair belong to field service or the site owner. Smoke, fire, heat, exposed electrical parts, collision, severe damage, or another urgent report stops routine guidance and follows the approved urgent route.
The receiving owner and failed transfer contract states what context follows each call and what happens when that owner does not answer.
Financial owner
Refunds, disputed amounts, reimbursement, and policy exceptions
Field or site owner
Physical inspection, maintenance, repair, access, and site conditions
Urgent owner
Safety language, emergency threshold, immediate route, and failed contact fallback
After hours owner
Which route remains staffed and what the caller hears when it isn't
Test the pressure points at one real corridor stop
The Pilot Should Fail Safely Before the Public Call Ever Does
Bring the labels, system responses, site contacts, financial owners, and unavailable paths the CPO will actually use.
The corridor review should include
- A driver who supplies the site name but not the direction or charger label
- A start attempt that fails before and after authorisation
- A session whose displayed charging value creates a speed complaint
- A connector release request with a submitted but unconfirmed result
- One unavailable connector compared with a possible site-wide condition
- A payment question that becomes a refund or disputed amount decision
- A physical safety report that must bypass routine technical steps
- A Level 2, network operations, field, financial, or urgent route that does not answer
The overnight and failed contact test checks the same routes when fewer teams are staffed.
Questions corridor CPO teams should settle before launch
Frequently Asked Questions
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