01
Conversation volume
Counts are derived from persisted tickets and messages within the selected workspace.
Understand your support activity, from the questions coming in to the work that needs attention. Follow the signals back to the conversations.
Conversations are grouped by time and channel. Open the underlying work to understand what changed.
Your live reports use your workspace activity.
Counts are derived from persisted tickets and messages within the selected workspace.
Operational timing uses real message and ticket state timestamps rather than showcase values.
Website and connected provider conversations remain attributable to their source.
Unanswered patterns and source performance help owners decide what information to improve.
A ticket count alone cannot explain why customers wait, which channel creates demand, or where the knowledge base keeps failing.
Volume, response, resolution, channel, and knowledge signals stay connected to the conversations that produced them.
A message becomes a tenant-scoped conversation.
Message and ticket events contribute to operational metrics.
Owners review demand and response patterns.
The team updates knowledge, staffing, or automation.