Meetings

The meetings surface is Dispatch's view of your calendar and what happens around it. The agent maintains a record of each meeting (who attended, what was decided, what action items came out) and uses that record to prepare you for the next call and to draft follow-ups after.

The agent reads from your connected calendar (Google Calendar or Outlook Calendar) and stores per-meeting notes as files the agent and the user can both edit.

What it does

• Briefings. Before a meeting, the agent can pull together a brief: who you're meeting, recent email threads with them, any open todos involving them, what was discussed last time.
• Notes during and after. Notes land in the meetings surface under /meetings/ organized by date. You can pin items, jot rough notes, and have the agent enhance them after the call.
• Meeting notetaker. Dispatch can send a notetaker bot to join your video call (Zoom, Google Meet, Microsoft Teams, Webex, GoTo Meeting), record it, produce a transcript, and write a summary. The transcript lands at /meetings/YYYY-MM-DD/slug/transcript.yaml and the summary at summary.md. When a new meeting lands on your calendar, a default "Event Added" automation decides whether to attend: by default it joins any meeting with a video link, respecting any preferences you've set about which meetings to skip.
• Action items. The agent extracts action items from notes and can convert them into todos or into draft follow-up emails.
• Follow-ups. Asked to draft a follow-up, the agent uses the notes plus the participant list to compose a thank-you, a recap, or a next-step email.
• Calendar awareness. The agent knows your free/busy and can answer questions like "when did I last meet with this person?"

How to use it

The most common pattern is to ask for prep before the call and a recap after.

• "Brief me on my 2pm with the Acme team."
• "Pull the last three threads I had with this person before the call."
• "Draft a follow-up for the meeting I just had with the design team."
• "Have Dispatch take notes on my 2pm with Acme."

Which meetings get a notetaker is governed by the "Event Added" automation that runs whenever a new meeting appears on your calendar. To change the rule, ask the agent to update it, for example "Only attend external meetings" or "Stop attending my 1:1s." The agent edits the automation's instructions (stored at /automations/triggers/), and the new rule applies to meetings going forward.

See the morning briefing recipe for a daily summary that includes your upcoming meetings.

What Dispatch can do here

• Morning briefing: a scheduled daily summary that surfaces the day's meetings, times, and attendees.

Limits and behavior

• Calendar provider scopes. The agent only sees events on calendars you have authorized through Google Calendar or Outlook Calendar.
• Notetaker bot. The bot is visible in the call and announces itself in the meeting chat ("Dispatch is taking notes for this meeting."). It needs a video link on the calendar event, and only upcoming meetings can be attended. It leaves on its own after 20 minutes of meeting time followed by 5 minutes of silence. Notetaking is enabled by default for the organization and can be turned off in workspace settings. When it is on, the "Event Added" automation attends any new meeting with a video link by default; edit that automation (see How to use it) to narrow which meetings it joins.
• Transcripts without the bot. When the notetaker did not attend, the agent works from the calendar event, your notes, and any transcript you provide (for example pasted into a meeting note).
• Cross-org separation. Meetings, like all memory, are per-organization. Meetings in your work account stay separate from a side-board calendar in another org.

Related

• Google Calendar connection details
• Outlook Calendar connection details
• People: the directory the agent uses for participant context.
• Cookbook: Morning briefing

For agents

• The meetings surface reads from Google Calendar and Outlook Calendar via their connectors.
• Per-meeting notes are stored as files under /meetings/ organized by date.
• The agent extracts action items from notes and can convert them into todos or follow-up email drafts.
• Free/busy queries and event reads are read-only; creating or modifying an event is annotated external-write and gated.
• A notetaker bot attends a meeting when attend: true is set in its details.yaml. The default "Event Added" trigger automation sets this for any new meeting with a meetingUrl, respecting user preferences about which meetings to skip; users retune attendance by editing that automation under /automations/triggers/. The bot records, transcribes, and summarizes the call.
• Notetaker output lands at /meetings/YYYY-MM-DD/slug/transcript.yaml (read-only) and summary.md, with a speaker map at speakers.yaml.
• Notetaking is gated by the org-level notetakerEnabled toggle (default on). Supported platforms: Zoom, Google Meet, Microsoft Teams, Webex, GoTo Meeting. The bot is visible in the call and auto-leaves after 20 minutes plus 5 minutes of silence.