Team Pulse Agent

The Team Pulse Agent blueprint demonstrates a pattern that many remote and hybrid teams desperately need: asynchronous stand-ups powered by a persistent AI agent. Instead of pulling everyone into a synchronous meeting or relying on people to remember to post in a channel, the agent reaches out to each team member individually, collects structured updates, and produces a digest that the entire team can read on their own schedule.

The Problem

Daily stand-ups are one of the most common rituals in modern teams, but they scale poorly. In a 10-person team, a synchronous stand-up consumes 10 person-hours per week. Distributed teams across time zones struggle even harder - someone is always joining at an inconvenient hour. Async stand-up bots exist, but most are rigid form-fillers that produce mechanical lists nobody reads.

This agent is different. It has a conversational approach - it DMs each team member, asks follow-up questions when something sounds blocked or unclear, and produces a narrative summary that highlights what actually matters: blockers that need attention, progress on key deliverables, and patterns across the team.

How It Works

The agent operates in two distinct phases:

• Collection phase (morning or configurable time) - The agent reads the team roster file to know who to contact, then sends a friendly DM to each team member on Slack asking for their update. It asks about what they accomplished, what they are working on today, and any blockers or issues. It can follow up conversationally if answers are vague or if a blocker sounds urgent.

• Summary phase (end of collection window or on demand) - The agent reads all the collected updates from the daily log, identifies common themes, flags blockers and cross-team dependencies, and posts a structured summary to a designated Slack channel. The summary is not just a list - it highlights patterns, calls out items that need attention, and tracks progress against previously reported blockers.

Persistent Report Space

The agent stores all data in a dedicated Space - a persistent file system that it can read from, write to, list, and search at any time:

• team-roster.md - List of team members with roles, focus areas, and Slack user IDs. The agent reads this to know who to contact daily.
• daily-updates.md - Rolling log of individual daily updates with timestamps. Each entry captures what was done, what is planned, and any blockers.
• weekly-summary.md - End-of-week compiled summaries showing weekly progress, resolved blockers, and emerging trends.
• issues-tracker.md - Persistent tracker of ongoing issues, blockers, and their resolution status across multiple days.

Unlike static file resources, the Space acts as a full storage file system. The agent can create new files as needed - per-person update logs, monthly archives, project-specific trackers - without being limited to a fixed set of file resources. It can also search across all files to find relevant context quickly.

Team vs. Company Scope

The blueprint works at any scale. For a single team, configure the roster with your team members and point the summary channel at your team channel. For company-wide deployment, expand the roster to include everyone and use a company-wide channel. You can also deploy multiple instances of this blueprint - one per team plus one that aggregates across teams for leadership visibility.

Why This Pattern Matters

The value is not just automation - it is intelligence. A simple form bot collects answers. This agent:

• Detects stale blockers and escalates them over time
• Identifies cross-team dependencies from individual reports
• Produces summaries that highlight what changed, not just what was said
• Adapts its follow-up questions based on context
• Maintains institutional memory across days and weeks

Market Context

Async stand-up tools like Geekbot, Standuply, and Range are popular but limited to structured forms with static questions. The AI-powered approach here goes further - conversational collection, intelligent summarisation, and persistent context. Teams using Slack already spend billions on productivity tools; this blueprint turns ChatBotKit into an intelligent team coordination layer.

Getting Started

1. Deploy the blueprint and configure the Slack integration with your workspace bot token and signing secret.
2. Edit the team-roster.md file in the Team Pulse Workspace space with your team members, their Slack user IDs, roles, and focus areas.
3. Two scheduled triggers are pre-configured: 9 AM daily for update collection and 4 PM daily for summary broadcast. Adjust the cron schedules and trigger prompts to fit your team's cadence.
4. Browse the workspace space to see accumulated reports, update logs, and issue tracking build over time.

Backstory

Common information about the bot's experience, skills and personality. For more information, see the Backstory documentation.