Onboard a new customer
Customer onboarding automation is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
Customer onboarding automation is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
Onboarding 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.
| 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.
Kickoff produces a plan with named dependencies instead of a cheerful timeline that quietly assumes everything arrives on time.
The access you need is requested in week one rather than discovered as a blocker in week four.
The handover carries what was promised in the sales process, so the CSM is not renegotiating expectations on day one.
Almost always a dependency on the customer's side that was never named with an owner and a date. That is the section most onboarding templates omit.
Yes, and that is the point of naming dependencies — a shared plan makes the dependency theirs rather than a private worry of yours.
An agent can watch the checkpoints and flag slippage. The skill defines what a checkpoint must demonstrate.
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-questionsAccount research earns its time only when it changes the first sentence you write, which means looking for what recently changed rather than assembling a profile anyone could have found.
/our-icpA 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-questionsAn account plan is worth the hour only if it names the one unknown that would most change your approach — everything else in a plan template is decoration you will never re-read.
/our-icp