Push-to-talk for approved field users
The PTTHex Client app gives field users the operational surface for channel selection, PTT audio, notices, maps, SOS requests, hotkeys, prepared messages, and local settings after Customer Panel policy allows access.
Field team workflow
The app stays behind Customer Panel approval, channel permission, device state, and runtime admission before live PTT begins.
What field users can do
The Client app is the field user's tool for daily communication. It is not an admin console, and it does not set policy: what a user can do is decided by the Customer Panel.
Press, hold, release PTT
Users speak after joining an approved channel and receiving the required admission state. The app handles busy, denied, timeout, active speaker, and reconnect states.
Approved channels
The app shows the channels a user is approved for. A saved copy keeps the list quick to open, but it does not grant the right to join or speak on its own.
Notices and prepared messages
Field users can receive notices and use prepared messages where Customer Panel policy and channel controls support that workflow.
Policy-led map context
Location workflows require customer policy, platform permission, and approved telemetry settings. Background location is not marketed as generally available.
SOS request path
SOS behavior depends on Customer Panel policy, channel permission, and active approved session state. The client requests priority but does not create emergency authority by itself.
Supported app surfaces
The app runs on Android, iOS, Windows desktop, and web, and works within each platform's rules for background activity, permissions, and audio.
Calling and dialer
Place internal calls to other users and external calls over the customer's phone lines. Policy checks can deny a call before it connects, and call history is kept without storing the audio.
Messaging and announcements
Direct and channel messages plus read-only announcements from a prepared set. Read receipts show what was seen, and messages queue offline and send once the connection returns.
SOS with a clear lifecycle
An SOS moves through open, acknowledged, escalated, and resolved so field users can see where their request stands. Emergency alerts are never silently dropped and can't be silenced by preferences.
Live map and location sharing
See a live map, team presence, and geofence status. Sharing your own location is consent-based and can be paused, and users outside your scope can't see your position.
Live translation and captions
Live translation and on-screen captions help people on different languages understand each other. This runs on the customer's own server, stays consent-gated, and does not retain the raw audio.
Works on the devices your teams use
The same field-user app runs across the platforms teams already carry. Which platforms are allowed is set by the customer's license, and every device still needs customer approval before it gets access.
Android
Phones and rugged handhelds for daily field work.
iOS
iPhone and iPad for teams on Apple devices.
Windows desktop
A desktop app for control rooms and fixed positions.
Web
A browser client for approved users without an install.
Built to stay reliable in the field
Field conditions are not always ideal. The app is designed to keep working through weak coverage and to be honest about what it can and can't do at any moment.
Offline message queueing
Messages you send while offline are held on the device and delivered once the connection returns, so nothing is quietly lost when coverage drops.
Emergency alerts always come through
Emergency notifications take precedence over other messages and can't be silenced by personal preferences, so urgent alerts still reach the people who need them.
Honest connection status
The app shows real connection and quality state instead of a false healthy signal. Stale positions are marked as stale, so what you see matches what is actually happening.
How the app stays controlled
The Client app works from a verified Customer Panel profile, keeps sensitive session data in secure storage, and stops rather than opening access when approval, license, channel permission, or zone policy is missing.
- Device registration can show pending, rejected, disabled, or approved states without granting local access by itself.
- A voice session opens only after the Customer Panel grants short-lived permission to talk.
- Offline queues and cached display data do not create PTT, SOS, map, telemetry, or media authority.
Plan the app rollout
Bring device types, team structure, channels, site constraints, and onboarding needs. PTTHex can help define which app workflows should be enabled first.