Government SMS and Citizen Messaging: A Practical Guide

How should WhatsApp be used for citizen services?

WhatsApp suits conversations: a citizen asks a question, an agent or chatbot answers, and documents can be shared. Use it with opt-in and approved templates.

• A citizen who messages first opens a 24-hour customer service window in which you can reply with free-form messages (see the 24-hour window).
• Outside that window you can send only approved templates. Label them by category: appointment confirmations and status updates are normally Utility templates, one-time codes are Authentication templates, and campaigns to promote a service are Marketing templates. Meta decides the final category.
• WhatsApp's business policy requires opt-in permission and respect for requests to stop, and says businesses must not share or request full payment card numbers, financial account numbers or personal ID card numbers. Do not collect these in chat; link to a secure portal instead.
• Where automation is used, offer an easy route to a human officer. See chatbot to human handoff.

Example Utility template for an appointment: Hello {{1}}, your appointment at {{2}} is confirmed for {{3}}. Reply CHANGE to reschedule.

How do you design alerts that reach everyone?

Plan the fallback before the emergency. A single channel will miss some residents, so combine them.

1. Define the audience from a registered list, such as a district or service group, with a documented legal basis.
2. Send on the fastest broadly available channel, normally SMS.
3. Add WhatsApp or push for people with data connections and richer content.
4. Use voice calls for the most critical notices and for residents who rely on audio. Voice is provisioned with the account team.
5. Record delivery status per citizen and retry or escalate failures. See channel fallback strategy.
6. Respect quiet hours for non-urgent notices; see the quiet hours glossary entry.

We do not cover cell broadcast (the operator-level alert system built into mobile networks) here. It is run by operators and national authorities under separate frameworks.

What about multilingual and accessible messages?

Send each citizen the notice in the language they chose. Arabic, English, Kurdish or any other language needs Unicode for SMS, and every WhatsApp template is approved per language. Keep sentences short, avoid acronyms, and offer a voice option for people who cannot read a text message. Our guide to Arabic customer messaging covers direction, numerals and tone.

What should procurement ask a messaging supplier?

Ask for evidence on security, data handling, sender registration and reporting. Use this checklist in the tender and pilot.

1. Security attestations. BroadNet holds ISO/IEC 27001:2022, ISO/IEC 27018, ISO 9001:2015, ISO 22301 and a SOC 2 Type II attestation, and operates in line with the GDPR; details are on the security page. Ask any supplier for certificates you can verify.
2. Data location and retention. Where are message content, logs and contact lists stored, and for how long? Hosting and data residency needs are reviewed during discovery.
3. Access control. Who can see content? Does each account use its own token and role?
4. Sender ID registration. Who files it, for which countries, and what are the published lead times? We handle registrations end to end; approval decisions stay with operators and regulators.
5. Delivery reporting. Per-message status, filters and export for audits.
6. Opt-out and consent tools where the law requires them.
7. Fraud controls. Protection against SMS pumping on OTP flows.
8. Fallback and support. Channel fallback and a named contact for incidents.
9. A pilot on a limited audience with agreed success measures.

Use the messaging provider RFP kit as a starting template.

Worked example: a municipal permits office

"Northgate Municipality", a synthetic city, wants fewer missed permit appointments and fewer "where is my application?" calls. It starts with two flows. First, an SMS reminder 48 hours before each appointment with a CHANGE keyword that opens a conversation in the shared inbox. Second, a WhatsApp Utility template that tells applicants when their status changes, with a button to the official portal.

Before launch the office registers one sender ID, publishes a page titled "Messages we send and messages we never send", and trains counter staff to answer questions about it. After 60 days it compares missed appointments and call-centre volume for the pilot district against a district that has not started. The comparison, not the sending volume, decides whether to extend the service.

What mistakes should agencies avoid?

• Sending from many different sender names. Citizens cannot learn which one is real.
• Putting sensitive details in the SMS. Case numbers are fine; diagnoses, income or ID numbers are not.
• Asking for replies with personal data. It trains citizens to answer scammers.
• No opt-out or contact route for non-emergency messages.
• Launching to everyone at once. Pilot with one service first.
• Ignoring the legal basis. Rules for public-sector messaging differ by country; involve your legal and data-protection teams.

How OmniChannels.ai helps

OmniChannels.ai, powered by BroadNet Technologies, supports government and public-sector messaging across SMS, WhatsApp, RCS, voice and email. SMS runs over BroadNet's direct operator connectivity with registered sender IDs, and WhatsApp and RCS show verified profiles. Citizen questions land in a shared inbox where chatbots and AI agents answer in Arabic and English, with handover to an officer. Delivery reports support audits. To discuss requirements, security and registration for your country, contact our team.