A WhatsApp bot for municipalities and public services
that books appointments and tracks requests

The problem in municipalities and public services

Booking a permit appointment or checking on a service request usually means calling during business hours and often waiting on hold, because most municipal offices have no self-service way to book a real slot or check a real status outside a phone call or an in-person visit. A resident who cannot easily reach the office during work hours simply waits, or shows up without an appointment and takes a staff member’s time to sort out on the spot.

The second problem is no-shows. An appointment booked weeks in advance, with no reminder before the date, gets forgotten at a real rate, wasting a slot that another resident could have used, and the office rarely has a system that flags this pattern until a staff member happens to notice an empty chair.

The third is document deadlines tied to an open request, a missing form, a required follow-up visit, which depend entirely on a resident remembering, or a staff member remembering to remind them, rather than a system that tracks the date and sends a reminder on its own.

A fourth is that requests submitted by phone or in person often have no visible status a resident can check without calling again, so a request that is actually progressing normally generates repeat follow-up calls simply because there is no other way to know.

What we build for municipalities and public services

A WhatsApp bot that books appointment slots for permits and public services directly into your office’s real calendar, so a resident never books a time that is already taken, and sends a reminder before the appointment to cut down on no-shows. Service request status becomes checkable by reference number at any hour, instead of requiring another phone call just to confirm nothing has gone wrong.

The bot has a clear boundary: anything beyond booking, status checks and simple FAQ, a dispute, a request for an exception to a rule, gets routed to staff with the full conversation attached. Structured data, bookings, status checks, reminders sent, exports to your case-management system or a spreadsheet, so your office has a record without anyone re-entering it by hand.

Typical integrations: your office’s calendar or booking system, a case-management system or a structured spreadsheet for request status, and WhatsApp Business API for messaging.

How it works in 2 to 3 weeks

1. Audit of the current booking and request flow. We read how appointments and requests are currently handled to map what repeats.
2. Script and rules. Booking rules, reminder schedule and the hand-off rule, written with your office staff.
3. Build and connect. The bot is built against your real calendar and case-management system, tested on a sample cycle.
4. Launch. Clear hand-off path for anything outside the script, full logging and export.
5. Tuning. Two weeks of reviewing real conversations and adjusting the scripts.

What it costs

Running cost is separate and usually $20 to $100 a month in messaging and model usage depending on resident volume, with a hard budget cap set before launch.

Typical results

Public offices that add appointment reminders typically see no-show rates fall, a pattern reported across public-sector service delivery because the reminder goes out consistently instead of depending on staff remembering to send one. Self-service status checks commonly reduce repeat follow-up calls on requests that are progressing normally, since residents can confirm status without calling again. These are typical ranges reported across the sector, not a guarantee for every office, since service type and resident volume both move the number. Our own numbers are in the case studies: prototypes of a Telegram assistant with browser automation and OCR serving two visa centres through a unified bot, including appointment and status handling, are detailed in the visa appointment assistant case study.

Why Senator Media

We build these bots against your real calendar and case-management data from day one, so a booked slot or a status check is never out of sync with what your office actually has on record. The price is fixed once the plan is agreed, and the bot’s source code and data stay in your office’s name.

If your real bottleneck is that appointment slots and request status are not tracked in any system a bot could read from, we will say so, since a bot reading nothing reliable just repeats that gap faster. Getting a basic calendar or tracking system in place first is usually worth doing before this goes live on top of it.

Pair this bot with an AI agent for municipalities and public services if residents need deeper FAQ and department routing beyond booking and status. See the full package breakdown on the development service page, or get a written plan with a fixed price for your office.