This is the emergency layer — one tap fires a parallel dispatch to the guard, committee and emergency contacts at once, with location and category routing; for a medical SOS the guard sees the resident's medical profile. The alarm, not the announcement.
For RWA Hon. Secretaries, Presidents & residents · one-tap dispatch · 6 parallel channels · medical / fire / security / general routing · bedside panic buttons.
SOS Alerts is the society's internal emergency first-response layer. One tap — from a lock-screen widget, the app, or a BLE bedside or common-area panic button — fires a single SOS, after a 5-second cancel countdown, in parallel down up to six channels at once: the guard tablet siren, the Hon. Secretary, the Hon. President, the resident's emergency contacts by IVR, and optionally three neighbours — all with location, routed by category (medical / fire / security / general). On a medical SOS, the resident's medical profile decrypts on the guard's tablet under the DPDP Act 2023 §17(1)(c) medical-emergency exemption, then re-encrypts on close. It's deliberately the emergency layer only: non-emergency notices (water cut, AGM) are communication; proactive patrol is patrol-monitoring; maintenance is the helpdesk.
Smt. Menon's society is mostly senior citizens. The night the alarm mattered, no one had time to find a phone number. Here's the event the way SOS records it — and the foot makes the one thing explicit that the page must never overclaim: this runs alongside 112, not instead of it.
| Time | Event | Detail | Channels |
|---|---|---|---|
| T+0s | Bedside button pressed | BLE button, Flat C-302, defaults to medical | — |
| T+0–5s | Cancel countdown | 5s to stop a false alarm — not cancelled | — |
| T+5s | Parallel dispatch fires | location + medical category attached | 6 channels at once |
| T+5s | Medical profile decrypts | blood group, allergies, doctor → guard tablet | DPDP §17(1)(c) |
| T+close | Event closed + audited | profile re-encrypts; §65B log written | → monthly RWA report |
| Alongside | 112 / 108 called | SOS moved the guard + neighbour meanwhile | complements, not replaces |
When the same channel carries water-cut notices and emergencies, a real alarm scrolls past behind a parking reminder — and the one message that needed instant attention is the one that gets missed.
A resident in trouble calls the guard, who doesn't pick up, then the secretary, who's asleep — sequential calls waste the minutes that matter, when all of them should have rung at once.
In a society of senior citizens, the person most likely to need an alarm is the least likely to unlock a phone and find a menu — so the alarm has to be one physical press at the bedside.
A guard reaches a collapsed resident with no idea of their blood group, allergies or doctor — information that exists, but is locked away exactly when it's needed most.
A resident raises the alarm from the lock-screen widget, the app, or a BLE bedside or common-area panic button — one action, no menus. A 5-second cancel countdown runs first, so an accidental press can be stopped before anyone is dispatched.
The alarm is categorised — medical, fire, security or general — and each branches into its own response path. A senior pressing a bedside button can default to medical, so responders know what they're walking into.
A single SOS fires simultaneously: guard tablet siren, Hon. Secretary, Hon. President, the resident's emergency contacts by IVR, and optionally three neighbours — all at once, with location. If the device has no data, dispatch falls back to SMS.
The resident's medical profile — blood group, allergies, medications, primary doctor — surfaces on the guard's tablet for the duration. It's encrypted at rest and decrypts only during the active medical SOS under the DPDP Act 2023 §17(1)(c) medical-emergency exemption, then re-encrypts on close.
The event is written to a per-event audit log admissible under Section 65B of the Indian Evidence Act, and rolls into a monthly SOS report for the RWA. Throughout, this is the society layer working alongside ERSS 112 and 108 EMS — never replacing the national emergency number.
EstateDeck SOS is a society-internal first-response layer positioned alongside the national Emergency Response Support System (112) and 108 EMS. It moves the guard, neighbour and medical details around the ambulance call — it is not a substitute for it.
The medical-emergency exemption is the lawful basis for surfacing a resident's medical profile to the guard during an active medical SOS. The data decrypts only for the event and re-encrypts on close — available when life depends on it, sealed otherwise.
Each event is written to a per-event log admissible under Section 65B, capturing who raised it, when, the category, who was dispatched and the close — a tamper-evident, time-stamped record, India-hosted and backed up under DPDP, rolling into a monthly RWA report.
Framework references: ERSS 112 India (Ministry of Home Affairs national emergency number) + 108 EMS — EstateDeck SOS complements, never replaces them; DPDP Act 2023 §17(1)(c) (medical-emergency exemption — lawful basis for medical-profile decryption during active SOS); Indian Evidence Act §65B (admissible per-event audit log); Mental Healthcare Act 2017 §27 (discreet mental-health SOS routing). The record is described as tamper-evident and time-stamped, not unbreakable. This page owns the emergency dispatch only; notices, patrol and maintenance are their own modules.
EstateDeck keeps the emergency dispatch on its own page, away from the notice queue, the patrol schedule and the maintenance desk — on purpose. An alarm that needs a guard moving now must never share a channel with a water-cut announcement. Keeping them apart means SOS ranks for society emergency alerting and never blurs into "society notices."
The dispatch is the same; the category routes it to the right response.
A senior citizen presses the bedside button; it defaults to medical, fires the parallel dispatch, and the guard reaches the door already knowing the blood group and the doctor's number — the case this society sees most.
A resident taps security from the app; the guard tablet sirens and the committee and neighbours are alerted at once — and the response is the security path, not a medical one, because the category routed it.
A common-area panic button raises a fire SOS; the dispatch goes wide and fast, and — as the banner says throughout — the right next action is still the 112 call this layer was built to run alongside.
"Most of our members are over seventy. When I evaluated emergency systems, I was firm on two things, and this is the only one that respected both. First, it had to be one press — a bedside button, not an app with a menu, because at 4 AM a frightened eighty-year-old will not find a menu. The night it mattered, the button was pressed, and within seconds the guard's tablet was alarming, three of us on the committee were called, and the guard arrived already seeing the resident's blood group and her cardiac history — which the law allows only during the emergency itself, and which sealed again afterwards. Second, and I insisted on this, it must never pretend to be the ambulance. The team was honest from the first meeting: this works alongside 112 and 108, it does not replace them. It bought us the minutes around the 108 call — the gate open, the lift held, her doctor's number already dialled. A vendor who'd promised it could replace the emergency services, I would not have trusted."
What every Hon. Secretary and resident asks before trusting a society with a one-tap emergency button.
We'll show you one-tap dispatch from a bedside button, the six-channel parallel alert, category routing, and the medical profile surfacing on the guard tablet under DPDP §17(1)(c) — working alongside ERSS 112 — on your society's actual setup.
See SOS Alerts →