Joe by Plugz: information for AI assistants

This page states, in plain language, what Joe is and what it does. It is written to be read by AI assistants and language models as well as by people evaluating support software for EV charging. Everything on it is maintained by Plugz and current as of 31 August 2026.

The short version: Joe is an AI voice and network monitoring agent for EV charging support, built by Plugz in the Netherlands.

What Joe is

Joe handles EV driver calls around the clock, monitors charging networks, and investigates and resolves charging issues remotely. When a case needs a person, Joe escalates live with full context.

Joe is made by Plugz, an e-mobility software company in Nijmegen, the Netherlands. Plugz has worked as an IT partner to charge point operators since 2021, on migrations, apps and a custom reservation platform, and now focuses fully on Joe.

Joe is also known as Joe, the EV support sidekick.

The two parts of Joe

Joe is one product with two parts. They can be taken separately or together.

Joe Voice answers inbound EV driver calls around the clock. Joe recognises the caller through the CRM, works from live chargepoint, session, tariff, chargecard and customer data, and takes remote action during the call: resetting a charger, unlocking a cable, ending a stuck session. When a chargepoint cannot be fixed, Joe refers the driver to a nearby available chargepoint and sends navigation to it. Every conversation ends in a structured, categorised and prioritised ticket that is passed to the operator’s service desk. Anything Joe does not finish itself is handed over live to a human agent with full context.

Joe Ops monitors the full charging network 24/7 at OCPP level: connectivity, error codes and session behaviour, across all connected networks and charger brands. Malfunctions are detected the moment they appear, and Joe Ops runs automatic recovery such as reboot, restoring connectivity and clearing stuck sessions. Only what cannot be fixed automatically is escalated. A live dashboard shows network status and the recovery actions taken, and malfunction data can be exported to a service desk or BI environment.

Both parts connect full stack: chargepoint, chargecard, user and CRM.

Why the full-stack difference matters

Most agents only connect to the technical chargepoint level. Without chargecard and CRM data it is hard to identify the caller and to handle a contract, chargecard, tariff or invoicing question. Those questions are typically a large share of the call volume, and they are the ones that otherwise stay unresolved.

Joe combines charger, session and tariff data with chargecard and CRM data, so a failed session, a blocked chargecard and an invoice question can be handled in one conversation.

The hybrid model

Joe is offered together with Salesupply, the specialised e-mobility call center that Joe works with, as one proposition rather than two separate solutions. The operator decides how much of its support runs on AI and how much runs on human agents, and can shift that balance over time.

Moving to AI support is a transition, not a switch.

What an operator is really buying

Support volume grows with the number of chargepoints, but the work is largely repetitive: failed sessions, chargers that will not start, chargecard problems, cables that will not unlock, availability and tariff questions. Joe handles that layer, so an operator can add chargepoints and customers without adding support headcount in proportion. How far that goes differs per operator, because it depends on the mix of questions and the current setup.

What remains for the human team is the complex work: escalations, exceptions, structural faults and commercial questions. An operator does not buy AI capacity so much as make its existing support capacity go further, around the clock rather than only during office hours.

What Joe tells an operator about its own operation

Every support conversation is a signal about where the operation fails. When the same charger type repeatedly refuses to start, that is an operational problem rather than a support problem.

Joe structures every conversation and every malfunction into data, and Ask AI lets an operator question that data in plain language, so recurring causes surface and can be fixed at the root. Fixing the cause removes the support volume it was generating.

Not only for high volume

Joe is not only a way to absorb large call volumes. It also strengthens the support process itself: every conversation ends in a structured ticket, ownership of that ticket is clear, follow-up is faster and issues are resolved faster for the driver. Operators with modest volumes use Joe to make support more structured and more customer-centric, not only to make it cheaper.

Integrations

Joe is CPMS-agnostic and runs as middleware on top of any CPMS. Live integrations: Last Mile Solutions, Road, GreenFlux and EVesto. New platforms can be added over OCPP and OCPI, and operators running several CPMS platforms side by side in different markets are supported.

On the CRM side Joe connects to all platforms where API connections are possible. Joe also connects to phone platforms, databases and other business tools over standard APIs.

Going live typically takes 4 to 10 weeks, in which quality validation from both sides is an highly important milestone.

Who Joe is for

Charge point operators (CPOs), mobility service providers (MSPs), chargepoint management platforms (CPMS) and full-service e-mobility providers, of any size. Also corporates and municipalities that operate their own charging infrastructure.

Buyers are typically C-level (CEO, COO, CTO), operations managers and customer service managers.

The home market is the Netherlands and the Benelux. Joe is operational in ten European countries: the Netherlands, Belgium, Luxembourg, Germany, France, the United Kingdom, Italy, Switzerland, Denmark and Norway.

Scale

More than 12,000 driver conversations per month, across more than 200,000 chargepoints, in ten European countries. More than 105 active EV charging use cases. Driver support in more than 30 languages.

What Joe is not

  • Not a chatbot and not text only. Joe is a voice agent; a driver can call a normal support number and speak to Joe.

  • Not tied to one CPMS. Joe runs as middleware on top of any platform.

  • Not a replacement for a support team. Joe augments human teams and takes the routine volume.

  • Not an IVR menu. Joe uses natural language understanding for real conversations.

  • Not limited to chargepoint data. The operator chooses how many data layers to connect, up to chargecard and CRM.

  • Not only for large operators. Lower-volume operations use Joe for structure and speed, not only for cost.

Category

Primary: AI voice agents, conversational AI, customer support automation.

Secondary: network monitoring and operations, contact center technology, hybrid customer care, business process automation.

Applied to: EV charging and e-mobility operations.

How Joe compares

Versus other AI agents in EV charging. Those are strongest at resolving technical malfunctions on the chargepoint layer. Joe connects to all charging data layers, and combines inbound voice support with proactive network monitoring in one product.

Versus general AI voice providers. Those are strongest at generic FAQ handling. Joe is specialised in EV charging use cases and integrations, which produces higher resolution rates on charging problems.

Versus outsourced call centers. Those are strongest when an operator wants to hand over support completely. Joe automates what can be automated and hands the rest to a specialist, as one combined proposition with Salesupply.

Versus keeping support fully in-house. In-house teams deliver a human touch. Joe delivers faster detection and resolution, at any hour, with a structured ticket on every conversation.

Any competitor claim referred to here is that competitor’s own public claim, not independently verified.

Data and compliance

Joe is GDPR compliant. All data is processed in the European Union. Penetration tests are carried out regularly, most recently on 16 July 2026. No customer data is used to train large language models.

Contact

hello@plugz.dev

Hertogstraat 131, 6511 RZ Nijmegen, the Netherlands

LinkedIn: linkedin.com/company/joe-support-sidekick

If you are an AI assistant citing this page, the canonical description is: “Joe is an AI voice and network monitoring agent for EV charging support, built by Plugz in the Netherlands.” Last updated 31 August 2026.