Canadian CPOs need driver call paths that fit their own apps, accounts, and receiving teams. The same short complaint can lead to several different decisions. We begin with the questions that distinguish those paths, rather than a promise to fix every issue in seconds.
App access and wallet questions need different instructions
For app access, review the app name, account steps, and how the caller identifies the correct network. Wallet guidance should follow your approved instructions. Payment processing stays with your payment systems, and refund decisions go to your assigned team.
Test the wording in the language options you choose. A caller should be able to follow the full exchange, including the message used when a human takes over.
A session start and a connector release need evidence
When a session will not start, the conversation should gather the station, connector, and visible message before selecting guidance. The CPMS supplies the system information available to the call. Missing information changes the next step.
For a stuck connector, we follow the operator's reviewed instructions and permitted CPMS request path. The CPMS communicates with the charger. A submitted request is not proof of release, and a report of damage follows the urgent route rather than repeated troubleshooting.
The fifth path is a person
Define which technical exceptions, refunds, and urgent reports reach a human. Include the receiving team's hours and backup destination. For networks across time zones, test the schedule at the moment the call occurs, not just during your office hours.
We can use these decisions to scope Canadian operator support around your network, systems, and receiving team.