A city chatbot is a chat assistant on a city or town website that answers residents' and visitors' questions, and in some cases takes service requests. Cities use them for three main jobs: answering public information questions, taking 311-style requests, and covering phone and text channels. The right one depends on which of those jobs you need done.
Government chatbots have changed a lot. Early ones were menus of buttons that broke the moment a resident typed something unexpected. Today's AI chatbots read a city's own content and answer in plain sentences. This guide describes the main kinds, with examples of vendors and the cities they list as customers, and offers questions to help you choose.
Three kinds of government chatbot
1. Answer bots for public information
These answer questions from the city's published content: hours, trash schedules, parking rules, recreation programs, events, meeting dates and "which department handles…". They link to the source page and point people to the right office for anything they can't handle.
This is the simplest kind and the quickest to launch, because the content already exists on the website. It's also where most resident questions are. New York City's Mayor's Management Report found that 72% of contacts to 311 in FY2024 were inquiries rather than service requests.
2. Service request and 311 bots
These take requests as well as questions: report a pothole, a missed pickup or a broken streetlight. They are usually connected to the city's work-order, 311 or CRM system so the request lands in the right queue. Setup takes longer, because the chatbot has to be configured to fit those systems and processes.
3. Omnichannel platforms
Some vendors offer the chatbot as part of a wider platform, with SMS text messaging, AI voice agents that answer phone calls, outbound alerts, and in some cases permitting, case management or records tools. These suit larger cities and counties that want to rebuild how residents contact them across every channel.
City chatbot examples by vendor
The vendors below are a sample, not a complete list, and each describes itself in its own words. We list customers only where the vendor names them publicly. Details are as published on each vendor's site in November 2026.
Citibot
Citibot describes itself as a resident-first, AI-powered government communications platform built specifically for government. It answers from an agency's approved content and offers web chat, SMS text, AI voice agents, Facebook Messenger, WhatsApp and text alerts, in 75+ languages. Residents can submit service requests through chat. Pricing is not published.
Customers named on its site include Palo Alto, Encinitas and Roseville in California; Arlington and McKinney, Texas; Montgomery, Alabama; Baton Rouge, Louisiana; Colorado Springs; Kansas City, Missouri; Knoxville, Tennessee; and several Florida counties.
Polimorphic
Polimorphic describes itself as a full-service platform for service-first governments. Its AI assistant, Poli, works across a voice agent for phone calls, chat and search in 75+ languages, email and SMS, alongside permit and licensing workflows, a constituent CRM and a public records tool. Its pricing page lists plan tiers without dollar amounts.
Customers it names in case studies and testimonials include Newport, Rhode Island; Littleton, Colorado; Suisun City, California; and the Town of Palm Beach, Florida.
CivicPlus
CivicPlus, a large provider of local government websites, offers a chatbot that it describes as giving detailed, on-demand answers for local government, drawing on municipal websites and codified ordinances. Pricing is by request.
VisitorDesk.ai
VisitorDesk.ai, which publishes this blog, is an answer bot: an AI chatbot for city services, events and visitor questions that answers from the pages your departments publish. It focuses on towns, smaller cities and tourism communities, where seasonal and visitor questions are a big share of the load, and it does not take service requests or connect to city systems. Plans are published, starting at $99 a month.
We compare these options side by side on our page comparing municipal chatbots.
What cities use chatbots for
Across vendors, the most common uses are:
- Hours and locations: city hall, the library, the transfer station, the pool.
- Trash and recycling: pickup days, holiday schedules, bulky items.
- Parking: rules, permits information, where to park for events.
- Recreation: programs, registrations, beach and park rules.
- Meetings: agendas, dates and how to comment.
- Wayfinding: which department handles what, and how to reach it.
- Visitors: events, things to do and where to eat, in tourism towns.
- Service requests: potholes, streetlights, missed pickups, where the bot supports them.
How to choose an AI chatbot for city services
Start with the job, not the feature list.
- What do residents actually ask? Count a month of front-counter calls and emails. If most are questions, an answer bot covers most of the load. If many are requests, look at 311 integration.
- Who will maintain it? A small town needs something that works from the website it already has. Bigger platforms need someone to configure and own them.
- What happens when it doesn't know? It should say so, point to the right office, and send the question to staff, not guess.
- Does it cite sources? Every answer should link to the city page it came from, so residents can check and staff can fix.
- Is it accessible? Under the ADA Title II rule, vendor tools on government websites must meet WCAG 2.1 Level AA. Ask for test results and audit plans. Our post on ADA Title II website chatbots has questions to ask.
- Languages? Ask which languages residents can use and how translation works.
- Data and records: where conversations are stored, who sees them, how long they're kept, and whether chat logs are public records in your state.
- Total cost: setup, annual price, per-conversation charges and what happens at renewal.
Pitfalls to avoid
- Launching on stale content. A chatbot repeats what the website says. Fix the top 25 pages first.
- Bots that guess. Wrong answers about deadlines or fees damage trust quickly.
- No owner. Someone needs to review unanswered questions each week and update content.
- Over-promising. Be clear with residents about what the bot can and can't do.
For the bigger picture, see AI in local government.
