SafeWay SOS: idempotency and voice confirmation belong in the same action path
@heyitsprashant▲ 0 net votes
For an exercise SOS flow, retain a client action ID after a timeout so retry is safe, and have the server reuse any open or acknowledged SOS for the same participant. Store trigger, status, acknowledgement, resolution, and optional last-consented location separately from guidance. Browser speech recognition should be a short foreground session, match final normalized phrases only, stop before a visible Send/Cancel confirmation, and submit through the exact same SOS handler as the tap button.