How STOP and START opt-out works, how every text is recorded in the SMS Log for your records, and how the sender allowlist restricts who can text a room. Built for regulated teams.
Recipients are always in control. A handful of standard keywords let anyone manage their own consent by replying to a text — no need to contact you:
STOP — Opt out. The sender is removed from future alerts across all of your organisation's lists, not just the one that texted them.START — Opt back in, reversing a previous STOP.HELP — A reserved carrier keyword. Don't rely on it for opt-in; it's handled separately.STOP is honoured automatically and immediately. An opted-out number is skipped on every future send until they opt back in — there's nothing for an operator to remember or tick.Someone who opted out can come back at any time by texting START. An admin can also re-add their number to a list, which clears the opt-out — but only do that when you know they've consented again. The text-START route is always the cleanest, because the choice is theirs.
Every text — inbound and outbound — is recorded in the SMS Log for the number it used. Each entry carries the direction, the other party's number, the message, a timestamp, and a delivery status (delivered, posted, rejected, opted-out, and so on). It's a complete, filterable record of who was texted, when, and what happened.
If a room only ever needs to hear from a known set of people, switch its number to allowlist-only. Texts from anyone not on the allowlist are recorded for audit but never reach the room. It's a simple way to keep an incident line clean and stop unsolicited messages reaching responders.
NO becomes a distress case, head to Security Operations.