Employee eligibility and enrolment
Follow the employer's approved invitation, credential, account, and location process without deciding who qualifies.
For CPOs serving employee charging programmes
Workplace EV Charging Support Has to Respect the Workday, Access Policy, and Facilities Team
Keep charging guidance useful without turning a technical call into an employer decision.
CPO buyer focus24/7 call availabilityMultilingual call supportEmployer policy stays employer owned
The call runs on more than charger time
A Charging Session Can Work While the Workplace Process Fails
Employee context
Eligibility, credential, schedule, vehicle, and observed issue
Workplace rules
Shared use, parking access, time limits, fees, and exceptions
Operating owners
CPO, programme, facilities, parking, security, and field routes
A workplace credential isn't a public charging account
The Charger Is Only One Part of the Employee's Question
Workplace EV charging support begins by identifying the employer programme, location, employee type, parking area, charger, credential, and schedule that govern the call. An account can be active while the employee lacks permission for that site, shift, stall, or shared station window.
We follow the guidance and connected paths the CPO approves. We also stop where the employer, facilities team, parking office, security contact, financial owner, or field team needs to decide. That keeps a charging answer from becoming an unsupported workplace promise.
This service is for CPOs with an approved operating relationship. It isn't a public helpline for employees at workplaces where EVCalls has no defined programme or access to the required support context.
Every issue needs the right kind of authority
Six Paths Separate Charging Help From Workplace Permission
The caller can cross several paths, but the workflow never borrows authority from the wrong team.
Shared station use
Explain approved booking, queue, time limit, notification, and vehicle move steps while leaving disputes with the policy owner.
Parking and site access
Keep gate, garage, security, visitor, and after hours permissions with the workplace team authorised to change them.
Account and session context
Use reviewed account or CPMS information, then separate a submitted request from a confirmed charging result.
Facilities and building service
Route site power, lighting, access equipment, physical conditions, and building operations to the right local team.
Field and urgent escalation
Stop routine guidance when damage, smoke, heat, exposed parts, collision, or another urgent condition is reported.
One station can answer to four schedules
The Workday Doesn't End at One Universal Closing Time
A session can continue after the employee's shift, the facilities desk, or the parking gate changes state. The workflow needs each clock before that happens.
Employee schedule
Arrival, break, shift end, hybrid attendance, and the time the vehicle must leave.
Parking access
Garage opening, gate permissions, visitor windows, move rules, and closing time.
Workplace coverage
Facilities, parking, security, programme administration, and financial team availability.
CPO response path
Level 2, connected system, field service, urgent route, and failed transfer fallback.
The right employee at the wrong site is still the wrong context
Five Identifiers Find the Policy Before the Next Step
A company can have several offices, credentials, parking arrangements, and charger groups. Hybrid employees, contractors, visitors, and fleet users can also follow different rules at the same address.
We collect only the approved context needed to select the correct workflow. If the site, programme, charger, credential, or session can't be matched, the call uses the CPO's missing context route instead of choosing a policy from a similar workplace.
- 1Employer and workplace location
- 2Employee, contractor, visitor, or fleet programme
- 3Parking area, stall, charger, and connector label
- 4Approved credential, account, or access method
- 5Vehicle and current charging session context
A shared charger doesn't create shared authority
Four Owners Keep Technical, Policy, and Site Decisions Separate
The CPO and employer approve the exact split for each workplace before support begins.
01
CPO support
Employee facing app and account guidance, reviewed system context, permitted connected requests, Level 2, and network escalation
02
Employer programme
Eligibility, enrolment, shared use policy, charging allowance, employee communication, and policy exceptions
03
Facilities and site
Parking access, building power, physical conditions, local service, security coordination, and workplace opening hours
04
Employee
Approved identification, visible station details, observed symptoms, safe caller steps, and compliance with workplace rules
Connected evidence doesn't approve an employee
The CPMS Can Describe Charging State, Not Employment Policy
Before we use a CPMS API or webhook for a workplace programme, the CPO reviews the interface, permissions, available fields, allowed requests, responses, and unavailable path. We don't connect directly to charging stations or execute OCPP commands.
The system may return an approved account, station, connector, or session detail. It doesn't decide employee eligibility, parking rights, workplace priority, a fee exception, building access, or who should move another vehicle.
Our CPMS integration review records the owner and meaning of each field so connected context supports the workplace rule without replacing it.
The call changes owner when
- The employee, workplace, programme, credential, charger, or session cannot be matched
- The caller needs new access or a workplace policy exception
- A shared station, reservation, queue, fee, or parking rule is disputed
- The CPMS result is unavailable, rejected, delayed, or unconfirmed
- A building, field, physical, electrical, or urgent condition is reported
Early shifts and late sessions expose missing owners
When a Workplace Team Is Closed, Its Authority Doesn't Move to Support
Our call coverage remains available 24/7. That schedule doesn't hand us the employer's access, parking, facilities, security, refund, or field authority. The CPO and workplace decide which approved guidance continues and which decisions wait for a named owner.
The coverage schedule and fallback should state who receives an early or late call, what happens when that route doesn't answer, and what the employee hears next. Urgent reports continue through their separate path.
A closed team needs a defined substitute or wait state
01
Approved routine guidance
02
Employer policy fallback
03
Facilities on call rule
04
Parking and security route
05
CPO Level 2 threshold
06
Failed contact message
Test the exceptions inside one real operating day
A Workplace Pilot Should Cross Opening Time, Peak Use, and Closing Time
The busiest workday reveals more than a generic charging script. It shows whether schedules, labels, policies, systems, and receiving teams agree.
The pilot should include
- An employee who is eligible but cannot complete the approved enrolment path
- A hybrid worker calling from a workplace they do not normally use
- A shared charger reaching its time limit while another employee is waiting
- A charging session that overlaps a parking, gate, or building closing time
- One unavailable charger compared with a wider site or building power report
- A CPMS request that is rejected, delayed, unavailable, or not confirmed
- A policy, facilities, refund, Level 2, field, or urgent route that does not answer
The receiving owner and failed transfer test confirms that every unresolved call ends with a known next step.
Questions the CPO and employer need to settle together
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