The chat layer adds real-time one-to-one and group conversations inside your application. It powers user-to-user messaging, support chat with operators, and broadcast chats inside teams, projects or organisations.
Conversation Types
- Direct (1:1): A private thread between two users.
- Group: A persistent thread with multiple participants and a name (e.g. “Project Tigris team”).
- Topic-scoped: Anchored to a record — e.g. a chat thread tied to a specific support ticket, project or order.
What's Delivered in Real Time
Messages, read receipts, typing indicators and presence (online/offline) are all delivered over the platform's WebSocket connection. Users who are offline at the time still receive the message via push notification (if enrolled) and can read it next time they sign in.
Example Deployments
- Field service app: Engineers chat with dispatchers in 1:1 threads, and an “Incidents” group lets the operations team broadcast to all engineers on shift.
- Marketplace: Buyers and sellers communicate inside the platform without exposing personal contact details. Each thread is anchored to the listing.
- School portal: Teachers run a group chat per class, and pastoral staff have 1:1 threads with parents.
Moderation and Retention
Administrators can configure message retention (e.g. delete chats older than 12 months), keyword filters that flag or block messages, and per-group banned users. Every action is recorded in the activity log.
Note: Disabling chat does not delete existing messages. Use the retention settings or a one-off bulk delete from Site Settings → Communication → Chat if you need a clean cutover.