A WhatsApp complaint desk: from a citizen’s photo to a closed ticket.

By the Autowhat AI team · Updated 7 Oct 2026

The problem

Complaints arrive on paper, phone and social media, are logged late or not at all, and have no owner. Citizens hear nothing back, so they complain again in another channel.

The playbook

1. One number. Publish a single WhatsApp number for civic complaints and keep the helpline and web form feeding the same queue.
2. Locate every complaint. Use the photo’s location or a shared location to place it on the map and match it to a drain segment or asset.
3. Group duplicates. Ten photos of the same street are one ticket with ten reporters.
4. Assign an owner. The nearest crew with the right equipment, with an ETA.
5. Tell the citizen. Send the acknowledgement and the ETA on the same chat.
6. Close with proof. A closing photo goes to the citizen and onto the record.
7. Review by ward. Open tickets and acknowledgement times per ward, every morning.

How to measure it

How CityWatch does it

CityWatch puts rain gauges, channel levels, pump telemetry, citizen complaints and crews on one live map for municipal commissioners, city engineers and ward officers. When rain rate and channel trend cross a threshold, it proposes an alert with the wards at risk. Pumps are shown as running, offline or “no telemetry”, never assumed. Complaints on WhatsApp, the helpline or the web become tickets located to the drain segment, with duplicates grouped; the nearest crew with the right equipment is routed and the citizen gets the ETA and a closing photo. Desilting is closed with geotagged before/after photos per drain segment, every ward is ranked, any event can be replayed minute by minute, and the daily report is drafted from the record with sources.

See it on your own data. CityWatch — Warn before the street floods. Book a 30-minute working session with an engineer.

General guidance, current as of the date above. Figures and examples are illustrative unless a source is linked.