OCPP Support That Keeps Your CPMS in Control

OCPP support starts with a clear split of responsibilities. OCPP, the Open Charge Point Protocol, connects a charger with its management system. We connect EVCalls to your charging point management system, or CPMS, through approved APIs or webhooks. Your CPMS manages the charger connection.

That distinction shapes what a call can do. A driver reports a stuck cable or a failed start. We follow your questions, use the information your CPMS makes available, and request the next permitted step. The charger protocol version alone doesn't tell us whether that step is available through your platform.

An accepted request isn't a confirmed result. The cable still needs to release or charging needs to begin. We build the call flow around the result your CPMS returns and the checks your team approves. If a result is missing, stale, or unclear, the flow needs a defined next step.

In an illustrative cable release workflow, we first agree how to identify the station and connector, check the session context, and apply your safety rules. An approved release request passes through the CPMS. We then confirm the available result and the caller's situation before closing the call. Include this scenario in your pilot so your team can review each decision.

Bring your CPMS documentation and the calls that are hard to resolve. We'll map the information each question needs, who approves each request, and when another attempt should stop. We'll also agree what your L2 team needs to receive when a person takes over.

Test the difficult calls too. Include a normal response, a rejected request, a timeout, and a caller whose report doesn't match the system. You can then review whether the call followed your rules. That gives your operations and technical teams a shared basis for deciding the next step.