GovTech

WhatsApp broadcasting platforms

Reach residents where they already are — targeted by ward, in their language, with a reply path that leads somewhere.

How do public bodies use WhatsApp to reach citizens?

Through the WhatsApp Business API, a public body can send approved message templates to residents who have opted in — water supply disruptions, tax due dates, ward notices, emergency alerts — targeted geographically and delivered in the local language, with replies routed into the service system.

The channel people actually read

SMS is ignored, portals are visited only when something is wrong, and app installation is a barrier most residents will not cross for an occasional interaction. WhatsApp is already open on the phone, and messages there get read.

The discipline required is restraint. Broadcasting frequently or irrelevantly gets a public body's number blocked and reported, and once trust in the channel is lost the emergency message goes unread too. Ward-level targeting matters precisely because it keeps messages relevant.

Process

How we deliver it

1Set up the APIBusiness verification,number provisioning,template approval.2Build the audienceOpt-in capture with ward andlanguage attributes.3Create templatesApproved multilingualtemplates for each messagetype.4Target and sendWard, category or property-linked segmentation.5Handle repliesTwo-way routing into thegrievance or service system.
Process flow for WhatsApp broadcasting platforms
  1. 01

    Set up the API

    Business verification, number provisioning, template approval.

  2. 02

    Build the audience

    Opt-in capture with ward and language attributes.

  3. 03

    Create templates

    Approved multilingual templates for each message type.

  4. 04

    Target and send

    Ward, category or property-linked segmentation.

  5. 05

    Handle replies

    Two-way routing into the grievance or service system.

Deliverables

What you receive

  • Verified WhatsApp Business API account and number
  • Approved multilingual message template library
  • Opt-in capture with ward and language segmentation
  • Broadcast interface with targeting and scheduling
  • Delivery and read reporting, plus reply routing into service systems

Engagement shape

Eight to sixteen weeks. Business verification and template approval sit with the platform and add lead time we plan around.

Tooling

What we typically build with

  • WhatsApp Business API
  • Node.js
  • PostgreSQL
  • GIS ward mapping
  • Template management
  • Delivery analytics

Stack decisions follow the problem. This is where we usually start, not a fixed menu.

Frequently asked

Questions we get about this

Do residents have to opt in?

For most message categories, yes — WhatsApp's policies require it and it is also the right practice. Opt-in can be captured at any touchpoint: paying tax, raising a complaint, at a counter. Building the list takes time, which is why we start early.

What does it cost to run?

WhatsApp charges per conversation, with rates varying by category and changing periodically. We model expected monthly cost at your resident volume and message frequency before build, so the operating cost is understood rather than discovered.

Talk it through before you commit

A discovery call is a working session on your constraint, not a sales pitch.

Quick inquiry

Tell us what you're trying to build

A short note is enough. You'll hear back from the team, not a bot — usually within one working day.

Captcha challenge