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.
/call-recap-formatA 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-questionsA 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-rulesAutomatic call scoring is only fair if the rubric is visible: score the observable things — whether a next step was agreed, whether questions were about the past — and leave judgement to a human.
/discovery-questionsAfter-call work is the twenty minutes nobody books: the CRM update, the recap, the follow-up, the task for the thing you promised — and it is the first work to disappear on a busy day.
/call-recap-formatAn automated standup is only read if it is short and specific: what moved, what is blocked, and what nobody has touched — with the last category being the one that justifies posting at all.
/call-recap-formatA useful Zoom summary is not a compression of the transcript: it is the commitments, the decisions and the unresolved risks, written for someone who was not on the call.
/call-recap-formatPre-meeting research has a five-minute budget, so it should return exactly three things: what changed recently, who you are talking to, and the one thing that would embarrass you not to know.
/our-icpOnboarding fails on dependencies rather than on effort, so the skill worth writing is the one that names what you need from the customer, by when, and what happens to the date if it does not arrive.
/call-recap-formatGood discovery asks about what happened rather than what the buyer wants, because people are reliable historians of their own problems and unreliable architects of their own solutions.
/discovery-questionsIt defines the shape of the work rather than doing it. A recap skill says a recap must carry commitments with owners and dates, name unresolved risks, and stay under 200 words — then any agent producing a recap follows that.
For anything that reads a transcript, yes — Zealos works with Zoom, Avoma, Fathom and Gong. Prep skills only need your calendar and CRM.
Because you want one recap standard and several agents that meet it. Five agents times forty skills is a much larger surface than forty more agents.