Step 1 — Find and read the transcript
The call recorder drops the transcript into the connected Google Drive folder
({{transcript_folder}}) once a call finishes. Open the new file via
google_drive and read its full content — every question raised, every
answer given, every commitment either side made. This is the entire input for
the session; no other call's context loads in.
Step 2 — Match the call to its HubSpot deal
Identify the deal from the call's attendees (contact email domain, company
name).
| Signal |
Routing |
| Exactly one deal matches confidently |
Pull its current stage, notes, and contact list before writing anything, so Step 4's update is a diff against reality, not a guess |
| No deal matches, or more than one plausibly matches |
Do not guess — skip Step 4 and flag the call instead when you hold it for approval (Step 7), so a human links it to the right deal manually |
Step 3 — Load the account's history and the recap playbook from memory
Read the shape of a good recap, how the team phrases next steps, which kinds
of objections need a considered answer, and this account's own history (past
calls, open threads) from memory. A recap that revisits an earlier commitment
should reference it, not restate it as new.
Step 4 — Update the HubSpot deal
Skip this step entirely if Step 2 didn't produce a confident deal match — go
straight to Step 5, and let Step 7 carry the flag instead. Otherwise write
back what the call actually covered:
| Field |
Update |
| Stage |
Advance only if the call clearly moved the deal (verbal commit, next step scheduled) — otherwise leave it |
| Notes |
Append a summary of the call: what was discussed, decided, and asked |
| Contacts |
Add any new attendee who isn't already on the deal |
Step 5 — File the follow-up tasks
Create one Linear task per commitment in {{linear_team}}: title is the
commitment phrased as a task, description is the context plus a link back to
the call, due date from anything the call implied ("by Friday"), assignee is
the rep who hosted the call (the owner/host field on the transcript file or
recording). If that isn't resolvable, file the task unassigned with a note
instead of guessing.
Step 6 — Draft the recap email
Write the recap to the account's history and the team's playbook: a short
summary of the call, a direct answer to every open question that came up, and
the next steps restated plainly. Ground it in what was actually said — never
a generic template with the account name swapped in.
Step 7 — Hold for approval
Place the drafted recap in {{approval_channel}} as a draft only. Do not send
it. If Step 2 found no confident deal match, put a flag at the top of the
held item instead of a deal reference: which call, why no deal matched (no
match / multiple plausible matches), and a link to the transcript, so a human
can link it to the right deal manually — the deal update stays pending until
that link exists. Otherwise, the deal update and the filed tasks are already
live by this point — only the outbound email waits on the rep.
1---2name: call-recap3description: The per-call runbook for turning a finished sales call's transcript — found in the connected Google Drive folder — into an updated HubSpot deal (or a flagged handoff when no deal matches), filed follow-up tasks in {{linear_team}}, and a drafted recap email — held for the rep's approval before it sends.4---56<skill name="call-recap">78<overview>9Turn one finished sales call into three artifacts: an updated HubSpot deal, a10handful of Linear tasks — one per commitment made on the call — and a drafted11recap email ready for the rep. The scheduled check spawns a fresh session per12new transcript file it finds in the connected Google Drive folder, seeded with13that one call — this skill is what turns the raw transcript into the14account's next CRM state, its follow-up tasks, and a recap the rep can send15with a read, not a rewrite.16</overview>1718<when-to-load>19- The scheduled check finds a new transcript in the connected Google Drive20 folder since the last run.21- A human asks the agent to write up or redraft the recap for a specific past22 call.23</when-to-load>2425<workflow>2627## Step 1 — Find and read the transcript2829The call recorder drops the transcript into the connected Google Drive folder30({{transcript_folder}}) once a call finishes. Open the new file via31`google_drive` and read its full content — every question raised, every32answer given, every commitment either side made. This is the entire input for33the session; no other call's context loads in.3435## Step 2 — Match the call to its HubSpot deal3637Identify the deal from the call's attendees (contact email domain, company38name).3940| Signal | Routing |41|---|---|42| Exactly one deal matches confidently | Pull its current stage, notes, and contact list before writing anything, so Step 4's update is a diff against reality, not a guess |43| No deal matches, or more than one plausibly matches | Do not guess — skip Step 4 and flag the call instead when you hold it for approval (Step 7), so a human links it to the right deal manually |4445## Step 3 — Load the account's history and the recap playbook from memory4647Read the shape of a good recap, how the team phrases next steps, which kinds48of objections need a considered answer, and this account's own history (past49calls, open threads) from memory. A recap that revisits an earlier commitment50should reference it, not restate it as new.5152## Step 4 — Update the HubSpot deal5354Skip this step entirely if Step 2 didn't produce a confident deal match — go55straight to Step 5, and let Step 7 carry the flag instead. Otherwise write56back what the call actually covered:5758| Field | Update |59|---|---|60| Stage | Advance only if the call clearly moved the deal (verbal commit, next step scheduled) — otherwise leave it |61| Notes | Append a summary of the call: what was discussed, decided, and asked |62| Contacts | Add any new attendee who isn't already on the deal |6364## Step 5 — File the follow-up tasks6566Create one Linear task per commitment in {{linear_team}}: title is the67commitment phrased as a task, description is the context plus a link back to68the call, due date from anything the call implied ("by Friday"), assignee is69the rep who hosted the call (the owner/host field on the transcript file or70recording). If that isn't resolvable, file the task unassigned with a note71instead of guessing.7273## Step 6 — Draft the recap email7475Write the recap to the account's history and the team's playbook: a short76summary of the call, a direct answer to every open question that came up, and77the next steps restated plainly. Ground it in what was actually said — never78a generic template with the account name swapped in.7980## Step 7 — Hold for approval8182Place the drafted recap in {{approval_channel}} as a draft only. Do not send83it. If Step 2 found no confident deal match, put a flag at the top of the84held item instead of a deal reference: which call, why no deal matched (no85match / multiple plausible matches), and a link to the transcript, so a human86can link it to the right deal manually — the deal update stays pending until87that link exists. Otherwise, the deal update and the filed tasks are already88live by this point — only the outbound email waits on the rep.8990</workflow>9192<guardrails>93- **Never send.** The recap email is always a draft held in94 {{approval_channel}} for the rep to review, edit, and send.95- **One call, one session.** Nothing carries over between calls; each is96 scoped entirely to its own transcript and deal.97- **Flag instead of guess.** A call that doesn't confidently match exactly one98 HubSpot deal skips the CRM update and is held in {{approval_channel}} with99 the ambiguity noted, instead of updating the wrong deal or silently skipping100 the call.101- **CRM writes are grounded in the transcript.** Stage advances, notes, and102 contacts only reflect what the call actually covered — never inferred103 beyond it.104- **Scoped secrets.** Google Drive, HubSpot, and Linear credentials are105 injected by the connector at runtime, scoped to this agent's grant.106- **No chat posts.** The HubSpot deal, Linear, and the held email draft are107 the only outputs — this skill does not post to Slack or any other channel.108</guardrails>109110</skill>
kortix-ai