Before anything goes wrong
The alarm that raises itself.
A safety timer is a countdown a worker starts before a risky task. If they do not cancel it in time, an alarm is raised automatically. A check-in is the scheduled version: periodic prompts through a shift, where a missed prompt escalates to the monitoring centre. Both exist for the case where the worker cannot reach a button, and both run on all four Duress devices.
The problem it solves
Every button-based alarm shares one assumption: that the worker is conscious, has a free hand, and knows they are in trouble. A collapse, a car accident on a rural road, or an assault from behind breaks all three at once.
Timers invert the logic. Instead of the worker raising an alarm when something goes wrong, the system raises one when the worker does not confirm they are fine. Silence becomes the signal.
Step by step
- 1
Set the window
A safety timer is started by the worker before a specific task, a home visit or a remote drive. Check-ins are scheduled by an administrator in Pathfinder and run on their own through the shift.
- 2
The worker confirms, or does not
The device or app prompts for confirmation. Cancelling the timer or answering the check-in closes the loop silently, with nobody contacted and no fuss.
- 3
A miss becomes an alarm
No confirmation means the case opens at the monitoring centre automatically. The worker does not have to do anything, which is the entire point.
- 4
The operator works the case
The operator sees the last known location and the missed prompt, and works the escalation procedure configured for that site on the same 4-minute cadence as any other alarm.
What each device does
Including the ones that do not have it. A device paired to a phone does not inherit the phone's capabilities.
Duress App
Supported
Safety Timer for a single risky task, plus scheduled Are You OK? prompts that escalate on no response. Runs with the app closed and the phone locked.
See Duress App →Phoenix
Supported
A dedicated Check In button, one of its three physical buttons, with escalation handled through the paired phone.
See Phoenix →Falcon
Supported
Configurable timers that auto-escalate on the device's own connection, so a phone left in a vehicle changes nothing.
See Falcon →Eagle
Supported
Configurable timers, auto-escalating, on a device built for week-long deployments away from a charger.
See Eagle →Comparing devices rather than features? The full comparison table puts all four side by side, or the device selector asks six questions and recommends one.