EV Charging Support Security Starts With Knowing Where Every Call Detail Goes

EVCalls records a caller's name and phone number when those details are needed for an approved Level 2 handoff. The rest of the required context depends on the operator's workflow and may include the stated call reason plus the site, station, connector, account, or session identifiers needed to understand the issue. The CPO decides which fields are necessary for each path before launch. That review should also identify fields the agent must not request. EVCalls is not designed to collect broad identity profiles simply because a driver called. The goal is to gather enough approved context to support or transfer the call without turning the conversation into an unnecessary data collection exercise.

No. EVCalls is not designed to collect or process payment card information. The agent can explain wallet or account steps that the charge point operator has approved, but it should not ask a caller to read a card number, security code, or other payment credential aloud. Refunds, disputed charges, and financial exceptions move to an authorized human route defined by the operator. The workflow review should test those boundaries with realistic call examples, including a caller who offers payment details without being asked. The agent needs a clear interruption and escalation response so sensitive financial information does not become part of the normal support record.

A Canadian data location requirement must be verified across the complete deployment before it becomes a contractual promise. The proposed Canadian architecture uses AWS infrastructure in Canada for caller information, but server location is only one part of the flow. Telephony, AI processing, logs, backups, monitoring, support access, subprocessors, and the operator's connected systems can each affect where information travels or who can reach it. EVCalls maps those services with the CPO before launch and records the approved commitments in the customer agreement and data processing terms. Until that review is complete, we do not present Canadian hosting as an absolute guarantee that every data element stays in Canada.

No universal recording or transcription setting is published for every EVCalls deployment. The operator and technical team need to decide what is required for the approved workflow, caller notice, quality review, escalation, and record keeping. That decision should identify whether audio, a transcript, a structured summary, or only selected fields are retained. It should also define the purpose, access roles, storage location, retention period, deletion process, and behaviour when recording or transcription is unavailable. EVCalls does not use an undefined default as a substitute for that review. The final setting belongs in the deployment design and customer terms before live calls begin.

EVCalls may use de-identified scenarios, missed vocabulary, and unusual edge cases to improve the support model, while caller names and phone numbers are excluded from that improvement process. That is the current business rule, but the technical controls still need to be verified for each deployment. The review should show how identity is separated, which material remains, who can access it, how long it is kept, which vendors process it, and whether the CPO has contract-specific choices. A general statement about removing names is not enough by itself. The operator should be able to trace the improvement path and approve the controls before its call material enters that process.

A CPO security review should settle the data categories, purposes, system owners, locations, access roles, subprocessors, retention rules, deletion steps, incident contacts, and model improvement choices for the pilot. It should also document the CPMS fields EVCalls may read, the requests it may submit, the evidence that confirms a result, and the context permitted at human handoff. The technical test needs normal calls and failure cases, including unavailable systems, rejected requests, missing identifiers, and transfers that do not complete. Any requested certification, legal alignment, encryption detail, or residency promise should map to evidence and approved contract wording. Unknown controls stay open instead of being answered with a marketing claim.