Talkgroup management basics

Radio people already understand channels. Software PTT just makes them easier to create and visible on a dashboard. The hard part is design, not the button.

List how teams actually work: north route, town centre, gate A, maintenance on call. Each gets a talkgroup. Resist putting everyone on one main channel unless the operation is genuinely tiny. Noise drives people back to personal mobiles, which is exactly the habit you are trying to break.

Add a separate logistics group only if supervisors truly need it. Every extra group is another place someone can leave a mic open, and another line item supervisors have to remember when briefing new staff.

Designing talkgroups around real shifts, not org charts

The instinct when setting up talkgroups is to mirror the org chart: one group per department, one per role. That rarely matches how work actually moves. A better starting point is the shift pattern itself. Who needs to hear who, in real time, to do today's job? A parks route needs its own crew to hear each other. It does not need to hear the town centre security channel, and vice versa.

Start with fewer groups than you think you need. It is much easier to split a busy group into two once you see where the noise actually comes from than to merge several under-used groups back together after staff have already learned the wrong habits.

Busy and idle

Busy means someone is transmitting or the channel is otherwise in use. Idle means the air is clear. Dispatchers use that to decide whether to pass information by voice or wait ten seconds before keying up.

Train field staff to release PTT promptly. A long hold blocks the channel the same way it would on hire radio, and the same discipline that works on RF radio works here without any real adjustment.

Permissions

Not every user should hear every site. A parks cleaner does not need the festival security channels in August unless you temporarily add them. Tenant admins assign membership and roles. One customer's groups never leak into another's, and role-based permissions mean a dispatcher can see across talkgroups while a field user only sees the ones relevant to their shift.

This separation matters more as an organisation grows. A five-person pilot rarely needs careful permission design. A fifty-person rollout across several sites does, and it is much easier to get that structure right from the start than to retrofit it once habits have formed.

After the first month

Sit with supervisors for a quiet hour. Which groups were silent? Which were chaos? Which incidents never got a channel assignment? Adjust before the habits stick. Most talkgroup structures need at least one revision after real use, and that is normal rather than a sign anything was planned badly.

Two people keying up at once gets the same arbitration you expect on radio. Wait for the channel to clear, and remind staff that the discipline problem is identical to the one they already know from RF radio, just visible on a screen now instead of invisible.

Naming groups so new staff understand them instantly

Name talkgroups after what staff already call the place or the shift, not an internal reference code. "North gate" works. "Zone 4B" does not, unless your team already talks that way on the ground. The best test is whether a new starter can match a talkgroup name to where they are standing within the first few minutes of a shift, without anyone explaining the naming system to them first.

This matters most on temporary or agency-heavy shifts, where staff have no existing familiarity with your internal structure and are relying entirely on what they hear in briefing matching what they see on the app.

Common questions

How many talkgroups should we start with? Fewer than feels complete. Match them to how your team actually splits up on a normal shift, and add groups later once you see where communication genuinely breaks down.

Can talkgroups change between shifts? Yes. Membership is set by tenant admins and can be adjusted as often as your operation needs, for example adding parks staff to a shared group only during a joint bank holiday job.

Do talkgroups cost extra? No. Talkgroups are unlimited on paid tiers and included on the free tier for the first two users. See pricing for the full breakdown.

What stops one client's traffic reaching another's channel? Tenant isolation. Talkgroups belong to your organisation only, and there is no cross-tenant visibility regardless of how permissions are configured within your own account.

Talkgroups are configured in the RevoNet app after registration. Practical limits are about supervision, not software caps, so the real work is deciding how your team should be grouped, not how many groups the platform allows.