We answer the driver, follow the workflow and CPMS access you approve, and bring in your team when the call needs a human decision.
Scripted EVCalls Example
Play a scripted call flow
This visual example has no audio and does not represent a live customer call.
Scripted EVCalls Example
Play a scripted call flow
This visual example has no audio and does not represent a live customer call.
Start with the real call
EV charging support in Ontario has to sort out what the driver can see from what your systems can confirm. A failed start might involve the app, wallet, account, authorization, connector, charger, communications link, or CPMS. The first job is to ask the questions that narrow that list without making the driver repeat the story.
We build those questions around your business flow. EVCalls can guide a first charge, help the driver find the correct app, explain approved wallet steps, use the CPMS interface you authorize, and request an allowed action when that interface supports it. We don't connect directly to charging stations or execute OCPP commands.
If the call reaches a safety concern, emergency, refund decision, physical site problem, or result we can't confirm, we stop the automated path. The caller moves to your Level 2 or emergency route with the agreed context already collected.
Ontario is not one charging environment
Public corridors, community sites, residential buildings, and fleets need different questions, permissions, and handoff teams.
A driver beside Highway 400 or 401 needs a direct next step, not a lesson in network architecture. The workflow identifies the site, connector, session, and visible problem before it decides whether to guide, request an approved CPMS action, or escalate.
Ontario's ChargeON program is expanding public charging in smaller and Indigenous communities. A support plan has to preserve each operator's site rules and local escalation contacts while giving drivers a consistent first response.
Multi-unit charging involves residents, building owners, property managers, parking access, shared equipment, and account rules. We separate the driver's charging question from the issues that belong to the property team.
A depot or workplace has operating schedules, authorized users, site contacts, and different consequences when a session fails. The call flow follows those business rules instead of borrowing a public-charging script.
Ontario is expanding chargers through ChargeON community funding and provincial carpool and park locations. The province's current energy plan identifies ONroute charging along Highway 400 and 401. Natural Resources Canada also explains the extra decision-makers and technical layers involved in multi-unit residential charging.
A winter script shouldn't blame the charger before the facts are clear.
Winter-aware triage
Cold weather can increase vehicle energy use and charging time. Snow or ice can also make cables and plugs harder to handle, while plowing and snow accumulation can affect access to outdoor equipment. Those are different problems, and the support flow should not treat them as one charger fault.
We separate the vehicle, connector, station, site conditions, account, and network status. When the driver reports damaged equipment, blocked access, exposed components, or another unsafe condition, the workflow stops. A phone agent shouldn't coach someone through a physical hazard.
Natural Resources Canada's fleet guidance for Canadian winters notes that snow and ice can make charging equipment harder to handle even when the charger itself is rated for cold conditions. That distinction belongs in Ontario call scripts.
From ring to handoff
We don't start with a generic promise to automate support. We start with the decisions your team already makes.
EVCalls answers around the clock in English or Arabic and begins with the approved questions for that call reason.
The agent collects the caller details needed for support, along with the site, station, connector, session, and problem the driver can see.
The agent provides the approved instructions and uses only the CPMS data or actions included in the tested workflow.
If the result is uncertain, or the issue involves safety, an emergency, a refund, or an exception, the call moves to the route your team selected.
Language is part of operations
EVCalls currently supports English and Arabic. If your Ontario network requires French, we treat it as a real implementation item. The terminology, complete call paths, voice experience, edge cases, and human escalation coverage have to be built and reviewed before we call that language ready.
English and Arabic are available today.
Every additional language needs complete workflow testing.
Human escalation coverage must match the language promise.
We won't publish French readiness before that work is complete.
Canadian data planning
Our proposed Canadian deployment stores caller information on AWS infrastructure in Canada. We record a name and phone number when they're needed for a Level 2 handoff. We don't design the support flow to collect or process payment-card information.
Canadian hosting is only one part of the answer. Before launch, we document telephony, AI processing, subprocessors, backups, support access, retention, deletion, and every connected operator system. De-identified scenarios and missed vocabulary may be used to improve the model, while names and phone numbers are excluded from that improvement process.
Our privacy policy explains the current public commitments. Customer-specific requirements belong in the technical design and contract.
A focused Ontario pilot
Give us one common call reason, the current decision tree, CPMS interface, permitted actions, escalation contacts, languages, and a result you can judge. We will map and test that workflow before discussing a wider rollout.
Ontario operator questions
A useful evaluation depends on clear systems, languages, safety limits, and handoff rules.
Start with one call reason that your team already handles often and can explain clearly. That could be a first charge, finding the correct app, adding funds to a wallet, identifying the right station or connector, or following an approved cable-release path. We map the questions your agent asks, the information available in your CPMS, the steps the caller can safely complete, and the point where a person takes over. Emergency calls, refund decisions, and anything outside the approved path follow the escalation route you define. A narrow first workflow makes testing useful because both teams can see exactly what worked and what needs correction.
No. EVCalls does not communicate directly with a charging station and does not execute OCPP commands. It works through the API or webhook made available by the operator's charge point management system, commonly called a CPMS. If the CPMS supports an action and you authorize that action for the support workflow, EVCalls can request it through that interface. The CPMS remains responsible for communicating with the charger and returning the result. We review the available data, permissions, safety limits, and confirmation method before testing. If the result cannot be confirmed, the call moves to the human route instead of treating a request as a successful outcome.
A winter call should separate the vehicle, the charging equipment, the site, and the account before anyone assumes what failed. Cold weather can increase the vehicle's energy use and charging time, while snow or ice can make a cable or plug harder to handle. A site may also have an access, maintenance, or snow-clearing issue that software cannot resolve. We build these distinctions into the questions and next steps approved by the operator. EVCalls does not diagnose physical damage from a phone conversation. When the driver reports damaged equipment, unsafe conditions, inaccessible equipment, or an uncertain result, the workflow stops and sends the call to the correct human or emergency route.
Not automatically. EVCalls currently has complete support capability in English and Arabic. We do not present French as available until the terminology, call flow, voice experience, human quality review, and escalation coverage have been built and tested for the operator. That distinction is important in Canada because a translated greeting is not the same as a complete support operation. During scoping, you identify the languages your drivers need and the people who can review the operational vocabulary. If French is required, it becomes a defined implementation item with its own test cases and approval gate before any live use or public promise.
The proposed Canadian deployment uses AWS infrastructure in Canada for caller information. EVCalls records a caller's name and phone number when those details are needed for a Level 2 handoff, and the service is not designed to collect payment-card information. Before launch, the complete data flow still has to be documented. That review covers telephony, AI processing, subprocessors, backups, technical support access, retention, deletion, and the operator's own connected systems. De-identified scenarios, missed vocabulary, and edge cases may be used to improve the support model, while names and phone numbers are excluded from that process. The final commitments belong in the customer agreement and data-processing terms.
Prepare one common call reason and the real way your team handles it today. We need the current questions or decision tree, the CPMS interface involved, the information an agent may view, the actions the agent may request, and the point where the call must move to Level 2 support. Add the destination for emergencies and refunds, the languages included in the test, and the details the receiving person needs. We then agree on test cases and a clear pass or fail condition. The launch date is set after we review the workflow and technical interface, because different operators require different integration and approval work.
Bring one common call reason and the way your team handles it today. We'll use those details to prepare a practical demonstration.
Automated form delivery isn't active yet. Send one call reason and the way your team handles it today directly to EVCalls.
Don't include passwords, API keys, payment card details, or live caller records. See our Privacy Policy.