REC
//CLASSIFIEDOPS_COMPANION v3.0.1//CONSOLE.READY////
DEMO ENV
[M-02]

CHAT HUB

Tactical team communications — push-to-talk voice channels, text messaging, dispatcher broadcast, and a secure voice message vault.

// OPS_COMPANION FIELD MANUAL

Chat Hub replaces the fragmented mix of personal phones, SMS threads, and radio channels that most field operations still rely on. It brings all team communications into a single, audit-logged, role-aware platform — without requiring a separate app or subscription.

Inspired by the operational simplicity of walkie-talkies, Chat Hub's primary interaction is a single hold-to-talk button — zero learning curve for field technicians and drivers. More structured communications (text, file attachments, voice messages) are layered on top for roles that need them.

Channel Types

ORG-WIDE BROADCAST

Dispatcher-only send. All active field users receive the message simultaneously. Used for urgent operational alerts, weather holds, or site-wide instructions. Cannot be muted by recipients.

TEAM CHANNEL

Role-scoped group channel. Technicians share a channel; Drivers share a channel. Created automatically at org setup, membership managed by Administrator.

DIRECT MESSAGE

One-to-one voice or text messaging between any two users. Subject to the same RLS restrictions — a Technician cannot message a user outside their organization.

TASK THREAD

Automatically created per work order. All parties associated with that work order (technician, dispatcher, supervisor) can communicate within the thread, and all messages are sealed in the work order audit trail.

Push-to-Talk Voice

The primary UI element for field users is a hold-to-talk button — the same muscle memory as a physical radio. Voice is encoded as a compressed audio message and delivered to all channel participants in near-real-time over WebSocket. Unlike live radio, the message is also stored in the secure vault, so recipients who were offline will receive it on reconnect.

// PUSH-TO-TALK SPECS
Max message length3 minutes
Audio codecOpus (compressed, low-bandwidth)
Delivery latency< 800ms over LTE
Offline deliveryQueued — delivered on reconnect
StorageSecure vault — retained per org retention policy
Listen receiptSender sees timestamp of each recipient's playback

Secure Voice Message Vault

Every voice message, text message, and file attachment is stored in the secure document vault — encrypted at rest with AES-256, access-controlled by RLS, and linked to the sending user's identity and timestamp. Messages cannot be deleted by the sender after delivery.

Administrators can retrieve the full communication log for any user, channel, or date range for audit and compliance purposes. This is particularly relevant for regulated environments where verbal instructions must be traceable.

COMPLIANCE NOTE
Voice messages stored in the vault qualify as recorded communications under most provincial labour and safety regulations. The timestamp, sender identity, and channel are sealed and cannot be altered retroactively.

Dispatcher Broadcast

The Dispatcher role has exclusive access to the org-wide broadcast channel. A single tap sends a voice or text message to every currently active field user simultaneously, regardless of which channel they are monitoring. Broadcast messages are visually distinguished from direct messages with a red priority indicator.

Broadcast voice messages delivered via WebSocket to all connected clients
Recipients cannot mute or dismiss a broadcast — it plays immediately
Broadcast is logged with full recipient list and delivery timestamps
Offline users receive the broadcast on reconnect with an urgency flag