[Developers]

Collaboration Real-Time Messaging: Instant Team Communication Platform

When an analyst spots a link between two financial accounts that changes the direction of an investigation, they do not send an email and wait. They open a channel, post the finding, tag the relevant colleagues, and the

Category: CollaborationLast Updated: Feb 23, 2026
collaborationreal-time

Overview#

When an analyst spots a link between two financial accounts that changes the direction of an investigation, they do not send an email and wait. They open a channel, post the finding, tag the relevant colleagues, and the conversation happens in real time. Decisions get made in minutes, not hours. That is the practical value of real-time messaging in operational environments.

The Real-Time Messaging module powers the conversational layer of team collaboration with fast message delivery, group chat, direct messaging, @mentions, threaded replies, and emoji reactions. It replaces fragmented communication across email, SMS, and legacy chat systems with organised, searchable, and persistent team communication. The platform supports both Matrix Synapse and XMPP federated messaging protocols for organisations requiring cross-domain federation with partner agencies. All channels are scoped to the organisation; messages never cross tenant boundaries unless explicitly configured through a federated channel.

Key Features#

  • Instant Message Delivery: Messages are delivered in real time across all connected devices over WebSocket connections, with delivery confirmation, read receipts, and reliable ordering guarantees.
  • Direct and Group Messaging: Support for 1:1 direct messages, small group conversations, and large broadcast channels to accommodate all communication scenarios from private discussions to organisation-wide announcements.
  • Threaded Replies: Organise conversations with threaded replies that keep focused discussions contained without cluttering the main channel view.
  • @Mentions: Tag individuals, teams, or entire channels to draw attention to specific messages with priority notification delivery that cuts through routine noise.
  • Rich Media Support: Share images, videos, files, links with automatic previews, code snippets with syntax highlighting, and formatted text directly within conversations.
  • Message Search: Full-text search across all message history enables retrieval of past conversations, decisions, shared links, and files regardless of when they were posted.
  • Presence and Typing Indicators: Real-time presence detection and typing indicators show team availability, active conversations, and current engagement status.
  • Cross-Platform Synchronisation: Consistent experience across desktop, mobile, and web clients with synchronised message history, read state, and notification preferences.
  • Pinned Messages: Pin important messages to channel headers for easy reference, keeping key decisions, links, and announcements visible to all channel members.
  • Message Actions: React to messages with emoji, bookmark important messages, create tasks from messages, and share messages to other channels for efficient cross-team communication.

Use Cases#

Operational Coordination#

Investigation and incident response teams use real-time messaging for quick questions, status updates, and spontaneous problem-solving that is too time-sensitive for email but too informal for a scheduled meeting. The speed of text messaging combined with persistent, searchable history makes it the natural coordination layer for fast-moving operations.

Cross-Department Communication#

Dedicated channels for cross-functional topics enable departments to communicate and coordinate activities without cluttering individual inboxes or requiring formal communication processes. In multi-agency environments, federated channels allow partner organisations to participate without requiring accounts on the host organisation's platform.

Remote Team Engagement#

Distributed teams, including those supporting international joint task forces, maintain connection and social cohesion through casual conversation channels and real-time social interaction alongside work-focused communication.

Rapid Issue Resolution#

Support and operations teams use messaging channels for real-time incident coordination, enabling fast diagnosis, collaborative troubleshooting, and resolution through immediate group communication with full context preserved in the thread.

Knowledge Sharing#

Team members share articles, insights, and discoveries in topic-specific channels, creating a searchable library of shared knowledge that benefits current and future team members.

Workflows#

Channel-Based Communication#

  1. Create or join channels organised by team, project, topic, or interest area.
  2. Post messages, share files, and start discussions within the relevant channel.
  3. Use threaded replies to keep focused discussions organised within the channel context.
  4. Pin important messages and decisions for easy reference by all channel members.
  5. Search message history to find past conversations, shared files, and key decisions.

Direct Messaging#

  1. Start a direct conversation with one or more team members for private or focused discussion.
  2. Exchange messages with real-time delivery, read receipt confirmation, and typing indicators.
  3. Share files, links, and rich media directly within the conversation context.
  4. Message history is preserved, synchronised across devices, and searchable for future reference.

Cross-Channel Coordination#

  1. Discover a message in one channel that is relevant to another team or project.
  2. Share or forward the message to the appropriate channel with additional context.
  3. The shared message links back to the original conversation for full context.
  4. Follow-up discussions proceed in the destination channel with all relevant team members engaged.

Integration#

  • Programmable API Access: Send and receive messages programmatically for integration with bots, automation workflows, monitoring systems, and external notification feeds.
  • File Management: Share files from the collaboration platform directly within messages with preview generation, access control enforcement, and version tracking.
  • Video Conferencing: Escalate from text to video with one-click meeting initiation directly from messaging conversations.
  • Third-Party Applications: Receive notifications from connected applications, interact with external services through bot integrations, and automate routine communications.

Open Standards#

  • WebSocket (RFC 6455): All real-time message delivery, presence signalling, typing indicators, and read receipts are transported over persistent WebSocket connections; the platform enforces RFC 6455 close codes (e.g. 1008 policy violation) on authentication failures and cross-origin rejections.
  • Matrix Client-Server Specification (Matrix.org): The platform integrates with Matrix Synapse homeservers using the Matrix Client-Server API (v3 endpoints) for federated room synchronisation, enabling cross-domain channel federation with partner agencies.
  • XMPP Core (RFC 6120) and XEP-0045 Multi-User Chat: Messaging federation connects to XMPP/Jabber servers via the Multi-User Chat extension for persistent and temporary group channels; Jabber IDs are used as canonical channel identifiers.
  • JSON Web Token (RFC 7519): WebSocket connections and REST API calls are authenticated using JWTs carried as Bearer tokens or HTTP-only cookies; the collaboration auth layer validates credentials against the platform token service.
  • GraphQL (October 2021 Specification): All collaboration queries and mutations, including channels, notes, tasks, mentions, and entity locks, are exposed through a typed, introspectable GraphQL schema for clients.
  • ISO 8601 / RFC 3339 Date-Time Format: Message timestamps, presence last-seen times, and task due dates are serialised as ISO 8601 formatted strings throughout the collaboration service and WebSocket message payloads.
  • OAuth 2.0 Bearer Token (RFC 6750): The XMPP and Matrix integration clients authenticate to external messaging servers using Bearer token headers, and the platform's own WebSocket upgrade flow follows the same Bearer credential pattern.

Last Reviewed: 2026-02-23 Last Updated: 2026-04-14

Ready to Build?

Get started with our APIs or contact our integration team for support.