Skip to main content
The Messenger analytics dashboard shows chat deployment and adoption across Teams, Slack, Desktop, and Web. Use it to track rollout progress, find deployments that were enabled but never used, and see which channel your clients actually choose. Open it from Thread admin → General → Analytics.

What this dashboard answers

  • How many clients have Messenger deployed, enabled, and actively used?
  • What’s our activation rate — the gap between switching it on and clients using it?
  • Which platform is winning new rollouts, and is our pace accelerating?
  • How much chat ticket volume is each channel generating?
  • Which individual clients are deployed but quiet?

Filters and time windows

The Clients tab adds its own controls: search, a platform filter, and an active/inactive filter.

What’s on the dashboard

Overview tab

Six KPI cards: total deployments, enabled deployments, active deployments, activation rate, chat tickets in the last 30 days, and chat tickets all time. A 30-day momentum indicator compares recent chat volume against the prior 60-day average, so you can tell a genuine trend from a busy week. An AI-written summary of deployment health. Charts: a donut of deployments by platform, a grouped bar chart of total, enabled, and active deployments per platform, and a bar chart of ticket volume by platform across 30-day, 90-day, and all-time windows.

Channels tab

One card per platform — Teams, Desktop, Web, and Slack — showing total deployments, active deployments, activation rate, 30-day and all-time tickets, and average tickets per deployment. Platforms with no deployments show a not deployed state rather than being hidden, so you can see the channels you haven’t opened yet. A rollout section covering new deployments per month by platform, cumulative deployment growth, and a 100% stacked chart showing which platform is winning new rollouts each month. The rollout charts are capped to the trailing 12 months. An AI-written summary of rollout pace and channel mix.

Clients tab

A searchable, filterable, sortable table of every client deployment: platform, active or inactive state, ticket counts across each time window, share of 30-day volume shown both as a percentage and as a five-dot visual, first-deployment date, and last-activity date. The current filtered and sorted view exports to CSV.

Metric definitions

Things to watch

A low activation rate is the most actionable number here. It means chat is switched on for clients who haven’t started using it — usually an announcement problem rather than a deployment problem.
  • A platform showing “not deployed” is a deliberate state, not a data gap. Empty channels are shown rather than hidden so the unopened channel is visible.
  • Average tickets per deployment can be misleading on a small platform — a single heavy client will dominate it. Check the client table before drawing a conclusion.
  • The momentum indicator compares 30 days against the prior 60-day average, so it is deliberately slower to move than raw volume.
  • AI-written summaries are drafts. Review the wording before sharing one with a client.
  • Data refreshes daily, so a chat from today generally appears tomorrow.

Next steps

Deploy Messenger

Close the gap on clients who aren’t deployed yet.

Announce Thread

Fix a low activation rate with a client announcement.