Chatbots and voice agents for local councils: 24/7 answers for residents

The town hall switchboard rings non-stop in the first week of March, as the local tax deadline approaches. The same questions, dozens of times a day: how much do I owe, where do I pay, what documents do I need. In the evenings and at weekends nobody answers, and residents come back on Monday, annoyed. A chatbot or voice agent for a local council can handle exactly this part: the repetitive questions, at any hour.

Below you'll see how a council chatbot and an AI voice agent actually work, what they can and can't do, which rules must be followed and how to get one running without risking wrong answers to residents.

Chatbot or voice agent: what's the difference?

Many institutions start with one and add the other later, on the same knowledge base. That way the answers stay identical, whatever the channel.

How it works, in brief

1. The knowledge base. The council provides the official information: documents required for each type of application, fees, deadlines, opening hours, addresses, contacts. This is the only source the system answers from.
2. The AI model. It understands the question, even when it's phrased differently ("how much do I pay on the house?" or "building tax"), and looks for the answer in the knowledge base. At Neurotech we use Claude, the model developed by Anthropic.
3. Voice and telephony, for the voice agent: the Romanian voice is generated with ElevenLabs, and calls go through Twilio, on a new number or forwarded from the existing switchboard.
4. Automations. Through n8n, conversations can create appointments, send an SMS or message with the list of documents, or log a request for a department.
5. The log. Every conversation is saved in a database on EU servers, so it can be checked and so you can see which questions go unanswered.

What a chatbot or voice agent can do for a local council

• Answer frequently asked questions about fees, documents, deadlines, opening hours and locations, 24 hours a day.
• Book appointments at the civil registry, local tax or planning desks, straight into the department's calendar.
• Send written information: the list of documents, the link to the form, the desk's address, by SMS or WhatsApp, after a phone call.
• Take simple reports (a broken street light, a pothole, uncollected rubbish), with the address and description, and pass them to the responsible department.
• Put residents through to a person when the question falls outside its remit or when the resident asks.
• Show what people ask: reports on the most frequent questions tell you what information is missing from the website or which procedures are unclear.

What it shouldn't do

• Give out individual amounts owed without securely identifying the person and without a controlled link to the tax system.
• Give legal interpretations or promise the outcome of an application.
• Answer from "general knowledge" when the information isn't in the council's knowledge base.
• Keep the resident in a loop with no way out. There must always be a "speak to a colleague" option.

What a conversation sounds like

A simplified example of a call, on a Monday evening after the desks have closed:

Assistant: Good evening, you're speaking to the town hall's virtual assistant. How can I help?

Resident: I want to get a planning certificate for a house. What do I need to bring?

Assistant: For a planning certificate you'll need the standard application form and a few documents about the property, plus proof that the fee has been paid. I can send you the full list and the link to the form by SMS. Would you also like an appointment at the planning desk?

Resident: Yes, Thursday morning if possible.

Assistant: I have Thursday at 9:30 free. I'll confirm the appointment by SMS.

The example is illustrative: in reality, the assistant says exactly what your council's planning department has agreed, and nothing more. And if the resident asks something that isn't in the knowledge base, the assistant says so openly and offers to put them in touch with an officer during working hours.

Rules to follow

Transparency: residents must know they're talking to AI

From 2 August 2026, Article 50(1) of the EU Artificial Intelligence Regulation (AI Act) applies. Systems designed to interact directly with people must inform them that they're interacting with an AI system. In practice, the voice agent introduces itself from the start ("Hello, you're speaking to the town hall's virtual assistant"), and the chatbot displays the same clearly.

Personal data

Even a desk appointment means a name and phone number. Agree with the institution's data protection officer what data is collected, where it's stored, how long it's kept and how residents are informed. The simple rule: collect only what you need for that action. You'll find details of how we handle data on our data security page.

Reports and petitions

If the assistant takes reports, they must go into the institution's normal registration process. Legal deadlines don't change because a request came in via a chatbot: under Romanian Government Ordinance (OG) no. 27/2002, petitions must be answered within 30 days of registration, with a possible extension of no more than 15 days.

How to get it running, step by step

1. Gather the real questions. Ask staff at the registry and the switchboard to note down, for two weeks, the questions they get. Usually 20–30 questions cover a large share of the volume.
2. Write the official answers. Each department signs off the answers in its area. These become the knowledge base.
3. Set the routing rules. Which topics go straight to a person? To which number or address? During which hours?
4. Test internally. Staff play the part of residents and try to trip it up: vague questions, badly phrased ones, borderline topics.
5. Launch with a public announcement. Announce on the council's website and pages that there's a virtual assistant and what it can do.
6. Review monthly. Read the unanswered conversations, and update the knowledge base when fees or procedures change.

How to measure whether it's working

• how many conversations or calls the assistant handles each month, and how many it resolves without a person stepping in;
• how many calls still reach the switchboard, and whether they drop at peak times;
• how many questions go unanswered, and on which topics;
• how many appointments are made through the assistant.

A benchmark from the private sector: a chain of patisseries in Sibiu we work with recovers, with an AI voice agent, around 20 calls a day that used to go unanswered. In a council, an unanswered call doesn't mean a lost order, but a resident who comes back unhappy or a longer queue at the desk.

Common mistakes

• A knowledge base written by the supplier, not by the departments.
• Launching without an internal test period.
• Nobody appointed to keep the information up to date.
• A voice agent that doesn't introduce itself as a virtual assistant.
• No quick way through to an officer.

What we offer

Neurotech AI builds chatbots for websites and WhatsApp and AI voice agents in Romanian, on Claude, with data stored on EU servers. As a guide, our public implementation prices start at €800 for a chatbot and €1,500 for a voice agent, excluding VAT, paid in instalments tied to deliverables. Monthly costs depend on the volume of conversations and calls. For a public institution, the procurement route and documentation follow the rules that apply to it.

If you'd like to hear how a virtual assistant for your council would sound, book a free 30-minute call. We'll start from the questions you already get.