The tone drops.
Everyone knows.
Dispatch alerting that reaches your members wherever they are.
Respond turns a CAD dispatch into a phone that speaks the call out loud, a watch that taps your wrist, a car screen already routing to the scene, and a station board that shows who’s rolling — all from the same live feed.
Built natively for the devices responders already carry
Not one web app stretched across six screens. Each surface is a real native app, sharing one live incident stream — so the wrist, the dash, the rig and the wall never disagree about what’s happening.
iPhone & Android
Native apps, not a wrapped website. The live call board, full incident detail with units and CAD notes, and one-tap “I’m responding” with your destination and ETA.
Apple Watch
A haptic on the wrist the instant the page hits. Read the call, see who else is coming, and mark yourself responding — without digging your phone out of a coat pocket.
CarPlay
The call list on the car’s own screen. Tap it, and you’re responding with turn-by-turn navigation already running — while new CAD notes are read aloud over the nav audio.
Live Activity & Dynamic Island
The active call lives on your lock screen for the whole run: priority, call type, address, running clock, and how many members are responding. No unlocking, no app switching.
Apparatus iPad
A rig-mounted app that signs in as the apparatus and stays signed in — deployable by MDM/Jamf, guided-access friendly. On dispatch it pulls up everything for that call automatically.
Station Wall Board
An Apple TV app for the 4K display on the apparatus floor: live calls, unit status, weather and wildfire conditions, department cameras, and a full-screen incident command takeover when a call drops.
Respond in the wild
A station alerting system, in your pocket
Most apps give you a ringtone. Respond gives you staged alerting you control per member — and a phone that actually says the call out loud.
Pre-Alert
Fires the moment your jurisdiction is signed to the call — the earliest possible heads-up, before the dispatcher tones out. Optional, because it can occasionally turn out not to be yours.
Dispatch
The confirmed page, fired when your paging unit is assigned. This is the one everybody gets, with your chosen tone from a bundled library.
Spoken aloud
“Structure fire — 123 Main Street.” The dispatch is voiced on arrival, generated per call. You know what you’re going to before you’ve found your glasses.
Through silent & Focus
Dispatch alerts break through Do Not Disturb, Focus modes and the mute switch — deliberately reserved for one stage, so critical stays critical.
Off duty means off duty
A master availability switch plus snooze (an hour, eight hours, or until you turn it back on) takes you out of the recipient list — no muting the whole phone and missing the next one.
Neighboring calls, if you want them
Your department already tracks its neighbors’ calls on the board. Members can opt in to alerts for those, rule by rule — off by default, and never critical.
Know who’s coming — and when they’ll be there
“Responding” on its own doesn’t tell an officer much. Respond shows every member moving on the incident map, with an ETA that recalculates as they drive.
The roster ranks by arrival, calls out who’s first-in, and splits station-bound from scene-bound — so an officer can commit to a plan before anyone’s on the apron.
- Live positions on the incident map — every responder as a moving pin, not a static list of names
- Route-based ETA — real drive time to the station or the scene, recomputed en route
- Your personal average — historical response times become the smart default ETA, instead of everyone guessing “five minutes”
- Automatic arrival — getting there marks you arrived and stops sharing, without a second tap
- Sharing on a timer — location is opt-in per response and expires automatically. Respond is not a tracking app that happens to do dispatch
- Apparatus on the map too — rig-mounted devices report position, so the board shows units and people together
Your radio runs the fireground.
Respond runs the drive to it.
Respond carries what the radio can’t — who’s coming, how far out they are, and what dispatch typed after you rolled. That first page arrives over cell or Wi‑Fi, so it needs a connection. Everything after it is built to survive the dead zones a mountain response drives straight through.
The dispatch stands on its own
Once the alert lands it carries everything needed to run the call — type, priority, address and coordinates. Drive into a dead zone, open it there, and you still get the details and directions to the scene.
Nothing gets dropped
Tapping responding, on-scene or cleared with no service queues it locally — stamped with the time you actually tapped — and delivers in order the moment signal returns.
Honest status, never frozen
When a member goes dark, the board says “last seen 07:52” instead of leaving a stale ETA ticking. Nobody shows as “two minutes out” forever.
The information you’d otherwise be asking for over the radio
Hydrants on the map
Import your department’s existing hydrant data and see the nearest water supply on the incident map — with flow, size and out-of-service status, available offline.
Caution & address notes
Dispatcher caution notes plus your own officers’ notes on an address — the gate code, the aggressive dog, the access quirk — surfaced automatically when a call comes in there.
CAD notes worth reading
Machine chatter — unit status lines, timestamps, codes — is filtered out on the glanceable surfaces, so what you see and hear is what a human actually typed.
Navigate with what you use
Apple Maps, Google Maps or Waze on the road — and Gaia GPS or CalTopo when the call leaves the pavement for a backcountry rescue. Coordinates in the CAD notes are tappable.
Incident command view
A full-screen command picture on the wall board or the rig: assigned resources, unit positions, and a map you can zoom out on to see the approach, exposures and water supply.
Calls you can read at a glance
Every call is classified — medical, fire, MVA, hazmat, rescue, alarm — from a taxonomy built against tens of thousands of real dispatches, so the district map reads instantly by color.
What sets Respond apart
Response apps have looked the same for a decade. These are the places we went further.
Spoken dispatch, not a ringtone
The established apps break through silent mode with a tone you picked. Respond speaks the actual call — problem and address — the way a station alerting system does.
ETAs from data, not guesses
A typed-in “5 minutes” is a guess. Respond routes from where you actually are and learns your real average to that station.
Offline treated as normal, not an error
Most apps assume coverage and show a network error when it’s missing. Respond queues, replays and degrades honestly — because half our members lose signal on a routine run.
One system, from wrist to wall
Your station board, your apparatus, and every member’s phone run the same live feed — instead of a paging app here, a whiteboard there, and a TV showing something else.
Connected to the rest of the station
Respond stands alone, but with the full stationOS suite the same calls flow into your NERIS reports, and turnout feeds your personnel records. No re-keying what already happened.
Built by someone on the roster
Every feature here came out of a real call or a member’s complaint — including the ones that only show up at 3am on a mountain road.
Get Respond in your members’ hands
Available on its own, or as part of the full stationOS suite. Departments are running it today, with the public App Store release landing shortly.