Society WhatsApp & SMS Broadcast: Reaching Every Resident Reliably

Getting a society notice to every resident

"It was in the WhatsApp group" is not service of notice, and every committee discovers this the first time a resolution is challenged.

Roughly a third of residents are not in the group. Some left after one argument too many. Some never joined. Tenants often are not added at all. And of those who are in it, the ones who muted it in 2023 have not seen a message since.

For social chatter that is fine. For an AGM notice with a statutory notice period, a water shutdown at 6am, or a special resolution on a ₹40 lakh repair levy, it is a liability. This page covers how to pick channels, what "delivered" actually means, and how to hold proof that a notice was served.

Match the channel to the message

Not everything deserves the same treatment. Over-broadcasting is why residents mute the society in the first place.

The important row is the emergency one. SMS is the only channel that reaches a resident with no data connection, an old phone, or a full storage card. Whatever else you use, keep an SMS path working for genuine emergencies, and test it once a year.

What "delivered" actually means

Committees treat sending as the finish line. It is not. Each channel gives you a different quality of evidence, and they are not interchangeable:

• Push notification — you know it was accepted for delivery to a device. You do not know the phone was on, or that notifications were enabled. Weakest evidence.
• WhatsApp — with a business API you get sent, delivered and read receipts per recipient. Strong evidence, but only for residents who have opted in.
• SMS — delivery reports from the operator. Solid, and independent of the resident having any app.
• Email — delivered or bounced, and open tracking that is unreliable but directionally useful. Best for anything that needs to be retrievable later.
• Physical notice board with a photograph — old-fashioned, and still what a registrar or a court will most readily accept.

For a statutory notice, use several and keep the delivery report. The combination — email delivery log, WhatsApp receipts, and a dated photograph of the board — is what turns "we told everyone" into something the society can actually produce.

The WhatsApp rules you are subject to

Societies routinely run bulk messaging through someone's personal number and are surprised when it stops working.

• Personal WhatsApp is not built for this. Broadcast lists only reach people who have saved your number. Mass messaging from a personal account gets it banned, usually at the worst moment.
• Business messaging needs opt-in. Residents must have consented to receive messages from the society. Record when and how consent was given.
• Business-initiated messages use approved templates. You cannot send arbitrary text to someone outside a 24-hour window from their last message. Get your standard notices approved as templates in advance — including an emergency template, because approval takes time you will not have during an actual emergency.
• Opt-out has to be honoured, and honoured immediately.

Do not solve this by running society communications from the secretary's personal number. When the secretary changes, the society loses the channel, the history, and the resident list.

Consent, opt-out and the line you cannot cross

Residents may opt out of social and event messaging, and that must be respected without argument.

They may not opt out of statutory notices — an AGM notice, a special resolution, a bill. If a resident has opted out of your messaging channels, the society's obligation to serve notice does not disappear; it falls back to email and physical service. Keep that fallback path alive for every flat.

Hold, per resident: consent status per channel, timestamp, and how consent was captured. Keep phone numbers and email addresses restricted to committee roles that need them — a resident directory exported to a personal laptop is a real risk, and a society-wide broadcast that CCs 200 email addresses is a data breach.

Where a message is going to a large group, use per-recipient sends rather than one message with everyone visible.

Practical delivery habits

• Send at times people read. 7–9pm on weekdays beats 11am. Emergencies obviously override this.
• Put the essential fact in the first line. "Water supply off tomorrow 9am–2pm, B and C wings" — not three lines of greeting first.
• One message, one subject. Bundled notices get half-read.
• Repeat time-sensitive notices: once 24 hours ahead, once an hour ahead.
• Reconcile after every statutory send. Look at who was not delivered and chase those flats individually. That list is usually short and is exactly where a later challenge comes from.
• Never send a bill or a personal reminder to a group. Individual financial matters go to the individual.

How this works on Plinth

A notice is composed once and sent across the channels the society has enabled, with per-resident delivery status recorded rather than a single "sent" flag.

Consent is tracked per resident per channel, so social messaging respects opt-outs while statutory notices retain a fallback path. Recipients are addressed individually rather than in a shared thread, so no resident's contact details are exposed to the rest of the society.

Delivery reports are retained against the notice, which is what lets the committee demonstrate at the AGM — or to the registrar — that a notice was actually served, and to whom it was not. Every send is written to the append-only audit log.

Frequently asked questions

Is a WhatsApp group message valid service of an AGM notice? Treat it as insufficient on its own. Serve by the method your bye-laws specify — commonly written notice with the board display — and use WhatsApp as an additional channel, keeping the delivery record.

Can we message residents who have not opted in? For statutory notices the society has an obligation and a right to serve them. For everything else, no. Keep the two categories separate in your system.

Should we keep the WhatsApp group? For community chatter, sure. Just stop treating it as the society's notice mechanism, and stop assuming everyone is in it.

How do we prove a notice was served three years ago? Retain the notice, the recipient list, and the delivery report together. This is the whole reason to send through a system rather than a personal phone.

What about residents with no smartphone? Email, SMS to a basic phone, and the physical board. Every society has some, and the process must not assume otherwise.

Step-by-step guides

• Admin: Set Up Omnichannel Communications
• Resident: Use Omnichannel Communications

Related: society notice board explained · AGM quorum and notice period rules · maintenance dues reminders