SOS confirmation and countdown: reduce accidental sends

Balance mistakes and delay

Confirmation reduces an unintended tap but adds a step. A countdown gives time to stop, yet it can delay help when applied to every situation without considering urgency and context.

Measure both risks with real people: how often they tap accidentally, how long they need to understand, and when they abandon the flow. Do not choose a number because it merely feels cautious.

Make the pre-send moment clear

In the 2.3 flow in development, ALL OK or EMERGENCY opens the countdown with recipients, location and message. Opening an option pauses it: nothing sends until Send now. Leaving while it runs cancels the attempt; after confirmed sending, background-work limitations apply instead.

Changed choices are saved only when sending starts. All OK may remember recipients for next time; SOS audience changes apply to that signal only. Messages are not remembered. Cancellation does not modify saved choices: practise pausing, sending and cancelling separately.

Confirmed location becomes the default for subsequent in-app All OK and SOS sends; the combined widget shares that preference. Dedicated widgets have their own settings. The widget countdown (10 seconds) and Apple Watch countdowns (5 seconds SOS, 3 All OK) allow cancellation, without the Home recipient, message and location editors.

In the 2.3 preview, only SOS adds “Share live location” during the countdown. Touching the control or choosing a duration pauses the timer; then send now or cancel. The choice carries over to the receipt and remains editable. Confirmation opens live setup: review recipients and permissions and confirm Start. The switch alone does not start GPS or sharing.

“Send current location” attaches one fix captured when sending; it is not live sharing. The separate live control appears only in real SOS, not the guided Demo flow. A simulation starts no GPS session and confirms no delivery.

Make cancellation unambiguous

During the wait, show that the signal has not left. “Cancel” should end that attempt and confirm that no new SOS was sent; do not hide it behind a gesture or icon.

During the countdown, “Cancel” stops the command. If connection is missing after confirmation, the command remains saved and can retry in the background without creating a duplicate.

Correct after sending with a new message

Once sent, the original does not become editable. If needed, send a separate update that says what it corrects and which recipients receive it.

Do not erase a delivered message while implying the emergency was cancelled. Show the relationship between original, correction, and observable status.

Separate technical status from human response

The receipt separates preparation, server request, notifications, and outcome. “Outcome not confirmed” means delivery is not confirmed yet, not that the command failed.

Keep language calm and direct: when the flow cannot know, state which fact is known and what still needs checking.

Test ordinary and urgent cases

Test an accidental tap, last-second cancellation, slow network, locked phone, and wrong recipient. Ask people to explain the result without coaching.

Test an accidental tap, last-second cancellation, no network, and reopening the app. After confirmation, do not force-close the app: the system may complete the command in the background.

Frequently asked questions