For CPOs serving municipal and community charging

    Municipal EV Charging Support Has to Answer the Public Without Speaking for the Municipality

    Give callers a known next step while public policy and site decisions stay with their authorised owners.

    CPO and municipal buyer focus24/7 call availabilityMultilingual call supportPublic authority stays municipal owned

    One caller can report three different services

    The Charger, Public Site, and Municipality Don't Own the Same Answer

    Charging network

    Account, session, connector, system context, and CPO escalation

    Public location

    Parking area, access, lighting, signs, snow, damage, and facility service

    Municipal service

    Public policy, programme rules, exceptions, accessibility review, and civic response

    Classify the public request before touching the technical path

    Three Questions Stop a Charging Call From Becoming the Wrong Public Service

    Municipal EV charging support first asks whether the caller needs help with the charging service, is reporting a condition at the public site, or needs the municipality to explain or change a rule. The same charger location can produce all three calls, but their owners and evidence are different.

    We identify the public place and charging asset before following the CPO's approved guidance. Then we move parking, public policy, accessibility review, facilities work, financial decisions, and urgent conditions to the owners chosen by the CPO and municipality. We don't present EVCalls as a government office or public authority.

    01

    Is this a charging service question?

    Use the approved app, account, payment, session, CPMS, or Level 2 path.

    02

    Is this a public site report?

    Record the visible location and condition for facilities, maintenance, accessibility, field, or urgent review.

    03

    Is this a municipal decision?

    Send policy, parking, fee, exemption, penalty, or public programme questions to the authorised civic owner.

    Public language needs a service category

    Six Call Types Give Every Report a Defined Starting Owner

    A single call can cross categories, but each remaining decision still travels to the team with the right authority.

    Charging service question

    App, account, wallet, authorisation, session, station status, or another approved CPO support path.

    Parking or public policy question

    Posted hours, charging limits, fees, exemptions, penalties, or another decision owned by the municipality.

    Accessibility barrier report

    A blocked route, reach or clearance concern, snow, object, or other observed barrier needing a public site owner.

    Weather and site maintenance

    Snow clearing, surface conditions, drainage, vegetation, or another physical condition outside software support.

    Lighting, signage, or facility issue

    Missing or damaged signs, dark areas, gates, building power, or public facility equipment.

    Damage or urgent condition

    Impact damage, exposed parts, smoke, fire, heat, collision, or another report that stops normal guidance.

    A city name isn't enough to find a public charger

    Four Layers Connect the Caller to the Correct Civic Location

    Different facilities can reuse parking, entrance, stall, and charger numbers. The record needs both the public language on site and the technical references behind it.

    01

    Public place

    Municipality, facility, street or parking location, entrance, level, and nearby public label

    02

    Charging asset

    CPO, station, stall, charger, connector, QR code, phone label, and CPMS reference

    03

    Operating rules

    Posted hours, parking and charging limits, payment path, closures, and approved public wording

    04

    Receiving owners

    CPO Level 2, municipal service, parking, facilities, accessibility, field, finance, and urgent routes

    Public accountability starts with named authority

    Five Owners Can Participate Without Passing Decisions Sideways

    The operating agreement records which organisation speaks, acts, reviews, and closes each kind of public report.

    CPO support

    Owns approved charging guidance, account and session context, connected requests, technical escalation, and the charging service record.

    Municipal programme

    Owns public policy, programme instructions, exceptions, service standards, and the municipality's approved public response.

    Site and facilities

    Owns physical access, lighting, signage, power, snow and surface conditions, maintenance, and local service coordination.

    Parking or enforcement

    Owns parking permissions, time limits, posted restrictions, penalties, and decisions the charging system cannot make.

    Public caller

    Supplies the location and visible details the workflow requests, follows safe steps, and receives the confirmed next owner.

    Describe the barrier without deciding compliance

    An Accessibility Report Needs the Exact Place, Obstacle, and Public Owner

    A caller may describe a blocked route, reach or clearance concern, snow, an object, damaged equipment, or another obstacle at a municipal charging location. We collect the approved site and charger labels, the caller's observed condition, and whether an urgent risk is present.

    We don't determine legal compliance from a call or promise a site change. The municipality chooses who reviews accessibility and physical site reports, which details that owner receives, and what the caller hears while the condition is being assessed.

    The report should distinguish

    • The exact public location and route involved
    • The stall, station, connector, sign, or feature identified
    • What the caller observed and when
    • What came from the caller versus a connected system
    • Whether damage or another urgent condition was reported
    • The municipal or site team responsible for review

    A system result can't issue a civic decision

    CPMS Evidence Belongs to the Charging Service, Not Municipal Authority

    For a municipal programme, the CPO first reviews which CPMS API or webhook fields and requests can support the call. EVCalls doesn't connect directly to charging stations or execute OCPP commands.

    An approved interface can add account, station, connector, or session context. It can't interpret a bylaw, grant a parking exception, judge accessibility compliance, dispatch municipal maintenance, waive a fee, or close a public complaint.

    During the connected system review, we record what each response proves and which public owner takes over when the system is unavailable or the caller needs a municipal decision.

    The technical path stops when

    • The public site, station, connector, account, or session cannot be identified
    • The caller needs a policy interpretation, exception, enforcement, or public decision
    • An accessibility, facilities, parking, maintenance, or site condition is reported
    • The connected request is rejected, delayed, unavailable, or unconfirmed
    • Damage, exposed parts, smoke, fire, heat, collision, or another urgent condition appears

    Public chargers stay open after some civic teams close

    A Closed Municipal Desk Still Needs an Approved Caller Answer

    EVCalls provides 24/7 call availability, but the municipality and CPO decide what can continue after a public service, facilities, parking, finance, or field team closes. Charging guidance stays within its approved system and policy limits.

    The after hours owner map states which reports reach an on call contact, which urgent route bypasses routine handling, which items wait, and what happens when the first destination doesn't answer.

    Every closed route needs one recorded outcome

    01

    Guidance completed

    02

    CPO Level 2 accepted

    03

    Municipal on call accepted

    04

    Urgent route followed

    05

    Named wait state given

    06

    Fallback used after no answer

    Test several public settings inside one municipality

    A Municipal Pilot Should Prove the Location Changes More Than the Address

    Community sites differ in how people find the charger, park, pay, report a barrier, and reach the team responsible for the property.

    The municipal review should test

    • A public parking facility with controlled access or operating hours
    • A recreation or community facility with shared parking and local contacts
    • A street or open lot location where the caller relies on signs and charger labels
    • A site with an accessibility, snow, lighting, or physical maintenance report
    • A location whose municipal service route is closed when the charging call arrives
    • A charger whose CPMS context is rejected, unavailable, delayed, or unconfirmed
    • A routine, financial, field, policy, or urgent handoff whose first contact fails

    The handoff and failed route test confirms that the public caller, CPO, and municipal owner receive the same known next step.

    Questions CPO and municipal teams should answer together

    Frequently Asked Questions

    Start With the Municipality Whose Public Sites Create the Most Different Calls

    We'll map the public labels, charging paths, municipal owners, physical reports, schedules, and failed routes across its real locations.

    Get Started

    Plan a Working Demo

    Bring one common call reason and the way your team handles it today. We'll use those details to prepare a practical demonstration.

    Built around one real support workflow
    Multilingual call support scoped to your network
    CPMS access reviewed before integration
    A focused pilot with agreed test conditions

    We'll use these details to arrange your demo and respond to your request. See our Privacy Policy.