Browser Console
The browser stays in charge
Dispatch keeps the full operational surface: channel, talkgroup, roster, map, alerts, messages, video requests, and service state.
Audio Companion
Desktop dispatch control. Radio-grade audio at the operator's hand.
One operator. Two endpoints. One dispatch presence.
Audio Companion lets a browser console pair with a correctly provisioned mobile or portable radio. The browser remains the command surface for maps, roster, talkgroups, messaging, video requests, and workflow. The radio handles receive audio, microphone capture, and hardware push-to-talk.
Browser control
Radio audio
Reverse pairing
One public identity
Browser fallback
Feature Overview
A dispatch console can now borrow the best part of a radio: the audio ergonomics.
Browser dispatch is strong for live control, visibility, and supervision. A rugged radio is strong for speaker output, microphone capture, physical PTT, and muscle-memory operation. The audio companion feature combines those strengths without turning the radio into a second dispatch console.
Companion Radio
The radio owns audio
When paired, the mobile or portable radio becomes the audio endpoint for RX, TX microphone, hardware PTT, and radio-style audio handling.
Why It Matters
Better dispatch audio without adding another visible unit to the operation.
Audio Ergonomics
Use the radio hardware operators already understand
Speaker, microphone, and physical PTT stay on the mobile or portable radio while the browser remains focused on control.
Control Room Focus
Keep maps and supervision on the desktop
The operator does not need to drive field workflow from a small radio screen during dispatch operations.
Single Identity
Other users still see dispatch as dispatch
The paired radio is hidden as a child audio endpoint, so field users do not see two online devices for one dispatcher.
Flexible Hardware
Not tied to one model
Any compatible radio that is provisioned with the companion capability can be used as the audio endpoint.
How It Works
Pairing is deliberately simple and does not require a camera.
Reverse pairing is the default. The companion radio displays a short code. The browser operator enters it. The server verifies that both endpoints belong to the same tenant and the same operator.
1. Browser
Operator signs in to dispatch
The browser session is the control endpoint and keeps authority for target selection and workflow.
2. Radio
Same operator signs in on the radio
The radio enters dispatch audio companion mode only when the provisioned device and operator are allowed.
3. Code
The radio shows a one-time code
No mandatory QR scan. This suits radios without cameras, cradled devices, and vehicle-mounted setups.
4. Pair
The browser accepts the code
The server checks tenant, operator identity, device capability, session role, and code expiry before pairing.
5. Operate
Dispatch controls, radio talks
RX and TX audio route to the companion radio while the browser remains the operational authority.
One Dispatch Presence
The system knows there are two endpoints. The field sees one dispatcher.
Internally, Secure Radio can track the browser control endpoint and the radio audio endpoint separately for authorization, health, and audit. Externally, the public operational identity remains dispatch. That avoids confusion in the roster and prevents a companion radio from looking like an independent field user.
Internal
Two child sessions
- Browser control session
- Companion radio audio session
- Separate health and audit detail
- Same tenant and same operator
External
One public dispatch identity
- One dispatch roster presence
- TX labelled as dispatch
- No duplicate visible device
- Browser fallback when unpaired
Provisioning Model
A radio can be a normal mobile unit on one shift and an audio companion on another.
The feature is not a permanent device type. A provisioned radio remains a radio. Admins can enable the audio companion capability, and the current session role decides whether the device behaves as a field unit or as a dispatch audio endpoint.
Normal Mode
Visible field radio
Used by mobile staff as a normal Secure Radio field device, visible in roster and operating independently.
Companion Mode
Hidden dispatch audio endpoint
Used by the same dispatch operator as the audio half of the browser console, hidden from normal field rosters.
Admin Control
Capability must be enabled
Only correctly provisioned radios can request companion mode. Dispatch and gateway device types cannot be used as audio companions.
Controlled Rollout
Enable only where it fits
The capability can stay disabled for teams that want current behaviour unchanged, then be enabled selectively for approved operators and devices.
Security And Governance
Pairing is controlled, operator-bound, and audit-ready.
Controls
Designed to avoid split-brain dispatch
- Same tenant verification
- Same operator verification
- Short-lived one-time pairing code
- Admin-enabled device capability
- Browser-controlled target state
Audit Detail
Public identity and physical endpoint can both be recorded
Recipients see dispatch. Operations owners can still review which browser, which radio, and which operator were involved in the paired session. That gives the feature useful accountability without confusing the live roster.
Best Fit
Useful where desktop control and radio audio both matter.
Events And Venues
Temporary command desks with noisy surroundings
Keep the incident view on a laptop while the operator uses a radio for louder audio and physical PTT.
Facilities And Campus
Supervisors who need a working control surface
Use the browser for jobs, units, locations, and messages, while the companion radio handles the talk path.
Transport And Critical Sites
Control posts where headset audio is not always ideal
Pair a radio when the operator needs direct, tactile audio controls without losing the browser console.
Operating Guardrails
Designed to keep dispatch control clear.
Audio Companion is designed around paired dispatch audio for channel and talkgroup workflows. Browser control remains the source of truth, and browser audio fallback stays available. Private companion TX is introduced only when the full private-call experience can preserve the same identity and safety rules end to end.
Best for:
teams that want desktop or tablet dispatch control with radio-style audio hardware at the operator's hand.
Next Step
Evaluate whether audio companion fits your dispatch workflow.
We can walk through your dispatch desk, radio hardware, user roles, and pairing model, then decide whether this feature belongs in your evaluation plan.