Operations teams spend a surprising share of their day translating questions into filters. "Which DC chargers in Punjab lost more than four hours of availability this week, and what were the fault codes?" is a perfectly ordinary question that takes four screens and a CSV export to answer.
zevOS Copilot answers questions like that directly, and — this is the part that matters — returns the underlying records alongside the answer, so you can check it rather than trust it.
What it can answer today
- Availability and downtime, by charger, site, region or period
- Session and energy questions, including comparisons between periods
- Revenue, realisation per kWh and settlement questions
- Fault frequency and grouping — which units fail, how often, with which codes
- Driver and fleet consumption patterns
What it deliberately does not do
Copilot does not issue commands to chargers, change tariffs, approve settlements or move money. It reads. Anything with a consequence stays behind the existing permissioned workflows, where it is audited.
It also respects the same scoping as everything else: a staff member restricted to certain station groups gets answers about those stations only, and a partner gets answers about their own sites.
Availability
Copilot is rolling out in preview. Talk to us if you would like your account included.