A citizen grievance WhatsApp helpdesk for municipal bodies
A grievance WhatsApp helpdesk lets citizens report an issue by picking a category and ward from a menu, instantly receive a reference number to track it, and check status later just by sending that number back. Running in regional languages, it gives municipal bodies a single, always-open channel for complaints instead of relying only on phone lines or in-person visits.
- A category and ward menu structures every complaint consistently, which helps routing internally.
- Generating a reference number immediately gives citizens something concrete to hold onto and follow up with.
- Status lookup by reference number closes the loop without a repeat visit or call.
- Running the helpdesk in regional languages matters more here than in most other use cases.
Why WhatsApp suits civic grievance reporting
For a municipal body serving a city or town anywhere from Nashik to Guwahati, most residents already have WhatsApp, and far fewer are comfortable navigating a dedicated grievance portal or app. A WhatsApp helpdesk meets citizens where they already are, at any hour.
A dedicated portal also assumes the citizen remembers a URL, has a login, and is filling the form on a reasonably capable device: three assumptions that don't hold for a large share of any municipal population, particularly older residents and those in areas with patchy data connectivity. A WhatsApp number, already saved from years of everyday use, removes all three barriers at once.
A single WhatsApp number is also easier to publicise consistently, printed on a municipal notice board, shared in a local newspaper announcement, or circulated by ward-level community groups, than trying to get an entire population to remember a portal web address that most will never type into a browser.
It also meets residents partway through an existing habit rather than asking for a new one. Most people already message a local shopkeeper, a relative or a neighbourhood group on WhatsApp daily, so reporting a civic issue the same way requires no new behaviour to learn, unlike downloading and learning a dedicated civic app.
Category and ward capture
A List Menu presents common complaint categories: garbage collection, street light, water supply, road damage, stray animals, followed by an Ask a Question block for the ward or locality. This structure alone makes routing far more consistent than free-text complaints.
Not every citizen knows their ward number by heart. Offering a short list of well-known landmarks or localities alongside the ward option, or accepting a shared WhatsApp location pin instead of typed text, captures the same routing information without assuming administrative knowledge the citizen may not have.
Reference number and routing
A Set Variable block generates a reference number the moment the complaint is captured, and an HTTP/API request or Webhook block logs it into the municipal body's grievance system, routed to the right department based on category and ward.
Confirming the reference number back clearly matters more here than in most use cases, since it's often the only proof a citizen has that they actually reported the issue: "Complaint logged. Category: Street Light, Ward 12. Your reference number is GRV-20394. Save this message to check status anytime."
Where a single complaint genuinely spans two departments, a waterlogged road that's both a drainage and a road-repair issue, the routing logic should log it once with a primary department, rather than creating duplicate entries that both departments assume the other is handling.
Status lookup by citizens
Citizens can message the reference number back any time to check status. An HTTP/API request block queries the grievance system and replies with the current stage: received, assigned, in progress, or resolved.
Include the department name and, where available, an expected timeframe based on the complaint category. A garbage collection issue typically resolves faster than a road repair, and stating this difference honestly manages expectations better than a single generic "we're working on it" for every category regardless of actual complexity.
Building it on Convo360
On Convo360's Flow Builder, this entire helpdesk is drag-and-drop, no code needed.
- Set up a List Menu for complaint category, followed by Ask a Question for ward/locality and complaint details.
- Allow a photo upload via Send Media receive, since a photo often explains a civic issue faster than text.
- Use Set Variable to generate a reference number and a Webhook block to log it in your grievance system.
- Add a separate flow for status lookup, triggered by keyword, using HTTP/API request.
- Configure the AI agent or menu text in Hindi and the relevant regional language for your city.
See Flow Builder docs and webhooks docs.
Pilot the helpdesk with one or two wards first rather than launching city-wide on day one. This surfaces category and routing gaps against real complaint volume while the fix is still small, before extending the same tested flow to the rest of the city.
Mistakes to avoid and what to track
A common mistake is a category menu that's too generic to route correctly. "Other" becoming a dumping ground for a large share of complaints defeats the purpose of structured routing. Review the category list every few months against what's actually being reported and refine it rather than leaving it fixed from launch.
Track average time from "logged" to "resolved" by category and ward in your grievance system, alongside how many status-check messages a single complaint receives before resolution. A high repeat-check count on a specific category usually means citizens aren't confident the complaint is being acted on, which is worth addressing with clearer stage updates rather than just faster resolution.
Publish anonymised resolution statistics periodically where feasible: a ward-level view of how many complaints were resolved and in roughly how many days builds public trust in the channel itself, which in turn increases genuine adoption over relying on phone calls or in-person visits.
What it costs
This runs on the Starter plan (₹999/month, ex-GST) for the flow and webhook logging. Multilingual AI-assisted replies for open-ended complaint descriptions need the Pro plan (₹2,999/month, ex-GST) with a connected AI provider key.
Example conversation
Industry guide: AI agents for Govt & Utilities — Grievance intake, bill reminders & citizen FAQs.
Set up a citizen grievance helpdesk
Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.
Frequently asked questions
Can citizens attach a photo of the issue?
Yes, WhatsApp allows sending images directly, and the flow can accept and forward these into the grievance system along with the complaint details, which often explains a civic issue, like a pothole or overflowing drain, faster than a written description alone.
How do citizens check status later?
By simply sending the reference number back to the same WhatsApp number, which triggers a lookup flow that replies with the current stage of their complaint.
Can the helpdesk work in languages other than Hindi and English?
Yes, it can be configured for other major Indian languages the local population uses, since language coverage is one of the most important factors for civic adoption.
What happens to urgent safety complaints like a live wire or major leak?
These should be flagged with a Condition block for immediate routing and a clear message advising the citizen to also contact the relevant emergency helpline directly.
Related reading
Available across India — see WhatsApp & AI calling automation by state and city.