Society communication and notice board app
Notices that reach the right subset of residents on the channels they actually read, with a record of who has seen them — and discussion that lives somewhere the announcements do not have to compete with.
A society communication app sends targeted circulars to specific towers, wings or resident groups across push, SMS, email and WhatsApp, records read receipts and acknowledgements, and hosts moderated discussion forums so announcements are not buried in a group chat.
One announcement, every resident, zero WhatsApp chaos
The typical society communicates through an accumulation of WhatsApp groups: one per tower, one for the committee, one for residents in general, one left over from the last festival, and several nobody remembers creating. A notice about a water shutdown goes into three of them, gets forty replies, and is unfindable by evening.
This fails in both directions. Residents miss things that matter because announcements are buried under conversation, and the committee has no idea who actually saw a notice — which becomes a real problem when the notice was about a scheduled shutdown, a maintenance rate change, or an AGM.
The distinction that fixes it is between announcements and discussion. An announcement is one-to-many, needs to reach a defined audience, and needs a record of delivery. Discussion is many-to-many and needs moderation but not delivery tracking. Putting both in the same channel guarantees the first is lost in the second.
Announcements and digital circulars, not chat messages
Announcements and digital circulars
Circulars are structured documents rather than chat messages: a subject, a body, attachments, an effective date, and an audience. They are archived, numbered and searchable, which is what makes a circular referenceable six months later.
Formal notices — AGM notices, rate changes, bye-law circulars — carry their own status because they may need to be evidenced later. Those are issued through the governance module with per-member despatch records rather than as general announcements.
Ready-made notice templates
Templates for the notices every society sends repeatedly: water shutdown, lift maintenance, AGM notice, festival arrangements, pest control schedule, dues reminder, parking reallocation. Drafting starts from a structure rather than a blank box.
Templates also keep the tone consistent across committees. A society whose notices read the same way regardless of who is secretary this year looks considerably more competent than one where they do not.
Targeted notices by tower, wing or group
Audience is selected rather than assumed: a tower, a wing, a floor, owners only, tenants only, defaulters, committee members, or a custom group. Each segment comes from live unit and member records rather than a distribution list somebody maintains. Residents who receive only the notices that concern them start reading notices again.
| Notice | Who receives it | How it goes out | What confirms it |
|---|---|---|---|
| Water shutdown starting in an hour | The towers it affects | Every channel at once | Read status, with the gap followed up |
| Lift maintenance in Tower C | Tower C | Push, and SMS for members without the app | Read status |
| New amenity rules or gate policy | The residents it applies to | Push, with email where a document is attached | Acknowledgement |
| Parking reallocation | The flats affected | Push and SMS | Acknowledgement |
| Dues reminder | Flats with dues outstanding | The channels each resident has | Stops when the bill is paid |
| AGM notice | Every member entitled to notice | Through the governance module | Per-member despatch record |
Delivery on every channel, and proof a notice landed
Delivery on push, SMS, email and WhatsApp
The same circular goes out across channels according to what each resident has and what the notice warrants. Push for app users, SMS for the members who do not use the app, email where a document is attached, and WhatsApp where the society has that set up.
Other modules send through the same channels rather than having their own messaging. Billing reminders, ticket updates, amenity confirmations, gate notifications and AGM notices all arrive as one coherent stream instead of five.
Read receipts and acknowledgements
Delivery and read status is tracked per recipient, so a committee can see coverage and follow up the gap through another channel. For notices that require it, an acknowledgement can be requested — a resident actively confirming they have read it.
Acknowledgement matters for anything with consequences: new amenity rules, a change to gate policy, a parking reallocation. “Everybody was informed” is a much stronger position when it is a list.
Moderated discussion forums, away from the announcements
Discussion happens in topic forums — maintenance, amenities, security, general — rather than in the announcement channel. Threads are attributed to verified residents, moderated by whoever the committee designates, and searchable.
The point is not to replace WhatsApp socially, which will not happen. It is to give the committee a channel where announcements are not competing with conversation, and to have a moderated place for the discussions that genuinely need a record.