An AI agent for municipalities and public services
that answers resident questions, not policy decisions
A municipal office fields the same resident questions daily: what are today's hours, what does a permit application need, where does a service request stand. We build an agent that answers from your actual published rules and schedules, checks request status, and routes anything that needs a real decision to staff, never answering as if it were policy.
The problem in municipalities and public services
A municipal front desk and phone line field a steady stream of questions that are entirely a matter of public record: what time does the office open, what documents does a building permit need, where does my service request currently stand. None of these require a staff member’s judgment, yet each one takes a person away from a desk to look up and recite information that is, in principle, already published somewhere.
The second problem is availability. Residents try to reach a municipal office outside the hours it is staffed, evenings, weekends, and get nothing until the next business day, even for a question as simple as confirming an office’s hours or a form’s requirements.
The third is consistency. Without one authoritative source a staff member checks, the answer to “what does this permit require” can vary depending on who answers the phone, and an inconsistent answer from a public office carries more weight, and more consequence if wrong, than it would from a private business.
A fourth, seasonal problem is volume concentration around known events, a filing deadline, a public notice period, a seasonal service change, when the same question arrives from dozens of residents in a short window, and the office’s staffing does not flex with that pattern.
What we build for municipalities and public services
An agent that answers office hours, location and permit-requirement questions from your actual published rules and schedules, checks service request status by reference number, and routes a new request to the right department based on what the resident actually needs. The knowledge base is built from your real published documents, not a generic template, and staff can update it as rules change without any code involved.
The agent has one hard rule in its playbook: it never interprets a regulation, grants an exception, or gives anything that resembles legal advice. The moment a question moves from “what are the requirements” to “can I get an exception” or “how should I interpret this rule for my situation,” it says so and hands off to staff with the full conversation attached, so nothing needs repeating.
Typical integrations: your municipal website’s chat and WhatsApp for resident questions, a case-management or permit system where an API exists, and a structured spreadsheet for smaller offices not yet running a dedicated system. For jurisdictions handling several service types, permits, utilities, public records, the knowledge base is scoped by department, so an update to one department’s rules does not risk introducing stale information into another’s answers.
How it works in 3 to 5 weeks
- Audit of current resident inquiries. We read a sample of real questions from phone logs, email or your current contact channels, and map what repeats.
- Playbook. FAQ content pulled from your published rules and schedules, department routing, and the exact line the agent will not cross, reviewed with your office before any code.
- Build and test. The agent is built against your real rules and systems, tested on a sample of real questions first.
- Launch with guards. A clear escalation rule for anything beyond published information, full logging of every handoff.
- Tuning. Two weeks of reviewing real conversations and adjusting the knowledge base.
What it costs
| Package | Price | What it covers | Timeline |
|---|---|---|---|
| Assistant | from $2,000 | One to two channels, FAQ, permit lookups, status checks, routing | 3 to 5 weeks |
| Sales agent | from $4,000 | Multi-department intake, structured request routing, system writes | 4 to 6 weeks |
| Agent team | from $10,000 | Resident agent plus a monitor across several departments or offices | 6 to 10 weeks |
Running cost is separate and usually $20 to $200 a month in model usage depending on inquiry volume, with a hard budget cap set before launch.
Typical results
Public bodies that automate routine resident FAQ typically see front-desk and phone inquiry volume on repeat questions fall by a meaningful share, often reported in the 30 to 50 percent range across comparable public-sector deployments, because the agent answers from a fixed, published knowledge base rather than depending on who is at a desk. These are typical ranges reported across the sector, not a promise for every office, since service complexity and resident volume both move the number. Our own numbers are in the case studies linked below: a visa consulting centre’s client-facing AI consultant with a strict hand-off rule and an admin-editable knowledge base is detailed in the visa centre AI support case study, and an outreach and inbox agent built on a structured playbook for a B2B certification body is in the B2B certification AI sales agent case study.
Why Senator Media
We build these agents the way we build them for ourselves: a closed set of tools and a hard rule the agent cannot cross, here, no regulatory interpretation or exceptions, enforced in the playbook rather than hoped for. The price is fixed once the plan is agreed, you get a working demo every week during the build, and the conversation logs and source code stay in your office’s name.
If your real bottleneck is that rules and requirements are published inconsistently across different documents, we will say so, because an agent reading conflicting sources just automates the inconsistency faster. Consolidating that source of truth first is usually worth doing before any agent goes live on top of it.
Pair this agent with a WhatsApp bot for municipalities and public services for lighter appointment and request-status needs. See the full package breakdown on the AI agents service page, or get a written plan with a fixed price for your office.
FAQ
How much does an AI agent for a municipality cost?
Our Assistant package starts at $2,000: one or two channels, FAQ, permit lookups, service request status, routing, live in 3 to 5 weeks. A lighter FAQ-only bot starts at $900.
Does the agent interpret regulations or give legal advice?
No, and that boundary is written into the playbook before launch. It answers from your published rules, requirements and schedules, checks request status, and routes new requests to the right department. Any question that requires interpreting a regulation or making an exception is routed to staff.
How does it know our permit requirements and schedules?
From your published rules, forms and office hours, which we build into the knowledge base. Staff can update it as rules change, without touching code, so the agent never answers from outdated information by accident.
Which channels does it run on?
Your municipal website's chat and WhatsApp are the most common for resident questions, with Telegram as an option for jurisdictions where that channel is widely used.
Can it serve residents in more than one language?
Yes. Jurisdictions with multilingual resident populations typically run the agent in the official language plus one or two commonly spoken languages locally.
Does it integrate with our permit or request management system?
We integrate with common municipal case-management or permit systems where an API or reliable export exists, or with a structured spreadsheet for smaller offices, and we tell you upfront if your current system has no reliable way to connect.