Continue in the approved flow
App discovery, first charge guidance, wallet top up instructions, and other defined steps can continue when the call has the required context.
For CPO teams carrying the phone after the desk closes
After Hours EV Charging Support Should Protect Your On Call Team Without Leaving Drivers in a Dead End
Keep routine calls moving, wake the right owner, and carry unresolved work into the morning.
24/7 call availabilityMultilingual call supportCPO defined escalationCPMS-connected workflows
The hardest hour is the one with unclear ownership
One Overnight Call Can Need Four Different Endings
01Resolve inside the approved flow
02Transfer to the on call owner
03Enter the urgent safety route
04Create a clear morning handoff
The schedule alone doesn't make coverage work. Every ending needs an owner, a fallback, and words the driver can understand.
The call doesn't disappear when the office closes
Your Night Shift Is an Ownership Problem Before It Is a Staffing Problem
After hours EV charging support has to do more than answer the phone. A driver can call about a first charge, app access, a wallet balance, a failed session, a stuck cable, a refund, or a physical danger. Those calls don't belong to the same person and they shouldn't follow the same script.
We map what can continue without a human, what needs approved CPMS context, what should wake the on call owner, and what goes straight to the urgent route. You decide those boundaries. EVCalls follows them and keeps the caller informed when the next decision belongs to somebody else.
This gives your overnight coverage a defined job without pretending every problem can be resolved before morning. The goal is a known next step for the driver and a useful record for the team that takes over.
Not every ring should wake the same person
Four Ownership Lanes Keep Routine, Technical, Human, and Urgent Calls Apart
The CPO defines the lane for each call reason and what happens when the expected route isn't available.
Use reviewed CPMS context
The workflow can read approved information or submit a permitted request through the CPMS, then check the response before describing the result.
Wake the on call owner
Refunds, exceptions, unconfirmed outcomes, priority programme rules, and Level 2 decisions move to the person assigned for that schedule.
Use the urgent route
Smoke, fire, exposed electrical parts, visible damage, collision, medical risk, or another defined danger bypasses routine troubleshooting.
Coverage is a chain, not a switch
Five Decisions Turn Nights and Weekends Into an Operating Schedule
If one decision is missing, the call can still reach a dead end even though somebody answered it.
When coverage begins and ends
Set the exact hours, time zone, weekends, holidays, overflow triggers, and any customer or programme exceptions.
Which calls may continue
Give every approved call reason its own questions, guidance, connected permissions, confirmation, and stopping point.
Who receives each exception
Name the Level 2, refund, field service, account, emergency, and programme owners for each part of the schedule.
What happens when nobody answers
Define the next destination, caller explanation, retry rule, and record when the first human route is unavailable.
What the morning team receives
Separate completed calls from pending decisions, failed transfers, service needs, and urgent events with the approved context attached.
Connected evidence has limits
The CPMS Can Inform the Overnight Call Without Giving EVCalls Direct Charger Control
EVCalls can use an available CPMS API or webhook after the interface, permissions, fields, requests, responses, and unavailable path are reviewed. It doesn't connect directly to charging stations and doesn't execute OCPP commands.
When a workflow includes an authorised request, such as a connector release, EVCalls submits that request through the CPO's CPMS. The CPMS remains responsible for charger communication. The caller hears that a result occurred only when the agreed response or another approved signal confirms it.
Our CPMS integration process tests the normal result, rejection, delay, timeout, and unavailable system path before a connected step joins overnight coverage.
The voice agent stops instead of filling the gap with a guess
- Required caller, charger, account, or session context is missing
- The connected system is unavailable or returns an unclear result
- A financial or policy exception needs an authorised person
- A physical problem needs field service ownership
- Safety language activates the urgent route
A second path needs the same rules
Failover Should Preserve the Call Logic, Not Only Keep a Service Online
EVCalls is available 24/7 and the deployment plan includes failover to another server. That second path still needs the approved greeting, call rules, connected boundaries, human destinations, and data handling decisions.
If the CPMS is unavailable while the voice service remains available, the workflow changes according to the call reason. Some guidance can continue. A call that depends on live station, account, or session evidence must stop or escalate through the route you approved.
We include both failures in the overnight test because infrastructure recovery and caller handling are different responsibilities. Our security and data review documents where call information goes across the primary and failover design.
Two unavailable paths to test separately
Voice service path
Confirm the failover service receives calls with the approved workflow and routes.
Connected system path
Confirm each call reason continues, stops, or escalates correctly without CPMS context.
The morning team shouldn't have to reconstruct the night
Every Overnight Call Ends With a Status and a Named Owner
A completed guidance call, pending refund decision, failed transfer, field service need, and urgent event shouldn't arrive as five identical tickets. The handoff records the approved identifiers, what the caller reported, what guidance was completed, which connected requests were submitted, what responses came back, and what still needs a decision.
The CPO also decides which events require an immediate notice and which belong in the morning review. EVCalls isn't currently tied to a specific CRM, but it is ready to review the API or webhook available for the system the operator uses. Until that integration is approved, the handoff method remains part of the deployment design rather than a public product promise.
The next team should know
- Which call reason and charging context were identified
- Which approved guidance and requests were completed
- Which result was confirmed, rejected, delayed, or unavailable
- Which human routes were attempted and whether they answered
- Which decision, field action, or customer follow up remains
- Who owns the next action and when its review begins
Test the bad night, not only the clean demo
An Overnight Pilot Has to Prove the Boundaries Under Pressure
Start with one call reason, one schedule, the current receiving team, and a result everyone can judge.
The review should include
- A routine call reaches its approved end without waking the on call team
- A Level 2 exception reaches the correct person with useful context
- A safety phrase bypasses normal troubleshooting and enters the urgent route
- An unavailable CPMS changes the call according to the agreed fallback
- A submitted connected request is not treated as a confirmed result
- A failed human transfer follows its second destination and caller message
- The morning record separates completed work from decisions still waiting
Questions CPO teams ask before handing over the night
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