Call Recap
Turn a recent call into a compact recap with a summary, decisions made, action items with owners, and open questions, drawn from what was actually said.
Overview
Call Recap turns a just-finished call into a compact, high-signal writeup: what was discussed, what was decided, who owns what, and what is still open. It reads the conversation with conversation intelligence and adds light account research only when deal context helps. The output is a recap you can drop into notes or a follow-up email without editing for accuracy.
The skill is built for anyone who runs customer calls and needs the record fast: account executives, customer success managers, and the managers who review their deals. You can name the call by account or date, or let the skill list your recent meetings as a numbered shortlist to pick from before it spends any credits. An optional emphasis, such as just the action items, what did we decide, or a version for your manager, shapes what the recap leads with.
The recap stays honest to the conversation. It attributes decisions and action items only when the call supports them and never invents an owner or a due date, marking those as owner not stated or no date given. Conversation intelligence cannot search by topic or count mentions, so the skill keeps each read scoped to one engagement and runs a separate read per call when several are selected. When a call has no transcript, it reports that the recording was not available rather than fabricating a recap.
What It Does
- Compact summary: Captures in a few sentences what the call was about and where it landed.
- Decisions: Lists what was decided and attributes each to the person who made or agreed to it when the conversation says so.
- Action items: Records owners and due dates, and flags an item as owner not stated or no date given when the call did not specify.
- Open questions: Surfaces what is still hanging, each with the moment in the call that raised it.
- Adaptive output: Reshapes the recap around a requested subset, such as an action-items-only list or a manager-facing summary.
- Grounded attribution: Cites the source meeting and declines to assign an owner or date the conversation never stated.
Use Cases
Post-Call Writeup
An account executive wraps a call and wants the record before context fades. The skill reads the meeting and returns a summary, the decisions reached, action items with owners, and open questions, each citing the source moment. The AE pastes it into the CRM or a follow-up email in seconds rather than reconstructing the call from memory.
Action-Items-Only Follow-Up
A rep needs to send next steps right after a meeting and wants nothing but the commitments. With an action-items emphasis, the recap leads with owners, actions, and due dates, marking anything the call left unstated. The rest of the template is trimmed so the follow-up is ready to send.
Manager-Facing Summary
A manager wants a tight read on how a deal call went for a pipeline review. Asked for a manager-facing version, the skill keeps the recap to the summary, the decisions, and the suggested next step. The manager gets the signal without wading through the full transcript.
Skill Definition
The raw markdown Claude uses when this skill is invoked.
---
name: call-recap
description: Recap a recent call with a tight summary, the decisions made, action items, and open questions. Name the call (account and/or date) if you know it, or let the skill pull your most recent calls and offer a shortlist to pick from. Uses conversation_intelligence to read what was actually said, with light account_research for deal context. Use when someone says "recap my last call", "what came out of the Acme meeting", "summarize yesterday's call", or needs a post-call writeup. The output adapts to the request — for example decisions-only or action-items-only.
---
# Call Recap
Turn a just-finished call into a compact, high-signal recap: what was discussed, what was decided, who owns what, and what is still open.
## Prerequisites
`browse_engagements` (to find the call) requires an active calendar/email/meeting integration. `conversation_intelligence` (to read the call) requires at least one connected meeting or email source. Both `conversation_intelligence` and `account_research` consume AI credits. If no conversation data is available for the call, say so and point the user to their ZoomInfo admin rather than guessing at content.
## Input
Provided via `$ARGUMENTS`:
- **Which call** (optional) — an account and/or a date ("the Acme call", "yesterday's demo"). If omitted, the skill lists recent calls to pick from.
- **Emphasis** (optional) — e.g. "just the action items", "what did we decide", "for my manager". Shapes the output.
## Workflow
1. **Identify the call.**
- If the user named an account or date, resolve the account via `search_companies` first if needed (`browse_engagements` filters by company/contact ID and date, not by call name), then call `browse_engagements` (`engagementType: MEETINGS`, `sort: -chronological`) scoped to that ID and date window and confirm the match.
- If nothing was named, call `browse_engagements` for the user's recent meetings and present a numbered shortlist (date, title, account, participants). Let the user pick one (or several) before spending AI credits. Keep each chosen engagement's ID.
2. **Read the call with `conversation_intelligence`.** Scope CI to the chosen engagement ID and ask for a structured read: what was discussed, decisions made, action items with owners and any stated due dates, open questions, and notable customer statements. For multiple selected calls, run one CI call per engagement (do not ask one CI call to span several). Keep the query specific to that engagement; CI cannot search by topic or count mentions.
3. **Add light context (optional).** If deal/relationship framing helps, pull `account_research` for the account — kept brief. Skip it if the user just wants the recap itself; this is a recap, not a full account brief.
4. **Synthesize.** Write the recap from the CI output. Attribute decisions and action items only when the conversation supports them; never invent an owner or a due date that was not stated (mark those "owner not stated" / "no date given"). Cite the source meeting.
## Output Format
Default compact template (adapt to the user's emphasis):
**[Call title] — [date]**
*Participants: [names].*
**Summary** — 2-4 sentences on what the call was about and where it landed.
**Decisions**
- [Decision, with who made/agreed it if stated.]
**Action items**
- [Owner — action — due date or "no date given"]
**Open questions / unresolved**
- [What is still hanging, with the source moment.]
**Suggested next step** *(one line, only if the conversation points to one.)*
### Adapting the template
If the user asked for a subset ("just action items", "decisions for the QBR notes"), lead with that section and trim the rest. If they asked for a manager-facing version, keep it to summary + decisions + next step. Match the format to the request rather than always emitting every section.
### When there is no call or no data
If no recent calls are found, say so and ask the user to name the account or widen the date range. If a call is found but `conversation_intelligence` has no transcript for it (e.g. not recorded, or indexed within the last several hours), report that the recording was not available to analyze rather than fabricating a recap.
Created by
Rowan Bailey
Senior Director, Product
Provided by
ZoomInfo ↗Capabilities
- Compact summary of what the call was about and where it landed
- Decisions made, attributed to who made or agreed them when stated
- Action items with owners and due dates, marked when either is missing
- Open questions and unresolved threads with their source moments
- Output that adapts to a requested subset such as action items only
- Honest fallback when a call has no available transcript