Community Pulse (demo)

THIS WEEK'S FOCUS

Channel activity spike is distorting community signal.

#bugs is running 3.2× above baseline — a small share of members is driving most of the volume.
Patch discussion is healthy, but bug noise may be crowding out feedback you need for the next ship.

Priority: Acknowledge the discussion in #bugs, then route triage to a pinned thread so other channels stay readable.

NEEDS ATTENTION· 2 ITEMS

Concentration above normal

Top 5 members sent 41% of messages in #bugs (7d)

High

Clear pattern: A handful of accounts are posting a disproportionate share of messages in the bug channel.

Impact: Skews velocity metrics and can look like a brigade even when reports are legitimate.

Do this: Review top contributors and thread split — consider a dedicated triage channel.

Past spike: #bugs elevated

38% of all messages · 3.2× baseline

Medium

Possible pattern: #bugs is 3.2× busier than usual — spike began shortly after Patch 2.4.1 shipped.

Impact: Spike in bug channel drowns out quieter channels and skews how patch health reads in reports.

Do this: Scan last 48h — pin a response if one topic is driving the spike.

Active today

847

▲ 12 vs yesterday

Patch signal

Mixed

Patch 2.4.1 · 38d ago

7d activity

+55%

74 msgs/day vs 30d avg

Net members

+23

78% activated

CHANNEL ACTIVITY · 7dRanked by volume

Anomalies

Activity Trend

7d · vs 30d average

74 msgs/day

+55%

7d vs 30d avg

74 msgs/day this week48 msgs/day 30d avg

Member Flow

Joins, leaves, activation

+23

net members

78%

activated in first 7 days

14%

joined and never spoke

41 joined in this period

Voice Activity

Sessions

4.2

voice sessions/day

Community plays together most on Saturday around 8PM

Community Pulse

Same layout as the real dashboard