PTT for security companies

Security contracts turn on response times and whether you can show the client what happened. Voice gets the officer there. Logs and timelines show you sent the right person.

Radio hire hurts when every new retail unit or festival site adds terminals and opaque invoicing. Control still runs on one screen while GPS, if you have it, runs on another. Officers carry a radio, a personal mobile, and sometimes a clocking app that none of them talk to. None of that is a criticism of any one supplier. It is what happens when voice, tracking, and job records grow up as three separate purchases.

Putting voice and dispatch together means the person on the channel and the markers on the map are the same shift. Reassignment is faster when someone drops offline mid-patrol. Debriefs reference an incident ID instead of reconstructing a phone call from memory. Clients notice fewer "we think someone was nearby" conversations because stale markers show last known position rather than a guess.

Software does not replace SIA training, site SOPs, or police liaison where your licence requires it. It removes some of the admin drag around all three, but the accountability still sits with your control room, your procedures, and your officers.

What a control room actually gains

The practical change is fewer systems open at once. A control room supervisor watching one screen for talkgroup activity and map markers can reassign an officer the moment someone goes stale, rather than waiting for a radio call to confirm it. When an incident comes in, creating a job with an assigned officer and a timeline takes less time than radioing it in and writing it down separately afterwards.

For contracts with multiple sites, talkgroups per site keep officers from hearing traffic that is not relevant to them, while control still sees the whole picture across every talkgroup at once. That separation matters more as contract count grows, since a control room covering five sites cannot afford every officer hearing every other site's traffic.

Rolling out without breaking a live site

Pick one manageable contract for a pilot. Run parallel radio for a short overlap if the client expects it. Train PTT discipline before you collect the hire kit, not after officers are already relying on it.

The free tier fits a control room supervisor and one officer rehearsing on a quiet day shift. That is enough to learn whether your talkgroup layout matches how sites actually run, before you commit a whole contract to it. Most firms find the talkgroup structure needs one or two adjustments after the first week, which is exactly why a small pilot matters more than a big-bang rollout.

Segregating clients

Talkgroups per site or contract work for many firms. Some run separate tenants per major client when procurement demands hard separation, which keeps one client's users, incidents, and logs entirely apart from another's rather than relying on permissions alone.

For festival patterns specifically, see the event security write-up, which covers a three-day multi-zone deployment in more detail.

Lone worker policy stays yours. Pair voice with the check-ins and escalation paths your control room already uses. RevoNet gives you the presence and map data to support that policy; it is not a replacement for having one.

National firms with dedicated compliance needs should ask about Enterprise and a dedicated instance, particularly where a client's due diligence process requires infrastructure isolation on paper as well as in practice.

What clients tend to ask about

Clients who already know their own compliance requirements usually ask two things early: how data is separated between contracts, and whether the system produces something they can hand to their own insurer. The tenant model answers the first, and incident timelines answer the second, but it is worth having both answers ready before a client asks rather than working them out mid-contract.

Smaller clients rarely ask either question directly. They notice the practical difference instead: fewer "we'll get back to you" moments when they ask what happened on a specific night, because the answer is sitting in an incident record rather than needing to be reconstructed from a supervisor's memory.

Common questions

Does this replace our SIA obligations? No. Training, licensing, and site procedures remain entirely your responsibility. Software supports the operational side, not the regulatory side.

Can we keep radios as backup? Yes, and many contractors do during a transition or in specific zones with poor mobile coverage.

How do client reports work in practice? Incident records include creation time, assignment, and closure, which most firms use as the backbone of a client-facing timeline rather than reconstructing one from notes after the shift.

What if an officer's phone battery dies mid-shift? Their marker shows as offline, which is a clear signal for control to call them or reassign the nearest available officer rather than assuming they are still covering the zone.

Start with two users on the free tier and run a single quiet shift before deciding whether to move a whole contract onto it.