How to actually run WhatsApp in an Indian election campaign

One group per polling booth capped at 256 members, a ward-level admin group above it, and a constituency core group at the top. Content flows down and intelligence flows up. Booth groups are for local information — this ward's water line, this street's road work — and grievance capture. The moment they become forwarding channels for state-level party content, members mute them and the asset is dead.

An unmoderated booth group becomes an opposition asset within a fortnight: somebody forwards a communal video, it gets screenshotted, and it is now your campaign's problem. Two admins per group, a one-page written content policy, and a removal protocol. This is unglamorous work and it is the difference between an asset and a liability.

Broadcasting from personal numbers gets them banned within 48 hours and takes your admins down with them mid-campaign. The official WhatsApp Business API with a verified profile, approved templates and a documented opt-in trail costs more and does not get switched off in week three. It is also what makes you defensible if a complaint reaches the ECI.

Booth and serial number lookup, grievance filing with photo and GPS, volunteer signup, event requests — every interaction landing in a CRM tagged by booth. A grievance filed, assigned to a ward in-charge, closed with photographic proof and followed up with a phone call is the highest-conversion voter contact we measure. Higher than any advertisement, and it compounds into the next election.

Under 30 seconds. Works on mute, with burnt-in subtitles in the local script. One message per group per day maximum. And always hyper-local: constituency-specific content forwards 6–8 times more than state-level party material in the groups we track. The candidate walking a specific broken road beats a professionally produced state ad every time.