CoOperator went live in March 2026 as the AI agent inside the AMPECO operator dashboard. It works on each operator’s own network data: it investigates failed sessions and offline chargers from the records, looks up settings, and makes changes across the network once an admin confirms.
The value operators get from it day to day is why AMPECO keeps investing in CoOperator. Their teams kept raising the same needs, and the October release goes deeper on three of them: investigations that start from the full record, context that carries between conversations, and answers shaped by the page an admin is on.
Investigations that start from the full record
A typical case: A driver calls because a session wouldn’t start. Overnight, a charger at a busy location went offline. Before anyone on the support team can explain either one, they need the session data, the authorization, the charger’s fault history and its network status.
CoOperator collects all of that before it answers. For a session, an authorization, a hardware fault or a lost connection, it pulls the complete evidence. It then works through known failure types, from a session that never started to an unexpected price.
Its answers stay tied to that evidence. Any status, amount, name or ID it reports comes from data it looked up for the question in front of it. When the data is missing, it says so. Offline time, for example, is read from the charger’s recorded network status and downtime, never inferred from gaps in the log.
When that driver calls about the session that wouldn’t start, the support agent can explain what went wrong while the driver is still on the line.
The same conversation can cover the platform itself, such as what a status means or which settings apply, answered from CoOperator’s built-in knowledge of each area.
As CoOperator works, the sidebar shows each step in plain language. When the fix is a change in the operator dashboard, such as a configuration update, CoOperator can make it too. A confirmation card shows exactly what will change, and nothing happens until the admin confirms. If a request covers several charge points and some updates are rejected, CoOperator lists which went through, which didn’t and why.
Context that carries from one conversation to the next
A typical case: On Tuesday, an admin looks into a tariff problem at an airport location. On Thursday, the problem is back.
The admin can ask CoOperator “what did I find on Tuesday about the airport tariff?” and carry on from there. The answer links to the earlier conversation, which opens in the sidebar. Every conversation is saved with a short summary and a descriptive title, so an admin’s own earlier investigations are easy to find in their history. This part works for every admin, with nothing to switch on.
With memory switched on, CoOperator also keeps a short personal memory for each admin: their role, their preferences and the terms they use. An admin who says “by site I mean location group” or “I prefer MWh” gets answers in those terms from then on.
Each admin controls their own memory and can ask CoOperator to remember or forget something at any point. The CoOperator memory tab in My account shows everything CoOperator holds about them. From there, they can delete single items, clear it all or go back to an earlier version, and no other admin can see their memory. Personal memory is limited to how an admin works. Drivers’ personal data and investigation results are never stored in it, and anonymising a driver removes that driver’s details from every memory and every earlier version. Conversations left untouched for 90 days are condensed to their summary, which can still be opened and continued.
When the tariff issue comes back on Thursday, the admin starts from Tuesday’s findings rather than running the investigation again.
Answers shaped by the page you’re on
A typical case: An admin filters the session list down to one location and last week’s failed sessions, and the list comes back empty.
With contextual assistance switched on, CoOperator takes into account the page the admin is on, so a question like “why is this list empty?” gets an answer with their filters in view. On a list, it sees the search, the filters and the sorting. On a record, it sees details such as a charge point’s network status or a session’s state, so a question asked from a session page needs no session ID.
What CoOperator sees of the page follows the same permissions as the rest of the operator dashboard, so it never sees records the admin can’t access.
The admin asks the question where it comes up, without copying IDs or describing filters first.
Questions to start with
The quickest way to judge the October release is to bring CoOperator the questions your team already asks. A few to try, grouped by the three areas above:
Investigations and changes
- Why didn’t session [ID] start?
- Why has charger [ID] been offline since last night?
- Which locations had the most failed sessions this month?
- Set [setting] to [value] on all charge points at [location]. (example still being confirmed with Product)
Earlier work
- What did I find last week about the [location] tariff?
- Remember that by site I mean location group. (needs memory switched on)
- What do you remember about me? (needs memory switched on)
The page you’re on (needs contextual assistance switched on)
- Why is this list empty?
- Why is this session failing? (asked from the session’s page)
- What does this status mean? (asked from a record page)
Switching on the new options
Memory and contextual assistance are off by default, and AMPECO switches them on per operator. Ask your Account Delivery Manager to turn them on for your team. Everything else in the October release is already available wherever CoOperator is in use.
Further CoOperator changes appear in our monthly platform updates. If you’re evaluating charging management platforms, book a demo to see CoOperator work through your own scenarios.
