Call intake
Identify the caller, network context, site, station, connector, account, or session details required by the approved flow.
For CPO network operations and support leaders
Charging Point Operator Support Needs a Clear Owner at Every Step
Keep calls, connected requests, Level 2 decisions, field work, and urgent escalations tied to the right team as your network adds sites and programmes.
Built for CPO workflows24/7 call availabilityMultilingual call supportHuman ownership stays explicit
The ownership test
Can Your Team Name the Next Owner Before the Call Begins?
01Guidance
02Connected request
03Level 2 decision
04Field work
05Urgent escalation
Growth exposes gaps when the answer depends on who is on shift, which vendor receives the case, or which system happened to respond.
Growth changes the support problem
More Sites Create More Handoffs Before They Create More Answers
Charging point operator support becomes harder when one network includes different site labels, apps, account models, hosts, charger vendors, CPMS interfaces, maintenance partners, and support schedules. The same caller question can require a different answer or owner depending on where the call began.
We help you turn those differences into operating rules. Each call reason receives an identification path, an approved set of instructions, a connected system boundary when needed, a way to confirm the outcome, and a destination for anything the flow shouldn't decide.
That structure is useful whether EVCalls handles a selected first response, an after hours schedule, overflow, or context gathering before Level 2. The detailed support workflow shows how those decisions move from the call to a known next step.
One call can cross several teams
Six Ownership Areas Keep the Case From Falling Between Vendors
The CPO chooses the exact boundaries. We make those boundaries visible in the workflow.
Guidance
Walk through the CPO's app, account, wallet, first charge, and safe caller checks in the order the operator approves.
Connected requests
Use a reviewed CPMS API or webhook for permitted information and requests, while the CPMS stays in control of charger communication.
Level 2 decisions
Send refunds, policy exceptions, unclear technical results, and other judgement calls to the team that owns them.
Field work
Route physical inspection, damage, maintenance, and repair to the CPO's field service or approved vendor path.
Urgent escalation
Bypass routine troubleshooting when the operator's emergency or safety conditions are present.
Build the map before the script
Seven Questions Expose an Ownership Gap Early
A helpful answer isn't enough if the connected request, exception, or field issue reaches nobody. These questions keep the whole operating chain in view.
01Who answers this call reason and during which hours?
02Which identifiers are required before guidance or a request?
03Which system supplies the information, and who owns that system?
04What may the support flow explain, read, or request?
05Which response confirms the result, and what counts as uncertainty?
06Who receives safety, refund, technical, or field exceptions?
07What happens when a transfer or connected system is unavailable?
The location changes the operating rules
One Network Can Contain Very Different Support Environments
The call first needs enough context to select the right guidance, system path, and receiving team.
Public charging sites
Station identification, app or account access, failed starts, connector questions, site conditions, and an escalation route that matches the location.
Community, workplace, and residential programmes
Different access rules, operating hours, property contacts, account models, and responsibilities between the CPO and site host.
Corridor and fleet operations
Time sensitive charging calls, known depot or route context, schedule pressure, and a defined technical or field destination.
For Ontario operations, our Ontario network support approach adds winter site conditions, highway corridors, community charging, workplaces, fleets, and multi unit buildings to that review.
The CPMS is one owner in the chain
A Connected Request Doesn't Transfer Operational Accountability
EVCalls can work through an available CPMS API or webhook after the interface, permissions, fields, and responses are reviewed. We don't connect directly to charging stations or execute OCPP commands. The CPMS remains responsible for its communication with the charger.
The CPO decides when the request is allowed, which response counts as confirmation, and who receives an unavailable, rejected, or unclear result. Our CPMS integration review documents that boundary before it enters a support flow.
The result still needs an owner
CPMS response confirms the agreed outcome
CPMS rejects or cannot accept the request
CPMS is unavailable during the call
Available response doesn't confirm what happened
Expand from evidence
Prove One Boundary Before You Add Another Part of the Network
A focused pilot can test how people, systems, and fallback routes behave without promising a fixed implementation date.
Choose one support boundary
Select one call reason, schedule, site group, or programme where ownership can be stated clearly.
Map every decision owner
Connect questions, systems, permissions, confirmation signals, people, and fallback routes to the current operating rules.
Test the paths that break
Include missing station details, unavailable systems, rejected requests, unclear results, safety reports, and failed transfers.
Review before adding scope
Use the agreed pass or fail record before another workflow, site group, schedule, or language enters the operation.
CPO operations questions
Frequently Asked Questions
Practical answers about ownership, network differences, escalation, records, and expansion.
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