Meeting and Communication Agents: Summaries, Follow-Ups, and Drafts
Meeting and communication agents turn transcripts, threads, and calendars into structured summaries, action items, and draft messages.
//
Search across all documentation pages
Meeting and communication agents turn transcripts, threads, and calendars into structured summaries, action items, and draft messages.
They save hours of note-taking when grounded in the source text and gated before send.
Use this cheatsheet to scope a v1 that people trust.
| Job | Input | Output | Autonomy default |
|---|---|---|---|
| Recap | Transcript / recording notes | Agenda-aligned summary | Auto OK for internal |
| Action extract | Transcript + attendees | Owner, task, due date, quote/timestamp | Auto draft; human assigns |
| Decision log | Transcript | Decision, context, dissent | Auto draft |
| Follow-up email | Recap + actions | Outbound draft | Human send |
| Thread triage | Email/chat thread | Priority, suggested reply | Human send |
| CRM note | Call transcript | Structured fields | Human approve write |
| Standup digest | Multiple updates | Team brief | Auto internal channel |
| Customer call coach | Sales call | Tips + risk flags | Private to rep/manager |
If you only ship one job first, ship action extract + recap before any auto-send.
| Artifact | Must include | Nice to have |
|---|---|---|
| Meeting summary | Purpose, attendees, key points, decisions, open questions | Links to docs mentioned |
| Action item | Verb + object, owner, due date or "TBD", source timestamp/quote | Priority, dependency |
| Decision | Statement, who decided, date, alternatives considered | Revisit date |
| Follow-up draft | To/cc suggestion, subject, body, linked actions | Tone preset |
| CRM update | Account id, fields changed, evidence quotes | Next step date |
| Risk flag | Claim + transcript span | Severity score |
Reject outputs that list actions without owners or quotes that cannot be found in the transcript window you stored.
| Criterion | 5 looks like | 1 looks like |
|---|---|---|
| Faithfulness | Every bullet traceable to transcript | Invented attendees or decisions |
| Actionability | Clear owners and next verbs | "Follow up on stuff" |
| Compression | 10-20% length, keeps decisions | Either transcript dump or empty |
| Attribution | Correct speakers on quotes | Swapped speakers |
| Tone fit | Draft matches audience | Casual slang to enterprise customer |
| Completeness | Open questions listed | Silent on unresolved conflicts |
Run the rubric on a golden set of 10 meetings before wide rollout.
| Tool | Use | Gate |
|---|---|---|
get_transcript | Source of truth | ACL by meeting id |
get_calendar_meta | Attendees, title, time | Read-only |
search_prior_notes | Continuity across series | Same ACL family |
draft_email / draft_chat | Create draft only | No send scope |
send_email | Outbound | Explicit human click / approval token |
update_crm | Field writes | Diff + approve |
create_tasks | Tickets/todos | Project allowlist |
Prefer two tools (draft_* and send_*) over one "communicate" supertool that hides side effects.
Skipping stage 4 is how confident fiction enters CRM systems.
| Failure | Symptom | Mitigation |
|---|---|---|
| Hallucinated decisions | "We chose vendor B" never said | Require quote spans; refuse if missing |
| Owner vacuum | Actions with no names | Default owner = speaker or "UNASSIGNED" |
| Infinite politeness | Drafts too vague to act on | Template with explicit ask + date |
| Context bleed | Prior meeting mixed into recap | Scope retrieval to meeting id first |
| Over-notification | Every recap pings a huge channel | Audience rules by meeting type |
| Diarization mess | Wrong speaker on commitments | Surface confidence; allow rename UI |
A single-shot summary can be a pipeline. It becomes agentic when it chooses tools (CRM lookup, prior notes, task systems) across turns based on content.
Default to one screen plus an action table. Offer "detailed" as a second artifact, not the default email body.
Live bots add consent and product complexity. Many teams start with post-meeting transcript processing only.
Detect language, summarize in the meeting language by default, and only translate as an explicit second step with review.
Preserve domain terms; do not "simplify" away API names or metric definitions. Link to internal docs when mentioned.
Yes after precision is high on action extraction. Start with draft tickets in a staging project.
Work agents center on shared meetings, CRM, and team ACL. Personal agents center on one user's inbox preferences and devices.
Long transcripts often need larger context windows or chunk-then-merge strategies. Verify limits at build; map-reduce summaries carefully to keep actions.
Score: correct recipients, correct commitments, no new promises, tone, and presence of scheduling ask when needed.
Return a failure artifact, not a creative story. "Insufficient transcript" is a valid product outcome.
Only if spoken or present in calendar. Otherwise mark due: TBD and ask the owner.
Strict ACL mirroring calendar permissions, optional meeting-type classifiers, and admin denylists for sensitive series.
Stack versions: Pins from the category manifest (verify at build): OpenRouter (~315+ models, July 2026 pricing/fees); LangGraph 1.0+; CrewAI 1.14+; Microsoft Agent Framework 1.0; Vercel AI SDK 6; Pydantic AI (latest); LlamaIndex (latest); OpenAI Agents SDK (latest + MCP); MCP (Linux Foundation governance); A2A (HTTP+SSE+JSON-RPC 2.0); Solana
@solana/web3.js+@solana/spl-token.
Reviewed by Chris St. John·Last updated Jul 16, 2026