Operational summary
Fleet chat (/fleet/chat) centralizes messaging between the operations center and each identified node.
Messages are tied to organization and node id, so threads remain coherent even if the handheld operator changes, as long as the hardware keeps the same node id.
Deep dive
Fleet chat (/fleet/chat) is the bidirectional communication tool between the operations center and identified nodes. Unlike WhatsApp or generic radios, messages are tied to organization and specific node, allowing reconstruction of conversations even when the operators assigned to a device change.
That per-node persistence (not per user) is a key design decision. In real operations, the same handheld can pass through several operators in a week—rotating shifts, replacements, team swaps. If chat were tied to the user, you'd lose context about that unit. Tying to the node makes the thread follow the device: when the incoming operator looks at chat, they see the unit's operational history.
Messages are tagged by source: admin (sent from web), node (originated in the operator's mobile app). That distinction enables audit and lets you build flows like 'all instructions from center to unit 12 in the last 48 hours'. For later incidents, that trace is valuable.
Usage tips: chat is for short, specific coordination ('confirm arrival at point X', 'send me a photo of the lock state'), not for critical emergencies. For real SOS, follow your SOP's voice protocol in parallel with the dashboard SOS flow. Chat stays as complement, not substitute. Keep it clean: clear, brief, actionable messages. That preserves usefulness when volume grows.
Key takeaways
- Dashboard users send as admin; field-originated messages appear as node in history.
- Use chat for short coordination; for critical incidents still follow voice protocol and the dashboard SOS flow.
Open in product