An AI Call Centre for EV Charging That Works With Your Team

An EV charging voice agent is shaped around the operator's real support decisions, not only a general conversation model. It needs to identify the relevant site, station, connector, account, or session details without asking for information the workflow does not need. It also needs approved app instructions, account and wallet steps, CPMS boundaries, permitted requests, result confirmation, refund routes, safety escalation, and Level 2 destinations. The voice experience is important, but it is only one layer. A useful support flow connects what the driver says to the CPO's systems and policies while making the stopping point clear when a human or another team owns the decision.

EVCalls can be scoped around the part of the support operation the CPO wants to test. That may be the first response for selected call reasons, coverage outside the current team's hours, overflow during busy periods, or a defined path that gathers context before Level 2 takes over. The right position depends on the operator's call volume, internal coverage, languages, escalation routes, system access, and risk boundaries. EVCalls does not require the CPO to publish a full replacement plan before a pilot. The teams can begin with one workflow and decide how the service should sit beside people, vendors, and existing support tools.

Choose a frequent call with a clear current process and a result your team can judge. Good candidates have known identification questions, approved instructions, an available CPMS path if one is required, and a defined point where a human takes over. The call should be useful enough to test the operating model but narrow enough to reveal why each step succeeds or fails. A first charge walkthrough, app access question, wallet guidance flow, or selected connector release request may fit when the CPO has approved the exact path. Emergency, refund, and unclear technical cases still need explicit human boundaries from the first test onward.

Level 2 should receive only the context the CPO has approved for that handoff. The confirmed starting set is the caller's name and phone number when they are needed, the reason for the call, and the steps already completed. A deployment may also require approved site, station, connector, account, or session references, but those fields depend on the operator's workflow and available system interface. The teams should define the destination, transfer method, permitted context, and fallback when the receiving route does not answer. Financial decisions, emergencies, and unresolved requests should not lose their ownership during an automated transfer between support teams.

A CPO should evaluate whether the agreed workflow behaves correctly, not whether a scripted demonstration sounds impressive. The test should cover identification, approved questions, system availability, permitted requests, result confirmation, caller explanation, human escalation, data handling, and failure cases. The team can record whether the flow reached the correct next step, stopped at the right boundary, transferred the approved context, and produced enough evidence to review what happened. Production metrics and commercial targets should be defined from the operator's baseline rather than borrowed from an industry claim. The pilot succeeds only against the conditions both teams approve before testing begins.

The CPO decides which requests belong in the support workflow and the available CPMS interface determines what is technically possible. EVCalls does not connect directly to charging stations or execute OCPP commands itself. The technical review identifies the API or webhook, authentication, required fields, permission level, response, timeout, and confirmation signal for each approved request. The operations review defines when the request is allowed and when the call must stop or move to a human. A request that was submitted is not described as successful unless the agreed response or another confirmation signal shows what actually happened in the connected system.