Team Chat
Use real-time chat for workspace, tour, event, project, and direct conversations.
Team Chat
Team chat keeps operational conversations close to the work they are about. If your plan includes chat, you can message across workspace conversations and entity-specific chats.
Conversation Types
Chat can be scoped to:
| Conversation | Use it for |
|---|---|
| Workspace chat | General team coordination |
| Tour chat | Tour-level decisions and updates |
| Event chat | Show-day questions, changes, and confirmations |
| Project chat | Project-specific collaboration |
| Direct or group chats | Smaller conversations between selected people |
Entity chats are useful because the conversation stays attached to the related tour, event, or project.
Messages
Chat supports:
- Real-time messages
- Replies
- Reactions
- Mentions
- File attachments
- Read state and unread counts
- Search across accessible conversations
Unread counts appear in the navigation and chat entry points so you can see when something needs attention.
Attachments
Use attachments for quick context such as stage plots, screenshots, settlement files, travel details, or reference images. Files shared in chat follow the same access model as the conversation.
Notifications
Chat activity can trigger in-app notifications and push-style prompts depending on your settings and device support. Mentions and direct conversations are the best way to make sure a message gets attention.
Access
Chat access depends on the workspace, plan, and conversation scope. Users only see conversations tied to workspaces and entities they can access.
Best Practices
- Use event chat for show-day updates instead of burying changes in a general thread
- Use tour chat for routing, staffing, or policy decisions that affect multiple events
- Keep external partner information in booklets unless they should become workspace members
- Attach files when they add context, but keep final reference documents in the Documents area