Your AI Chief of Staff Agent turns meeting conversations into clear outcomes and lasting context. When subscribed to a meeting, the agent captures the discussion and produces a concise summary with key discussion points, decisions, risks, and recommended next steps.
Anyone invited to the meeting series can receive a meeting summary in their preferred agent communication channel - Microsoft Teams, Slack, or email. From the notification, you can open the full summary and capture follow-up actions too.
Beyond the summary, the meeting conversation becomes part of the agent's memory. You can later ask questions about past meetings, and the agent will use those discussions as context to help guide priorities, decisions, and focus areas.
How Meeting Summaries Work
Meeting summaries can be delivered to both the meeting organizer and meeting participants. Both follow similar setup steps; the differences between the two roles are summarized in the Quick Reference table at the end of this article.
Meeting Organizer: the person who owns and created the recurring meeting series in Outlook/Teams.
Meeting Participant: anyone invited to the Outlook meeting series as an attendee.
Important: To receive the same meeting summaries, the organizer and all participants must be on the same WorkBoard instance - the same tenant (US vs. EU) and the same WorkBoard Org ID.
Setting Up Meeting Summaries
Anyone who wants to receive a meeting summary - organizer or participant -completes the same steps below. However, if the meeting organizer adds their Chief of Staff agent to the meeting series, participants can get the summary even without adding their own Chief of Staff agent.
If the organizer does not subscribe their agent, each participant who wants a summary must subscribe their own Chief of Staff agent to the meeting series. One participant subscribing covers only that person, not the others. Enabling delivery (Step 2) is done per person, and admitting the Notetaker (Step 3) happens once in the live meeting. Even if multiple Chief of Staff agents are added to the meeting series, only one Notetaker will join the call.
Step 1: Subscribe Your Agent to the Meeting
Open Agent Settings
Navigate to Data Access
Select Add External Source
Choose Meetings
Select the recurring meeting(s) from your calendar
Only recurring meetings from your Outlook calendar with a MS Teams link can be subscribed at this time. When you connect a recurring meeting, all instances in that series are added - not just a single occurrence.
Step 2: Configure Your Summary Delivery
In your Agent Responsibility settings, confirm that Send Meeting Summaries/Follow-up is enabled.
Make sure your preferred Agent Notification preferences are set in Agent General Settings, so the summary can be delivered to Teams, Email, or Slack.
Step 3: Admit the WorkBoard AI Notetaker
When the meeting starts, the WorkBoard AI Notetaker will join the Teams call approximately 2 minutes before the scheduled start time. A participant must admit the notetaker to allow it to capture the meeting.
The notetaker waits to be admitted for up to 8 minutes.
If the notetaker is not admitted, no meeting summary will be generated and no summary will be sent to anyone.
Even if multiple users have invited their Chief of Staff to the meeting, only one WorkBoard AI Notetaker will appear in the call.
The notetaker can be removed at any time, the same way any attendee can be removed from a Teams call.
Post-Meeting Summaries
After the meeting ends, WorkBoard AI processes the meeting and generates insights. In most cases, summaries become available within about 10–20 minutes after the meeting ends.
When the summary is ready, all eligible users receive a notification in their chosen channel. Selecting Capture Next Steps opens the detailed meeting summary inside the WorkBoard agent, which includes:
Meeting Overview
Key Discussion Points
Decisions Made
Risks, Blockers, or Open Questions
Action Items / Next Steps
Turn Meeting Outcomes into Actions
From the Capture Next Steps section, you can create action items from the meeting summary. This allows teams to quickly convert meeting outcomes into trackable work assigned to accountable parties with due dates.
Pressing Capture Next Steps opens the meeting summary in your agent window. Scroll to the bottom of the page to see suggested action items and a link to create an action item for each recommendation.
Note: All participants receive the same meeting summary and the same suggested action items.
Asking Your Agent Questions About Meetings
Once a meeting summary is available, you can ask your WorkBoard agent questions such as:
What decisions were made in X meeting?
What follow-up actions came out of the discussion?
What risks were identified?
What should I prepare for the next meeting?
Tips for Better Results
Reference the meeting clearly - e.g., "in Product-Marketing Sync last Tuesday."
Ask for a specific output - e.g., "list decisions," "owners + due dates," or "risks only."
Add a timeframe when useful - e.g., "in the last 2 weeks" or "in the last 20 minutes of the meeting."
The agent uses meeting summaries as a contextual data source not only when you ask about specific meetings, but also when analyzing follow-ups, risks, and creating periodic reporting such as Daily Memos, 1:1 Prep and Progress Summaries, Risk Analysis, and more.
Quick Reference Summary
| Meeting Organizer | Meeting Participant |
Chief of Staff enabled | Yes | Yes |
Subscribe your CoS agent to a meeting series | Yes - required | Situational - not required if the organizer adds their Chief of Staff. Required if the organizer has not. |
Accept meeting invite | N/A (organizer) | No - invitation is enough |
Attend the meeting | Not required to receive the summary | Not required to receive the summary |
Send Meeting Summaries/Follow-ups setting enabled | Yes - must be enabled for the organizer to receive the summary | Yes - must be enabled for the participant to receive the summary, whether the organizer's or the participant's CoS agent is invited |
Admit AI Notetaker | Must be done by any participant | Must be done by any participant |
Same WorkBoard instance | Yes | Yes |






