See How the EV Charging Support Workflow
Moves From Call to Next Action

The operator needs to provide the way the call is handled today. That includes the questions an agent asks, the information needed to identify the site and session, the CPMS interface involved, and any instructions the driver may safely follow. We also need to know which actions an agent may request, how a successful result is confirmed, and which calls must move to a human. Emergency contacts, refund routes, Level 2 destinations, supported languages, and the context required during transfer are part of the same review. Starting with the real decision tree keeps the workflow tied to the operator's policies instead of assumptions about how every network works.

EVCalls uses the identifiers and questions approved by the operator. Depending on the network, that may include a site name, address, station label, charger number, connector number, or information from the driver's account or session. The exact method depends on what the operator displays at the site and what its CPMS makes available. The workflow should not continue to a system action until it has enough information to identify the intended equipment and session. If the caller cannot provide the required details, or the connected system returns an uncertain match, the call follows the operator's fallback instead of guessing which charger the driver means.

EVCalls sends the request through the operator's charge point management system, not to the charging station itself. The CPMS exposes an API or webhook, applies its own permissions, communicates with the charger, and returns the available result. During setup, the operator decides which actions belong in the support workflow and under what conditions they may be requested. EVCalls does not claim compatibility until the required interface and permissions have been reviewed and tested. It also does not treat a submitted request as proof of success. The workflow needs a response or another agreed confirmation signal before telling the driver that the action worked.

The call follows a fallback defined before launch. EVCalls can continue with approved questions and driver instructions that do not depend on the unavailable system, but it should not invent station status or claim that an action succeeded. The workflow can explain that the result cannot be confirmed, collect the context needed by the next team, and transfer the caller to the operator's Level 2 route. The operator decides whether different call reasons use different fallbacks. A first-charge question may still have useful steps, while an uncertain cable-release request or safety concern may need an immediate handoff. These paths are tested during the pilot rather than decided during a live call.

The handoff can include the context agreed with the operator, such as the caller's name and phone number, the stated reason for the call, the site or charger identifiers collected, and the steps already completed. The purpose is to prevent the driver from starting the conversation again and to help the Level 2 person see why the transfer happened. The exact information package depends on the operator's systems, privacy requirements, and transfer method. EVCalls does not currently claim a universal CRM or ticketing integration. If a customer needs one, that connection and its field mapping become part of the technical scope and testing plan.

They move to the human route defined by the operator. EVCalls can recognize the issue category, stop the normal troubleshooting path, collect only the information approved for that situation, and transfer the caller to the correct destination. It does not make refund decisions, process payment-card information, or coach a driver through damaged or unsafe physical equipment. The operator supplies the emergency and financial escalation rules, including what the caller should hear while the transfer is happening and what context the receiving person needs. Those routes are tested as first-class scenarios because a workflow is not ready if it handles the common calls but fails at the moments where a person must take responsibility.