Slack Team Pulse Digest
A Slack digest people will actually read.
Reduces manager catch-up time by summarizing the important work signals hidden across channels and threads.
Reviews selected Slack channels and produces a digest that separates signal from noise for managers, operators, and distributed teams.
How it runs
Multi-agent orchestration — here's the flow, step by step.
Call verslay_recall to retrieve prior team pulse baselines, known recurring issues, and team sentiment history from memory. Pull message history from configured Slack channels via the slack connection using slack_get_channel_history for the past 24-48 hours — extract: message volume by channel, active contributors, escalated threads (by reaction emoji count or reply depth), and any messages containing blockers, risks, or help requests. Produce a raw Slack activity digest.
slack channel operations agentConsume Phase 1 raw Slack digest. Perform deep message classification across all channels: tag each message thread as decision, blocker, celebration, question, status update, or noise. Flag any cross-channel mentions of the same issue (indicating systemic problems). Identify the 5 most significant threads by engagement + content importance. Produce a classified message thread index.
messaging scannerIn parallel with messaging-scanner, call verslay_news_search and verslay_web_search on any external topics or vendors mentioned in the flagged Slack threads — for example, if a team member mentions an outage with a third-party tool, search for related service status news. Call verslay_web_search for context on any industry events or deadlines mentioned in Slack conversations. Produce an external context enrichment brief.
web researcherConsume Phase 2 classified message thread index. Score team sentiment across channels: positive energy (celebrations, progress updates, thanks), neutral operational (status updates, questions), and negative stress signals (blockers, conflict, urgency overload, repeated complaints). Produce a channel-by-channel sentiment heatmap and identify the top 2 mood risks and top 2 positive momentum signals. Pass to Phase 4.
sentiment analystConsume Phase 3 sentiment heatmap, Phase 2 thread index, and Phase 2 external context. Cross-tabulate message volume, sentiment, and thread importance by channel and team member contribution. Identify patterns: is one channel persistently negative? Is one person carrying disproportionate load? Call verslay_chart_create to produce a team pulse dashboard chart with channel sentiment and activity volume side by side.
data analystConsume Phase 4 team pulse dashboard, Phase 3 sentiment signals, and Phase 2 classified thread index. Write the executive team pulse digest: channel-by-channel sentiment scorecard, top 5 significant threads summary, blockers requiring leader attention (with suggested responses), positive team wins to amplify, mood risk flags, and recommended 1-2 manager actions for the day. Call verslay_memorize to store the team pulse baselines, mood trends, and blocker patterns in memory.
executive briefing writerReceive the team pulse digest from executive-briefing-writer. Post it to the configured Slack channel (typically a manager or leadership channel) or deliver via email as specified by the user. Confirm delivery and log send timestamp.
distributorRequired Agents
7- slack-channel-operations-agent
- messaging-scanner
- web-researcher
- sentiment-analyst
- data-analyst
- executive-briefing-writer
- distributor
Connections
Required
What it does
- Multi-channel scan
- Decision extraction
- Blocker summary
- Follow-up list
- Leadership digest
Example prompt
Summarize our main Slack channels for today. Pull out wins, blockers, decisions, owner follow-ups, and anything leadership should know.
Ready to deploy Slack Team Pulse Digest?
Start free. One click, full agent orchestration.
Get Started Free →