Multi-channel
Join the conversations that matter and see who is connected.
push.tt / Solutions
In beta
Dispatch the whole operation from one live screen
Monitor several channels, divide inbound calls across a shared queue, see the fleet on the map and answer without leaving your keyboard.
3channels joined
8units visible
Spacepush to talk
1shared inbound queue
In beta. The dispatch position and shared inbound queue ship together. It is a real push-to-talk client — same live connection, audio format and encryption as the handsets — with the remaining beta limits named below.
A working position, not another dashboard
Everything the dispatcher needs to hear, read and locate
Built around the live conversation rather than reporting after the fact. The current screen keeps channels, floor state, fleet position and message context together.
Keyboard PTT
Hold the space bar or use the on-screen talk control.
Fleet view
See managed units, last report, battery and accuracy.
Shared queue
Claim inbound calls once and measure response across the team.
01 · Dispatch Hub
Modern dispatch, without the radio clutter
The browser becomes the dispatch position. Channels, live traffic and the talk control stay in one working view, built for somebody who remains there all shift.
- Monitor several channels at once — join what you need, leave what you do not, and see how many people are on each
- Hold to talk with the mouse or the space bar; the talk control can float over the map if you would rather watch that
- Radio tones on transmit and receive, because the talk-permit tone is what tells you the floor is actually yours
- One person talks at a time, exactly as on the handsets — the desk does not get to jump the queue
02 · Dispatch Hub
The fleet, where the dispatcher is already looking
Position is not a separate product with its own tab. It is the ground the dispatch screen is built on, so "where is Truck 3" and "talk to Truck 3" are the same glance.
- Last known position per unit, with accuracy, battery and how long ago it reported
- Units only appear when a handset is enrolled in Device Manager with location switched on — an empty map outside working hours is the feature working, not a fault
- Live video from the scene alongside the map, so several people can broadcast while you keep talking
- Voice and text in one channel log, with any stored transmission replayable from the row
03 · Dispatch Hub
Read first. Claim together.
Voice is fast to send and slow to consume. Queue-enabled channels turn each finished inbound transmission into shared work, while the original encrypted recording stays in the channel log.
- Transcription runs on the sending device, so the transcript is encrypted with the message
- Every dispatcher sees the same list, and when one of them takes a call the others are told it is handled — two people can never pick up the same one
- Release returns a call to the team, resolve closes it, and the server measures arrival-to-claim and arrival-to-resolution without reading the traffic
- Workload reporting covers inbound volume, peak hours, response percentiles and per-dispatcher handling
04 · Rollout, stated plainly
The limits you should know before rollout
Two browser constraints remain. The third point explains exactly when a live transmission becomes shared queue work.
A new dispatch desk has to be let in. Encrypted channels are locked to the devices already in them, so a browser you have just opened cannot hear them until an existing handset lets it in — two taps on the phone, under Profile → Accounts. Until then those channels say "waiting" rather than playing silence at you
Use a current browser. Chrome, Edge, Safari 16.4+ and recent Firefox can play everything. An older one is told plainly that it cannot play a stream, rather than playing noise — and what the desk sends is always understood by every handset
A call joins the queue when the caller stops talking. Everyone monitoring still hears it live as it happens; the moment it is saved it becomes a job somebody can pick up, resolve and be measured on
Solutions · push.tt
Bring us your busiest shift
Show us the channels, the traffic and the decisions your dispatchers handle now. We will map that workflow onto the current position and call out any gap before rollout.