A button that has to work

Volunteer response, event medical, site rescue and security teams. push.tt is built so that an alert is a state somebody has to clear, not a chime that can be missed in a pocket.

Try for free Contact us

Shipping now. Everything described here ships today. Read the limits section before you rely on it: push.tt is not a certified public-safety system, and this page says so rather than leaving it to be discovered.

The current talk screen with the emergency control above the ring

An emergency is a session, not a message

A one-shot alert can be missed by somebody whose phone was in a pocket. On push.tt it is state: raised, acknowledged, and cleared, each a separate act.

A red banner persists for every member until it is cleared — acknowledging does not clear it
The raiser takes the floor even if someone else is mid-sentence, and the displaced speaker is told why
A handset that reboots mid-alarm still sees the active emergency when it reconnects
Clearing can be restricted to moderators and org admins

It gets through Do Not Disturb

An alert that a teammate's phone silences is worse than no alert. Emergency deliberately overrides Busy, Solo and channel mute.

Bypassing Do Not Disturb needs Notification Policy Access, which the user grants once in system settings
Because it bypasses, it has real abuse controls: one active alert per person per channel, a cooldown, an hourly cap, and an org-level off switch
Every raise, acknowledgement and clear is written to the audit trail

Emergency events in the console audit log

Limits, stated plainly

This is the page where overstating things would do the most harm, so here is what push.tt is not.

Not a certified public-safety system. It is not P25, not TETRA, and carries no availability guarantee. It runs on commercial data networks and stops where they stop
No location in the alert yet. Location messages are in the protocol but the client work is unfinished, so an alert tells you who and which channel, not where
On a private channel with no org escrow, an administrator cannot read the alert body — that is the encryption working as intended, and it means dispatch visibility has to be a deliberate, consent-gated choice

If your service has a statutory duty, treat push.tt as a supplement to your primary system, not a replacement for it. We would rather say that here than in an inquiry.

Talk to us about your deployment

Tell us what you are covering and what you are covering it with. We will be straight about whether this fits.

Talk to us