Citizen Fault Reporting on WhatsApp: From Potholes to Water Leaks

01 · People first

Citizens already report potholes, water leaks, broken streetlights, refuse problems, and sewer issues through WhatsApp groups and councillor messages.

The challenge is not demand; it is turning those messages into structured reports that the municipality can prioritise, assign, and update without losing public trust.

People-first means decisions follow evidence: who is excluded, where they abandon, and which channel already fits their day.

“The challenge is not demand; it is turning those messages into structured reports that the municipality can prioritise, assign, and update without losing public trust.”

02 · The access gap

03 · Design moves

Start with a narrow service promise. Guide the conversation; confirm before you write to systems of record.

1. 01Collect fault type, location, photo, urgency, and contact preference in a short guided flow.
2. 02Give a reference number immediately and explain what will happen next, even if the repair timeline is uncertain.
3. 03Route reports by ward, service department, severity, and duplicate likelihood so teams do not chase the same leak ten times.

04 · Trust and compliance

POPIA, consent, templates, and quality ratings are guardrails — not paperwork afterthoughts.

• Do not promise instant repairs if operations cannot meet that standard; honest acknowledgement is better than false certainty.
• Keep manual review for dangerous situations, repeated failures, and complaints involving vulnerable households.

05 · Rollout

Pilot one fault category, such as water leaks or streetlights, before opening every municipal service type.

Launch one high-volume journey, prove the operating rhythm, then expand. Do not ship a thirty-option menu on day one.

06 · What to measure

• Weekly review of the ten most confusing conversations

• Completion and handoff reasons over raw message volume

07 · Buyer guidance

Look for location capture, media handling, case export, and agent notes; a fault-reporting bot without operational routing only collects frustration.

Ask to see inbox, handoff rules, template library, audit trail, and one improved failed conversation. That is the difference between a demo bot and a service channel people trust.