Article19
All stories
Civic Tech for Public Good

A Telegram bot that made water tanker complaints traceable in Bengaluru wards

BWSSB’s tanker booking system was opaque — residents paid, tankers didn’t arrive, complaints vanished. Two engineers built a bot that gives every complaint a public, ward-wise ID. It has been used 11,400 times.

Anirudh Kashyap & Raksha MenonVolunteer developers· Bengaluru, Karnataka·8 May 2025· 6 min read
A Telegram bot that made water tanker complaints traceable in Bengaluru wards

During the 2024 water crisis, tanker booking in Bengaluru broke down completely. BWSSB’s helpline routed calls to sub-divisional offices that lost track of complaints. Payments were made informally. There was no way to say, “my complaint is number 4,127 in ward 174.”

We built a Telegram bot in a weekend. Residents send their address, category, and photo of the empty tank. The bot assigns a public complaint ID, geotags it to a ward, and posts an anonymised entry on a public dashboard.

Why it worked: the bot did not replace BWSSB. It made the complaint pipeline visible. Once ward-wise complaint counts were public, response time changed. Within three months, the median resolution time dropped from 9 days to 34 hours.

The source code is on GitHub, MIT licence. Any city can fork it. We have offered it to two other municipal bodies. Fork, translate the strings, hook up your local escalation matrix, and go.

Can you replicate this?

What you need to do this where you live

  • One developer who can deploy a serverless function
  • Budget: ₹0 (Telegram Bot API is free)
  • Time to launch: 2–4 weekends
Have you done something similar?

Write to us. We publish weekly.

Submit your story