An EV Charging Support Company Should Understand the Network Behind Every Call

EVCalls is built for charging point operators and the teams responsible for driver support, network operations, customer experience, and service costs. It isn't a public helpline for individual drivers, and it doesn't operate a charging network of its own. A CPO brings its support number, business rules, escalation routes, and available system interfaces. The service is then shaped around that operating model. This focus matters because a useful answer depends on more than a general charging script. It depends on the operator's app, account process, CPMS information, permitted requests, refund boundary, safety path, and human support structure. Those details are different for every operator.

EVCalls was founded by software and electrical engineers with experience in the EV charging industry. That combination informs how the team looks at a support call. The conversation is one part of a larger system that may include a mobile app, customer account, payment workflow, charge point management system, communications link, charging station, vehicle, and human escalation team. EVCalls does not publish individual founder names, former employers, degrees, or career timelines until those details have been approved for public use. The current claim is deliberately limited to the engineering disciplines and EV charging experience confirmed by the business owner. It is a specific boundary, not a placeholder biography.

No. EVCalls is the support layer that speaks with drivers and follows the CPO's approved workflow. It does not connect directly to charging stations, own the operator's CPMS, or execute OCPP commands itself. When a workflow needs connected system information or an approved request, the available CPMS API or webhook defines what can happen. The operator controls permissions and escalation rules. The charging station and CPMS remain responsible for their own responses. This separation helps technical teams review the service accurately because it prevents a voice support capability from being described as charger control or universal protocol compatibility. Each integration is reviewed on its actual interface and permissions.

Ontario is the first Canadian market because EVCalls is focusing its commercial work instead of claiming a local presence everywhere. The province includes public corridor charging, municipal and community sites, workplaces, fleets, and multi unit residential charging, each with different support responsibilities. Ontario also brings practical operating questions about winter conditions, language planning, escalation coverage, and Canadian data handling. EVCalls does not claim an Ontario office, government relationship, or live deployment that has not been verified. The market focus means the team can prepare operator workflows around real provincial conditions while keeping each capability, location, and result tied to evidence.

The starting point is a focused pilot based on the CPO's real business flow. The teams first identify one support scenario, the available CPMS interface, permitted information and requests, escalation destinations, language needs, and the result that must be confirmed. The pilot can then show where the support flow works, where it needs adjustment, and which technical or operational questions remain open. EVCalls does not publish a fixed pilot duration, deployment date, price, automation rate, or customer result without evidence. The purpose of the pilot is to let both teams evaluate the workflow before making a broader commitment or a public performance claim.