Turn a sales call transcript into an updated HubSpot deal, Linear tasks for commitments, and a recap email draft. Ambiguous deal matches are flagged for a person to check, and the email stays unsent for the representative's review.
中文简介正在准备中。当前显示英语简介。
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.
安装前可以查看交给 AI 代理的指令内容。
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.
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 |
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.
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 |
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.
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.
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.
</workflow> <guardrails> - **Never send.** The recap email is always a draft held in {{approval_channel}} for the rep to review, edit, and send. - **One call, one session.** Nothing carries over between calls; each is scoped entirely to its own transcript and deal. - **Flag instead of guess.** A call that doesn't confidently match exactly one HubSpot deal skips the CRM update and is held in {{approval_channel}} with the ambiguity noted, instead of updating the wrong deal or silently skipping the call. - **CRM writes are grounded in the transcript.** Stage advances, notes, and contacts only reflect what the call actually covered — never inferred beyond it. - **Scoped secrets.** Google Drive, HubSpot, and Linear credentials are injected by the connector at runtime, scoped to this agent's grant. - **No chat posts.** The HubSpot deal, Linear, and the held email draft are the only outputs — this skill does not post to Slack or any other channel. </guardrails> </skill>还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Review Slack access requests against Okta role and team information, then prepare narrowly scoped GitHub or AWS IAM permissions. Apply changes only after an eligible person's approval and record the grant, reasoning, approver, and timestamp.
中文简介正在准备中。当前显示英语简介。
Research companies and people before outreach or meetings. Combines business profiles, recent news, hiring signals, and key contacts into a sourced brief with talking points and suggested questions, adding relationship history when CRM data is connected.
中文简介正在准备中。当前显示英语简介。
Review daily Google Ads and Meta Ads results for budget pacing, declining performance, and unusual activity. Get prioritized findings with supporting numbers and concrete recommendations for a marketing team to assess and carry out.
中文简介正在准备中。当前显示英语简介。
Automate website tasks such as navigating pages, filling forms, clicking buttons, taking screenshots, and extracting data. The skill also supports web app testing, with specialized guides for Electron desktop apps, Slack, and cloud browsers.
中文简介正在准备中。当前显示英语简介。
Process emailed vendor invoices by extracting details, comparing them with purchase orders and invoice history, and recording duplicates, overcharges, or missing orders. Summarize results in Slack for human review; payment approval and execution remain with people.
中文简介正在准备中。当前显示英语简介。
Guide changes to Kortix billing code, admin controls, and pricing screens. Explain how plans, trials, enterprise contracts, and access exceptions should work, where pricing is defined, and which audited routes must handle account changes.
中文简介正在准备中。当前显示英语简介。