Overview
Go beyond simple message lookups. This agent analyzes your Slack data to answer complex questions like "Why is team communication slowing down?" or "Which channels have the most information overload?"
**Capabilities:**
- Analyze communication patterns and identify bottlenecks
- Surface channel engagement trends and information silos
- Compare message response times across teams and channels
- Identify notification fatigue and collaboration inefficiencies
- Synthesize insights from messages, channels, and user activity
[{"type": "user", "content": "Why are response times in our Slack channels 60% slower this month? Team communication seems to be breaking down."}, {"type": "thinking", "content": "Analyzing Slack communication patterns...", "thinkingSteps": ["Retrieving messages from last 30 days...", "Calculating average response times by channel...", "Identifying bottlenecks in communication flow...", "Comparing to historical benchmarks..."]}, {"type": "assistant", "content": "I analyzed your Slack communication data and found the root causes of the slowdown:\n\n<widget_chart name=\"Response Time Trend\">{\"type\":\"area\",\"title\":\"Average Response Time by Week\",\"data\":{\"labels\":[\"Week 1\",\"Week 2\",\"Week 3\",\"Week 4\"],\"datasets\":[{\"label\":\"#engineering\",\"data\":[2.1,2.8,3.5,4.2],\"backgroundColor\":\"rgba(239,68,68,0.2)\",\"borderColor\":\"#ef4444\"},{\"label\":\"#product\",\"data\":[1.9,2.4,3.1,3.8],\"backgroundColor\":\"rgba(59,130,246,0.2)\",\"borderColor\":\"#3b82f6\"},{\"label\":\"#support\",\"data\":[1.2,1.6,2.0,2.5],\"backgroundColor\":\"rgba(16,185,129,0.2)\",\"borderColor\":\"#10b981\"}]},\"trend\":{\"value\":60,\"label\":\"increase vs last month\"}}</widget_chart>\n\n## Root Causes\n\n**Primary Bottleneck:** **Channel overload** - #engineering has 450+ messages/day (vs. 280/day last month). Average user receives 180 notifications/day, causing notification fatigue. 58% of messages go unanswered for >4 hours.\n\n**Secondary Issue:** **Information silos** - 34% of questions are asked in wrong channels, causing delays. Average time to redirect: 2.3 hours. Users report 'can't find the right channel' as top frustration.\n\n**Pattern Identified:** **@mentions** response time increased from 1.2 hours to 3.8 hours. Users are overwhelmed - average user is in 28 channels (vs. 18-channel recommended max).\n\n**Engagement Drop:** Active participation dropped 32%. 45% of team members have muted 5+ channels due to noise.\n\n**Recommendation:**\n1. Consolidate channels - merge 8 low-activity channels, reduce channel count by 25%\n2. Implement channel guidelines - clarify purpose and usage for each channel\n3. Use threads more - reduce channel noise, improve signal-to-noise ratio\n\n<ENTITY_ANNOTATION id=\"CHANNEL-engineering\" title=\"#engineering\" integrationType=\"SLACK\" />\n\n<CTA label=\"View Channel Analytics\" action=\"Show detailed channel engagement metrics\" />\n<CTA label=\"Generate Optimization Plan\" action=\"Create a communication efficiency improvement plan\" />"}]
