Summarize calls and update the CRM
Post call automation is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
Post call automation is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.
| name | call-recap-format |
|---|---|
| description | The structure of a good call recap: commitments, owners, dates, risks. Use when summarising a recorded call or meeting, or writing a follow-up that has to survive being forwarded. |
| allowed-tools | none — this skill adds judgement, not reach |
| compatibility | Zealos, Claude Code, Cursor, Codex and any client that reads SKILL.md |
| license | Free to use and edit |
--- name: call-recap-format description: The structure of a good call recap: commitments, owners, dates, risks. Use when summarising a recorded call or meeting, or writing a follow-up that has to survive being forwarded. --- # Call recap format A recap is read by someone who was not on the call. Write for them. ## Structure **One line up top:** what was decided, or that nothing was. **Commitments** — the only section that always matters. Each line: *who* · *what* · *by when*. Both sides. If a date was not said, write "no date agreed" rather than inventing one. **What we learned** — new facts only. Not a transcript. Three bullets is plenty. **Risks and open questions** — what could kill this, and what we still do not know. If a concern was raised and not resolved, it goes here even if the tone was friendly. **Next step** — one action, one owner, one date. ## Rules - Quote the customer where the exact words matter (pricing, scope, timing). - Separate what they said from what you concluded. Mark inferences as inferences. - Do not soften bad news. A recap that reads better than the call did is worse than useless. - If the call had no commitments, say that. It is the most important thing on the page. ## Length Under 200 words. If it is longer, the call did not have that much in it and you are padding.
Six calls back to back means the fourth one gets a two-line note at 7pm. The recap is written before you leave the meeting, so the deal review two weeks later has the actual words the buyer used rather than your memory of them.
You stop reading recaps to find out what happened and start reading them to find out what was promised. Deals with no agreed next step surface as a list rather than a hunch.
You are the one taking the calls and there is nobody to hand the notes to. The recap becomes the handoff document for the first rep you hire, six months before you hire them.
Software that takes what happened on a call and produces the recap, the CRM updates and the follow-up without a human retyping any of it. The skill is the part that defines what good looks like; the agent does the work.
Zoom, Avoma, Fathom and Gong all sync transcripts into Zealos. The skill reads whatever transcript is there, so switching recorder does not mean rewriting the method.
Not if you pair it with a field-conventions skill. The rule that matters is that budget, timeline and decision maker are left blank unless the customer stated them.
A pre-call brief is worth writing only if it changes what you ask: who is in the room, what they are measured on, what happened last time, and the one question you cannot afford to leave without answering.
/discovery-questionsAn AI SDR agent is only as good as the definition of a good customer it is working from, which is why the fit criteria belong in a written skill rather than buried in a prompt nobody can find.
/our-icpAI email triage is worth having only when it sorts by consequence rather than by recency: what blocks a deal, what someone is waiting on you for, and what can be read at the end of the week.
/email-rulesCRM data hygiene survives AI only if one rule is written down first: a field left blank is a known unknown, while a field filled in by inference is an unknown unknown that will be reported on as fact.
/crm-field-conventionsQualification is a claim about evidence, not a score: a deal is qualified when every criterion has a source you can quote, and unevidenced criteria are named rather than filled in optimistically.
/meddiccA follow-up gets a reply when it opens with the specific commitment made on the call, stays under 120 words, and asks for exactly one thing the recipient can answer in a sentence.
/email-rules