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 drown in discussion. Forty replies later, the notice is above the fold for nobody.
- Everything goes to everyone. Tower B residents receive Tower A’s lift notice, and stop reading either.
- Delivery is unknown. A committee cannot say whether a shutdown notice reached the flats it affected.
Key capabilities
Reach the right people on the right channel, know that it landed, and give discussion its own place.
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.
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. A lift outage in Tower C goes to Tower C.
This is the change that recovers attention. Residents who receive only notices that concern them start reading notices again, and the effect on read rates within a couple of months is substantial.
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
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.
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.
Urgent notices — a water shutdown starting in an hour — can be escalated across every channel at once. Routine ones should not be, and the system distinguishes the two so residents do not start filtering out everything.
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.
How it works
Targeting is the step that makes the next notice get read.
Who it helps
Communication is the module residents interact with most often, and the one where over-use does the most damage.
Works with the rest of KeyMatrix
Targeting only works because the audience is derived from live data. Owners versus tenants, tower and wing, flats with dues outstanding, members eligible to vote — each of those comes from the unit and member records rather than from a distribution list somebody maintains.
Other modules send through it rather than having their own messaging. Billing reminders, ticket updates, amenity confirmations, gate notifications and AGM notices all go out on the channels each resident has, which is why a resident receives a coherent stream from one system instead of five.
- Unit management. Audience segments come from live ownership and tenancy data.
- Billing. Dues reminders use the same channels and stop when the bill is paid.
- AGM and governance. Statutory notices are issued with per-member despatch records.
- Helpdesk. Ticket updates reach residents without a separate notification system.