Charging account and session
App access, charger identity, authorisation, session state, approved CPMS evidence, and permitted connected requests.
For CPOs serving utility sponsored charging programmes
Utility EV Charging Support Keeps Programme Questions From Reaching the Wrong Owner
Give callers one approved answer while keeping charging, programme, utility, vendor, and urgent decisions with the teams that own them.
CPO programme focus24/7 call availabilityMultilingual call supportCanadian call data storage
A utility branded call can cross three contracts
The Caller Hears One Name. The Workflow Still Needs Every Owner.
One approved voice
Programme greeting, language, caller explanation, and privacy script
Separate evidence
Programme records, CPMS context, authoritative outage source, and vendor status
Known destination
CPO, utility, billing, installer, field, Level 2, or urgent team
The first answer is an ownership decision
One Programme Number Can Hide Several Different Services
Utility EV charging support starts by identifying whether the caller needs charging help, a programme answer, an electricity account owner, a managed charging route, or a physical service vendor. The shared brand shouldn't make those responsibilities interchangeable.
We build the questions, system evidence, caller wording, and escalation around the CPO and utility's approved operating model. EVCalls can guide an app or account step, use reviewed CPMS context, and submit a permitted request through an API or webhook when the workflow allows it.
We don't decide utility eligibility, promise an incentive, interpret an unapproved rate, diagnose the grid, connect directly to a charging station, or execute OCPP commands. When the answer belongs elsewhere, the call moves with the limited context that owner needs.
The caller's question chooses the operating lane
Six Call Lanes Stop Policy, Charging, and Field Work From Blurring Together
Each lane has its own approved source, stop rule, receiving owner, and caller message.
Programme enrolment and eligibility
Published steps, required records, application status, exceptions, and the utility owner who makes the decision.
Rates, incentives, and billing
Approved rate and incentive information without promising eligibility, a rebate, bill savings, or a financial outcome.
Managed charging participation
Programme status, caller choices, approved settings, event context, and policy questions that require the programme team.
Outage and communications
Separate an authoritative utility outage from a CPMS, communications, charger, site power, or still unknown condition.
Installation, warranty, and field work
Route physical inspection, installation, equipment warranty, site electrical work, and maintenance to the assigned vendor.
Identify the programme before selecting the script
Four Identity Layers Keep One Utility's Rules Out of Another Programme
The programme name, participant record, charger context, and final owner have to agree before the workflow uses a policy answer or connected request.
Programme
Utility, programme name, service area, support brand, rule version, and effective date
Participant
The limited caller, account, enrolment, vehicle, or premise reference approved for this workflow
Charging context
Site, charger, connector, app, account, session, CPMS fields, and observed message when relevant
Decision owner
CPO, utility programme, billing, managed charging, installer, field, Level 2, or urgent team
Programme answers need release control
A Script Becomes Risky When Nobody Knows Which Rule Is Current
Rates, incentives, enrolment steps, eligible equipment, managed charging choices, service areas, and office routes can change. We tie each approved answer to its source, effective date, change owner, and fallback wording.
A future rule shouldn't appear early, and an old rule shouldn't remain after its replacement takes effect. The utility programme owner approves policy wording. The CPO approves charging operations, CPMS access, and technical routing.
When a published rule doesn't answer the caller's situation, we don't fill the gap. The workflow records the exact question and sends it to the person authorised to decide the exception.
Effective date
When the answer becomes valid and when the prior version stops
Approved source
The programme document, system field, or owner that supports the caller answer
Change owner
Who can approve a rate, eligibility, incentive, script, route, or system change
Fallback wording
What the caller hears when the rule, source, or receiving team cannot answer
A managed charging record separates
- The programme and participant identity
- The vehicle, charger, app, or account involved
- The event or message the caller observed
- What the approved programme system confirms
- Which participation choice is permitted
- Which cause, saving, or technical result remains unknown
Participation status is not a charger diagnosis
Managed Charging Questions Need Programme Context and Technical Evidence
We can explain approved participation steps, settings, event messages, or opt out paths when the programme provides them. We don't promise savings, predict a bill, assign a grid cause, or claim that the charger or vehicle responded without a confirmed source.
A programme policy question stays with the utility owner. An app, account, CPMS, communications, charger, or installation issue moves through the technical or field route selected by the CPO.
Any connected action still follows the reviewed API or webhook boundary. EVCalls doesn't connect directly to the charging station.
A dark screen doesn't name the failed system
Outage, Communications, CPMS, Charger, and Site Power Need Separate Evidence
A caller observation can show that something is unavailable. It cannot, by itself, prove whether electricity service, site equipment, communications, the CPMS, the charger, or another condition caused it.
We collect the programme, location, affected equipment, timing, visible message, surrounding conditions, and approved system context. Only an authoritative utility source can confirm a utility outage when that source is included in the workflow.
We don't coach callers through panels, wiring, damaged equipment, or another physical hazard. Smoke, fire, exposed parts, heat, severe damage, or an urgent electrical concern moves immediately to the approved urgent path.
The receiving team needs to know
- 01
What the caller observed
- 02
Which site or premise is involved
- 03
Which equipment appears affected
- 04
What the CPMS or programme source reports
- 05
Whether a utility outage is actually confirmed
- 06
Which physical or urgent condition changed the route
A useful outcome record includes
- Programme and rule version used
- Issue category and approved identifiers
- Guidance and system evidence reviewed
- Connected request state when applicable
- Final owner and transfer result
- Unresolved question without an invented cause
Reporting begins with a shared vocabulary
A Handoff Record Should Preserve the Unknown, Not Hide It
The CPO and utility define the outcome categories and required fields before the pilot. That keeps a programme question, unconfirmed charger issue, confirmed outage, vendor route, failed transfer, and urgent escalation from becoming one vague support label.
EVCalls records only the caller and operational details approved for the workflow. Delivery to a CRM, case platform, or reporting system requires a reviewed integration and field map. We don't claim a current production CRM connection.
The data flow and retention review shows where approved call information is stored in Canada and which fields reach another owner.
One caller can touch five contracts
Ownership Has to Be Decided Before the Transfer Begins
Each owner receives the identifiers, evidence, completed guidance, remaining question, and caller message relevant to that decision. The caller shouldn't have to rebuild the case after every boundary.
The escalation and failed transfer design defines a second destination and caller answer when the first route does not respond.
CPO operations
Charging accounts, CPMS access, session evidence, approved connected requests, and technical escalation
Utility programme
Eligibility, enrolment, incentives, rates, managed charging rules, and programme exceptions
Installer or field vendor
Installation, warranty, physical inspection, site electrical work, and equipment service
Financial owner
Rebates, disputed amounts, credits, utility billing, and other authorised money decisions
Level 2 or urgent owner
Unconfirmed technical results, safety language, emergency routes, and failed contact fallback
Test the seams, not only the happy path
A Pilot Should Prove Which Organisation Answers Each Question
Bring the programme rules, system access, owners, vendor routes, office schedules, and unanswered cases the live programme will actually use.
The utility programme review should include
- A caller who names the utility but not the programme
- A charging session issue that belongs to the CPO rather than the programme desk
- An eligibility or incentive question outside the approved words
- A managed charging event with an unconfirmed vehicle or charger result
- A blank charger screen with no authoritative outage confirmation
- An installation or warranty problem that needs a vendor route
- A programme rule change with a future effective date
- A transfer that fails after the caller has already repeated the issue once
The after hours ownership test repeats those routes when utility, vendor, or programme desks are closed.
Questions CPO and utility 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