For the people who work on their own

A guard on a night patrol, a technician in a plant room, a driver at a depot at 3am. push.tt watches for a fall, for a long stretch without movement, and for a missed check-in — and if nobody answers, it raises the alarm for them.

Talk to us about your crews How alerts reach people

In beta. Android is built and in beta. Detection runs on the handset and no sensor data is sent to push.tt. iOS is not built. This is not a medical device and does not replace an emergency service — read the limits below before you rely on it for anybody.

Three ways somebody gets missed

Each answers a different failure. A crew that only has one of them has a gap in a predictable place, which is why they are separate switches rather than one.

Automatic fall detection. The handset watches for the signature of a real fall — free fall, impact, then stillness. It asks if you are okay, and raises an emergency if you do not answer
No-motion detection. If somebody who should be moving has not moved for the period you set, the same check runs. This is the one that catches a collapse that was not a hard fall
Periodic check-in. A scheduled "are you okay?" for the whole company or for named groups. It catches everything the sensors cannot — including a handset that was left behind

What actually happens

The same sequence in all three cases, and the countdown is the part that matters: most detections are false alarms, and a person who is fine must be able to say so in one tap.

The handset asks "are you okay?" — full screen, loud, and it says why it is asking
A countdown runs for the grace period you configured, from ten seconds to five minutes
"I'm okay" clears it. "Get help now" raises the alarm immediately, without waiting out the timer
If nobody answers, an emergency goes to your organisation in that person's name — through the same alert channel your team already uses, carrying what triggered it so a responder knows whether they are looking for a fall or a missed check

The limits, in plain terms

Everything below is a real boundary of what this can do. A safety feature oversold is worse than none, because somebody plans around it.

It is not a medical device and does not call an ambulance. It alerts the people in your organisation, who decide what happens next
Fall detection catches a hard fall, not every fall. A slow slump against a wall produces no free fall and no impact and will not trigger — that is what the check-in is for
A destroyed or dead handset raises nothing. No app can send an alert from a phone that is broken or flat, which is why the app also warns the wearer when their battery is about to end their reachability
It needs a working connection at the moment of escalation. The handset tells the person when it cannot reach the network, rather than letting them believe they are covered

Who decides, and what the worker is told

These features watch how somebody moves for a whole shift, so who controls them is part of the design rather than a setting buried in a menu.

The organisation chooses per feature: off, optional, or required. Optional lets the worker decide; required means they cannot switch it off
Required is never silent. The handset shows the worker it is on and names the organisation that required it. A phone monitoring somebody while showing them nothing would be lying about what it does
Turning it on for a whole company is consent-gated in push.tt: an administrator has to read and accept what it means for their members before it saves, and anyone invited afterwards is told before they join
Motion never leaves the handset. push.tt receives no accelerometer data, no step counts and no idle timings — only the emergency, if one is raised

It rides on the alerting you already have

An automatic alarm is only as good as what happens next, so these do not invent a parallel channel. They raise the same emergency a person raises by pressing SOS — the same people are notified, the same acknowledgement is required, and the same record is kept.

One thing for a dispatcher to recognise under pressure, not two
Alerts must be cleared by a person, so an automatic one cannot quietly disappear
The trigger travels with it, because looking for somebody who fell and somebody who missed a check are different searches