Sub-4s median dispatch

The right responder, on the right channel,
in under four seconds.

Buddy auto-dispatch turns an SOS into a ranked, parallelised, multi-channel responder blast — with Claude in the loop on the ranking and a human dispatcher in the loop on every action. Sub-4s median, audit-trailed end-to-end.

From trigger to first ack

Five steps. Median end-to-end under four seconds.

Each step is independently observable in the audit log — and the timing budget for each is enforced by a circuit-breaker that escalates to a human if any single hop exceeds its SLO.

  1. 0.0sStep 1

    SOS fires

    Worker triggers — physical button, wake-word, fall detect, watch crown long-press or panic gesture. Trigger source is logged.

  2. 0.3sStep 2

    GPS shortlist

    Howie pulls every responder within 1.5km of the worker's last fix, filters by role (first-aid, fire warden, security) and on-shift status, and shortlists up to 8 candidates.

  3. 1.2sStep 3

    Claude re-ranks with rationale

    Claude Opus 4.7 re-ranks the 8 with one-line reasoning per candidate — distance, training, last-seen freshness, gradient between worker and responder. Top 3 wired for dispatch.

  4. 2.1sStep 4

    Parallel channel blast

    Push + SMS + WhatsApp + voice all fire concurrently to all 3 responders. Each carries ETA, what3words, severity badge, deep-link to navigate.

  5. <4sStep 5

    First ack lands

    Median first-responder acknowledgement is sub-4 seconds end-to-end. The other 2 are auto-stood-down with a courtesy notification. Audit log captures the full chain.

Why parallel, not sequential

One channel can fail silently. Four can't.

The single biggest failure mode in lone-worker dispatch is a channel that thinks it delivered. Push notifications get killed by aggressive battery savers. SMS gets eaten by anti-spam filters. WhatsApp goes unread for 40 minutes. Voice calls time out when the phone is on silent.

Buddy auto-dispatch fires all four at the same time, to the top three responders simultaneously. The first ack wins. Everyone else is auto-stood-down. You never wait 30 seconds for a push that was never going to land.

Real-world delivery

Across our last 90 days of live escalations, at least one of the four channels delivered within 4 seconds for 99.4% of SOS events. The remaining 0.6% triggered the human-dispatcher escalation path inside 8s.

Push

~0.4s

First to land for any responder with the worker app open or backgrounded — but silently fails if they backgrounded the app 14 days ago and iOS killed it.

SMS

~1.8s

Survives a dead app, a dead data connection, a dead operator network (carrier failover). 99.4% delivery against our 90-day rolling window.

WhatsApp

~2.1s

Highest read-receipt rate of any channel — and the only one most off-shift responders glance at out of hours.

Voice

~3.0s

Synthesised call that reads the brief and confirms ack via DTMF. Survives a phone that's silenced for everything except calls.

What lands on the responder's phone

No app required. Tap once. Navigate.

Every alert carries the four things a responder needs in the first three seconds: who needs help, how bad, where exactly(what3words plus what-was-around-them context from Howie), and one tap to navigate.

  • Open in Apple Maps / Google Maps / Waze with one tap — no copy-paste.
  • Ack via push action button — no app launch needed.
  • Decline politely if you're 40 mins away; Howie escalates to the next responder automatically.
  • On-arrival auto-ping when GPS hits the incident geofence.
9:415G
SOS · CRITICALnow

Mei Tanaka needs help

Crash detect · HR spike · 230m NE of your last fix

///hatch.shape.spoon · ETA 2m walk
Push · SMS · WhatsApp · voice

See a fake SOS dispatch end-to-end.

Trigger one from the demo tenant — no real responders contacted, full chain visible in the audit log.