The hardest part of an emergency is hearing back
Sending an emergency alert is the easy half. The hard half starts one second later: who is safe, who needs help, and who hasn't answered at all? Ring-rounds collapse under that question. WhatsApp groups bury it. And “reply to this number” produces a wall of free text that someone has to read, interpret, and tally, all during the worst minutes to be doing any of those things.
That is why every whoot. emergency alert now carries a personal response link. Tap it and you're on a page built for exactly one job: telling your organisation that you are OK, or that you are not, in a single tap. It opens in any browser on any handset. There is no app to install, no account to create, and no password to remember at 2am.
The questions on the page are yours. “I'm safe” and “I need help” are the classics, but the wording, the options, and what each one means are set by your workspace, so the answers come back structured, countable, and instantly meaningful on the roster.
The page is not a one-way form, either. When the control room posts an update, such as “move to the north car park”, it appears on every open response page the moment it is posted, with a flash and a chime, and operators can see who has actually seen it. The page keeps the screen awake while the incident is live, because a locked phone helps nobody.
One link per person accounts for everyone
Everything the response page does, from the first tap to the final report.
- A personal link in every alert
- Each recipient receives their own unique link in the alert SMS
- Short enough to keep a typical alert inside one text segment
- Opens in any browser, with no app, no account, and no password
- One-tap status replies
- Your question set and your wording: "I'm safe", "I need help", or anything else
- Structured answers, not free text someone has to interpret
- A response can be updated if the situation changes
- Operator updates, pushed live
- Updates from the control room appear on the page the moment they are posted
- A flash and a chime ensure they are noticed
- Read receipts show operators who has seen each update
- Live location, with consent
- One clear tap to start sharing; it is never silent and never assumed
- Positions stream to the incident map while the page is open
- A pause control stays on the page the whole time
- Built for a real emergency
- The screen stays awake while the incident is live
- Works on any handset with a browser, old or new
- Guided fix steps if the phone's location services are off
- Everything on the roster
- Every tap lands on the accountability roster in real time
- Delivery, opens, responses, and updates in one timeline
- A complete comms log, ready for post-incident review
An alert is only over when everyone has answered.
Built carefully for the worst day
A page that people open in a genuine emergency has to earn trust twice: from the person tapping it, and from the organisation relying on it. Response links are unique to one person and one alert. Location sharing never starts without an explicit tap, and a pause control stays on the page for as long as it is open. Every response, every update, and every receipt is logged, so when the incident is over you have a complete, reviewable record of who was told what and when, which is exactly what an incident debrief or a Martyn's Law review asks for.
- Response links are unique per person and per alert, so they cannot be guessed or reused
- Pages are excluded from search engines and never leak the token to other sites
- Location sharing starts only after an explicit tap, and can be paused at any time
- The server re-authorises every single update; nothing relies on the client
- Every response and every operator update is logged for incident review
- Works alongside SMS keyword replies, so people can still simply text back