Slack Metrics

The Slack Metrics Dashboard shows Slack health, operational responsiveness, and burnout signals for your engineering organization. To open it, click Communication Tool in the left sidebar and select Slack. The dashboard reads data collected by the Slack integration, which syncs once a day. See Slack for setup. If no Slack connection is set up yet, the page shows Slack Connection Required with a link to the integration page. Everything on the dashboard is built from metadata and counts: who posted, where, when, and how quickly someone replied. No dashboard, chart, or report shows what anyone actually said.

Dashboard controls

At the top of the page:

Project filter: narrows the dashboard to the project a Slack connection is linked to. Leave it on All to see every connected workspace. On All, someone with an account in two workspaces is listed once per workspace, as Name (Workspace), because they can be active in one and not the other. Headcount and active users still count them once.
No page-wide Actor filter. A Humans and bots / Humans only / Bots only selector sits on the cards it actually filters: Weekly activity composition (message bars), Top collaborators and the Users activity list. Active-user figures always count humans only.
Date Range: pick a custom start and end date, or use the 7 Days, 15 Days, or 90 Days quick-select buttons. 90 Days is selected by default and covers the last three calendar months (from the first day of the month two months back). The quick-select buttons are disabled while a custom date range is set; clear the range to use them again. A custom range always shows daily data.
Export icon: downloads the current tab’s data as a report.

Below that, eight tabs organize the dashboard: Overview, Response Time, Inactive Users, Burnout & Risk, People & Collaboration, Channels, Departments, and Cost Savings. The Inactive Users and Cost Savings tabs follow the Project filter only; they ignore the date range. This guide covers each tab in turn, then explains how the metrics are calculated and how they differ by Slack plan.

Overview

Workspace-level KPIs, followed by activity and engagement trends.

Workspace KPIs

KPI	What it shows
DAU %	Average daily active users as a percentage of headcount, with the underlying figure underneath (for example, “0.13 of 16 headcount avg”). A person counts as active on a day when they posted at least one top-level message. Headcount is every non-bot member.
Avg First-Response	The average time to the first reply on a thread, across the threads in the period (for example, “across 5 threads”).
SLA Breaches	The number of threads whose first response took longer than 5 minutes, and what share of all threads that is.
Thread Response Rate	The share of threads that received at least one reply, shown with the thread count (for example, “5 of 5 threads”). A message only counts as a thread once someone replies to it, so this figure is almost always 100%. It does not measure unanswered questions. A reply from the person who started the thread counts.
Total Messages	Top-level messages posted in the period. Replies are not counted. Shows the split underneath: X by humans · Y by bots. See How metrics are calculated.
Cross-Team Threads	Threads where the person who started the thread and a replier belong to different departments, and what share of all threads that is. Needs department data, which is only available on Enterprise Grid.
After-Hours %	The share of messages sent outside 09:00–19:00 in each person’s own Slack time zone (the workspace’s when their profile has none).
Channel Churn Ratio	Channels created in the period divided by channels archived in the period, with both counts underneath (for example, “1 new : 0 archived”). Shows ”—” when no channel was archived.

Activity & Engagement Trends

DAU% and after-hours % — 30-day trend plots daily active users as a percentage of headcount alongside the share of messages sent outside working hours (09:00–19:00 local), over the selected date range, so you can see whether more activity is coming at the cost of more after-hours work.
Weekly activity composition shows Messages, Threads, and Active channels for each period of the selected date range.

Response Time

Shows how quickly threads get a first response.

First-response time by channel — p50 vs p90: a bar chart of each tracked channel’s median (p50) and 90th-percentile (p90) first-response time. Use Search channel to find a specific channel, or View Full List for the complete chart.
SLA breach detail: a table of channels sorted by breach rate. Columns are Channel, Threads, Response Rate, Breaches, Breach Rate, Avg, P50, P90, and Status. Click a column header to sort. Use Search channel or View Full List to browse more.

Status is based on the channel’s breach rate:

Status	Breach rate
HIGH	25% or more
MED	10% to under 25%
LOW	Above 0% and under 10%
OK	0%

The SLA target is a first response within 5 minutes. The chart subtitle may read “SLA = 15m”; the breach counts on this tab and on the Overview tab use 5 minutes.

Inactive Users

Shows Slack users (humans only) who haven’t been active recently, to help you spot disengagement and unused seats. A user is listed when they have not been active for at least the number of days set for Slack under Settings → Inactive User Settings (30 days if nothing is set), or have never been active. The tab shows the 10 most inactive users, with people who were never active first. Use Search user to find a specific person, or click View Full List to see everyone who meets the threshold.

Column	What it shows
User ID	The user’s Slack ID.
Name	The user’s display name.
Title	The user’s job title, if recorded on their profile.
Department	The user’s department, if recorded on their profile.
Inactive Days	Days since this user was last active, counted up to the last day the sync has fully processed (not today), so a late sync does not inflate the number.
Last Active	The date this user was last active.
Avg Msgs/Day (30D)	Their average messages per day over the 30 days up to their last activity, which shows how active they were before going quiet.

Burnout & Risk

Surfaces signals that may indicate burnout risk, plus a queue of alerts that need review.

Burnout Signals

Channels by after-hours % — burnout candidates: a bar chart of channels ranked by their average weekly after-hours share of messages over the selected date range. Bars are red at 30% or more (flagged), amber between 20% and 30% (watch), and green below 20%. Use Search channel to find a specific one, or View Full List for the complete ranking.
Top engineers by after-hours activity: a table of up to 10 engineers whose after-hours share of messages is 25% or more. It is scoped to humans only and explicitly intended for manager 1:1s only — not for performance reviews. Columns are Engineer, Messages, After-hrs Msgs, After-hrs %, and Risk. Risk is HIGH at 35% or more and WATCH below that. Use Search engineer or View Full List to browse more.

The chart subtitle may read “Threshold to flag: 20%”. The flag threshold is 30%. 20% is only where the amber “watch” band begins.

The “not for performance reviews” note on the after-hours table is intentional. This data is meant to help managers check in on wellbeing, not to evaluate individual performance.

Open Exception Alerts

Action queue lists the alerts for the selected date range, with the number of open alerts in its title. The alerts are calculated from the data each time you open the tab; there is nothing to assign or close. Each alert shows its type and severity, a title, and a short description. High-severity alerts are listed first.

Alert type	Raised when	Severity
Burnout	A channel’s average after-hours share over the range is 30% or more. The title shows the share and how many weeks were at or above 30%.	HIGH at 45% or more, otherwise MEDIUM
SLA Breach	A channel had at least one thread whose first response took longer than 5 minutes. The title shows the breach rate and the breach and thread counts.	HIGH at a breach rate of 25% or more, otherwise MEDIUM

The queue shows “No data for this period” when there is nothing to flag.

People & Collaboration

Looks at how people actually collaborate in Slack, not just how much they post.

Top collaborators — engineers who reply in threads: a bar chart ranking engineers by thread replies. As the subtitle notes, this measures collaboration, not broadcasting: someone who posts a lot but rarely replies to others won’t rank highly here. Switch the ranking between Replies, Messages, and After Hours with the metric dropdown, search by name, or click View Full List.
Users activity list — engineering roster: the top engineers (humans only) by messages, with Engineer, Messages, Replies, After-hrs, and After-hrs % columns. The list shows 15 by default; choose 5, 10, 15, 20, 25, or 50 with the Top N dropdown, and switch the ranking metric with the metric dropdown.
Slack users — directory: a directory of Slack users (people and bot accounts), with Name, Title, and Department columns. Filter by Bot or Active status, search by name, or click View Full List.

Channels

Covers channel-level activity and health.

Top channels by activity: ranks channels by a selected metric (Messages by default; also Threads, Members, or Avg Response), showing Channel, Messages, Threads, Unique Authors, Members, and Avg Response (s). The table shows 10 channels by default; change that with the Top N dropdown, search for a specific channel, or click View Full List.
Public vs private message split: a weekly stacked bar chart comparing public and private channel message volume. This chart is always weekly, whatever date range is selected.
Channel creation vs archive: a sprawl indicator comparing new and archived channels. High creation paired with low archiving suggests you have more channels than you need. Shows “No data for this period” when there’s nothing to compare.
Channel health: response times for each channel, including channels flagged as (suppressed). Columns are Channel, Messages, Unique Authors, Threads, Avg Response (s), and P50 Response (s). Every current, unarchived channel is listed, including quiet ones with zeros. A public channel the Slack app has not been added to is shown as #name (App not invited). Its zeros mean G360 cannot read it, not that it is quiet.

A channel marked (suppressed) had fewer than 5 distinct contributors in a week and is held back from certain rollups. This is intentional, and stops the dashboard from being used to point at one identifiable person.

Departments

Rolls Slack activity up to the department level, based on department data recorded on user profiles. This tab only populates when people have filled in the Department field on their Slack profile and your workspace is on Enterprise Grid.

Departments — headcount and message volume: lists each department’s Headcount and total Messages. Shows “No departments recorded on user profiles” if department data hasn’t been filled in for your users yet, or if your workspace isn’t on Enterprise Grid.
Department engagement & burnout signals: compares each department’s WAU % (weekly active users as a share of headcount) and After-hours % against the burnout and low-engagement thresholds, alongside Messages, Active Users, and Headcount, with a Status:

Status	Meaning
AT RISK	The department’s average after-hours share is 30% or more.
LOW ENGAGEMENT	Not at risk, and average WAU % is below 50%.
HEALTHY	Neither of the above.

A department (or the (no department) group) with fewer than 5 distinct contributors in a week shows as (suppressed) for privacy reasons, as channels do.

Cost Savings

Translates inactive Slack seats into a cost figure, so you can see the financial impact of unused licenses. This tab follows the Project filter only, not the date range. The tab has two groups of cards. Slack — License Cost

Card	What it shows
Total Seats	The number of paid Slack seats: every non-bot member, except single-channel guests (Slack does not bill them). Multi-channel guests are counted.
Cost / Seat / Month	The monthly license cost per Slack seat, set under Settings → Tool Cost Settings.
Monthly Cost	Total Seats × Cost / Seat / Month.
Annual Cost	The monthly cost × 12.

Savings Opportunity

Card	What it shows
Inactive Seats	Paid seats whose user has been inactive for at least the number of days set for Slack under Settings → Inactive User Settings (30 days if nothing is set), or was never active.
Monthly Saving Potential	Inactive Seats × Cost / Seat / Month — what you’d save per month by reclaiming those seats.
Annual Saving Potential	The monthly figure × 12.

If no Slack price is set under Tool Cost Settings, the cost and saving cards show ”—”. Update the price there and this tab recalculates automatically.

How metrics are calculated

Metric	How it’s derived
Messages, active users, active channels	Daily counts based on top-level messages. Replies are not counted as messages, and a person who only replied is not counted as active that day.
Threads	Top-level messages that have at least one reply.
Thread response rate	Threads with at least one reply ÷ total threads in the range.
Cross-team threads	Threads where the person who started the thread and a replier are in different departments.
Human vs bot messages	Split using each account’s bot flag. The card-level actor selectors and the Total Messages split use it.
First-response time	The time from the start of a thread to its earliest reply.
SLA breach	A thread whose first response took longer than 5 minutes.
After-hours %	The share of a channel’s (or a person’s) messages sent outside 09:00–19:00 in each person’s own Slack time zone (the workspace’s when they have none).
Burnout flag	A channel is flagged when its average weekly after-hours share over the selected date range is 30% or more. The same threshold sets the AT RISK status on departments. The Top engineers list uses its own threshold of 25% per person.
Department health	Weekly per-department messages, active users, and WAU % measured against department headcount.
Inactive users and seats	Days since a user’s last activity, counted up to the last fully processed day, against the Slack threshold in Inactive User Settings (default 30 days).
Small-group suppression	Any channel or department week with fewer than 5 distinct contributors is flagged as suppressed.

After hours is read in each person’s own time zone, taken from their Slack profile. The workspace time zone is only the fallback for people with none set. G360 detects it automatically as the most common time zone among the workspace’s members.

What each Slack plan includes

The integration works on any Slack plan. What changes is how much Slack makes available.

Metric	Free / Pro / Business+	Enterprise Grid
Messages, threads, response times, channel health	✅	✅
Burnout and after-hours	✅	✅
Inactive users, collaborators, channel churn, cost savings	✅	✅
Departments tab and Cross-Team Threads	❌	✅

On a standard plan, the Departments tab and the Cross-Team Threads KPI stay empty by design. This is expected, not an error. Everything else still works.

​Dashboard controls

​Overview

​Workspace KPIs

​Activity & Engagement Trends

​Response Time

​Inactive Users

​Burnout & Risk

​Burnout Signals

​Open Exception Alerts

​People & Collaboration

​Channels

​Departments

​Cost Savings

​How metrics are calculated

​What each Slack plan includes

Dashboard controls

Overview

Workspace KPIs

Activity & Engagement Trends

Response Time

Inactive Users

Burnout & Risk

Burnout Signals

Open Exception Alerts

People & Collaboration

Channels

Departments

Cost Savings

How metrics are calculated

What each Slack plan includes