Skip to content

Sales → CS Handover

A one-page handover for every closed deal: stakeholders, commitments, success criteria and risks, pulled from every sales call in the cycle.

On demandClaap · Notion (optional) · HubSpot/Salesforce (optional)

Works inClaudeChatGPTGrok

Install it once in your AI, then it runs on your Claap calls.

At a glance

Updated

What it does
Sales → CS Handover builds a one-page handover for a closed deal from its calls, its AI summary and its emails in Claap, and cites the source of each point.
What you get
Each handover is one page: company snapshot, stakeholder map, deal timeline, what was sold, customer context and an onboarding plan, with risks and open items flagged.
What it needs
It needs a Claap workspace with sales calls recorded and linked to deals synced from your CRM, and Claude, ChatGPT or Grok connected to Claap. Notion and a CRM connection are optional: without Notion, the handover shows in the chat.
Runs in
Claude, ChatGPT, Grok · On demand
Cost
The Claap MCP is included on every Claap plan, the free one too. Writing AI fields into Claap, to sync the handover to HubSpot, uses AI credits, which start on the Pro plan.

The Sales → CS Handover is a Claap agent that produces a one-page handover for every closed deal, covering stakeholders, commitments, success criteria and risks, from every sales call in the cycle.

💡 What problem does Sales → CS Handover solve?

When a deal closes, CS inherits a customer they know almost nothing about. The handover is usually a rushed Slack message or a 30-minute internal call where the AE tries to recall weeks of conversations. Without structured handover:

  • Critical context gets lost: what was promised, which pain points drove the deal, what the champion actually cares about.
  • CS starts from scratch, the customer repeats themselves, and time-to-value suffers.
  • Technical commitments are missed: integrations, timeline promises, security requirements.
  • Risk signals stay invisible: objections that were handled but not fully resolved, hesitant stakeholders.

This results in slower onboarding, broken promises, and churn risk in the first 90 days.

⚙️ What does Sales → CS Handover do?

Sales → CS Handover — example output

This AI agent creates a complete Sales → CS handover document by:

  1. Pulling every recording tied to the deal or company across the full sales cycle (discovery, demo, negotiation, close).
  2. Extracting structured signals from the call summaries, tagged buyer quotes and deal emails: stakeholder map, pain points, commitments made, technical requirements, success criteria, risk signals.
  3. Reading deal value, stage, owner and dates from the HubSpot-synced deal in Claap, with its AI summary. A CRM MCP is only needed for contract terms or SKUs.
  4. Generating a scannable one-pager that CS can digest in 2 minutes.
  5. Delivering via Notion, Slack, or a Google Doc, whichever fits your CS intake.

Run it in Claude

Pick your AI: connect Claap, add the agent as a skill, then let it run on its own.

  1. Connect Claap

    In Claude, open Settings → Connectors → Add custom connector, paste the URL and sign in to Claap. Works on every plan (the Free plan allows one custom connector). On Team and Enterprise, an admin adds it once for everyone.

    https://api.claap.io/mcp
  2. Add the skill

    Download the skill, then in Claude open Customize → Skills → + → Upload a skill. Skills work on every plan once "Create and edit files" is on in Settings → Capabilities. Then ask Claude to run the agent by its name.

  3. Keep it at hand

    Save the instructions in a Claude project and run it whenever you need it.

Install in Claude Code

Two commands: add the marketplace, then install the plugin.

/plugin marketplace add clementsprs/claap-skills
/plugin install claap@claap-skills

After every call, in Claap

Ask your AI to turn the handover notes into a Claap AI field. It fills itself on every new call and shows in the meeting summary, and it can sync to your CRM.

Create a Claap AI field that captures the handover notes on every new sales call, and add it to the meeting summary.

🧩 How do you set up Sales → CS Handover in Claude, ChatGPT or Grok?

1️⃣ Prerequisites

  • Claap workspace with your sales calls recorded and linked to the deal. Folders such as "Sales meetings" or "Customer meetings" are an optional scope.
  • Deals synced from your CRM into Claap, so recordings and emails attach to the deal and the company.
  • Notion workspace (or Slack / Google Doc) as the destination for the handover.
  • Optional: CRM (HubSpot or Salesforce) for deal metadata enrichment.

2️⃣ Required MCP servers

  1. Claap MCP: for reading recordings, transcripts, deals and emails. Add https://api.claap.io/mcp as a custom connector in your AI (Claude, ChatGPT or Grok), as shown in the tabs above.
  2. Notion MCP(optional): to write the handover directly into a CS Notion database. Connect it in your AI's connectors.
  3. HubSpot MCP or Salesforce MCP(optional): for deal metadata such as contract terms or SKUs. Connect it in your AI's connectors.

3️⃣ Notion destination structure (optional)

If you want handovers stored in a dedicated Notion database, create a "CS Handovers" database with properties: Customer, Deal value, AE owner, Risk level, Key commitments, Watch-outs. Share the database with your AI's Notion connection so the agent can write to it. If you don't want a dedicated database, skip this step: the agent can output the handover directly as a Slack message, a Google Doc, or a single Notion page.

4️⃣ Save these instructions in your AI

💡 Add the agent as a skill (Get the skill) or paste the instructions below into a project in your AI (Claude, ChatGPT or Grok). Fill in your workspace, optional folders and an optional Notion page or database. Leave Notion empty and the handover comes back in the chat.
You are a customer success enablement specialist. You create scannable Sales → CS handover documents from the whole deal in the Claap MCP: every call, the deal AI summary and the emails, not just the latest call.

Every insight must trace to a Claap source (recording, email, or deal/contact AI summary), cited by title and date. Do not invent or assume.

🔧 INPUT VARIABLES
- [CUSTOMER] → the customer / company name
- [WORKSPACE] → Claap workspace name (optional)
- [FOLDERS] → folders to scope to, e.g. "Sales meetings", "Customer meetings" (optional)
- [NOTION_PARENT_PAGE] → Notion page or database for handovers (optional; if empty, deliver in chat)
- CRM (optional): HubSpot / Salesforce, only for contract terms or SKUs

🧠 TASKS

1. Anchor on the deal
- Use [WORKSPACE] if set, else list_workspaces. If more than one, ask which by name. Never pick one.
- search_deals (title [CUSTOMER]), then get_deal (returnAiFields: true): amount, stage, owner, dates, AI Summary. Several deals? Take the most recent Won one and say so.
- Batch ("deals won this week"): reuse a deal view from list_deal_views with statusIn [Won], closed last 7 days, or create_deal_view after confirming. get_deal_view, then steps 2 to 4 per deal.

2. Gather calls and emails
- get_recordings (dealId, hasExternalSpeaker: true, folderTitle from [FOLDERS] if set). None? Say so and stop.
- get_recording on each call for its summary.
- search_recording_transcripts (dealId), tags PainPoints, Objections, CompetitorMentions, plus a semantic query for "success criteria". Tags cover the buyer only: read the surrounding transcript for what the AE promised.
- list_contacts (companyId), get_contact per stakeholder.
- list_emails (dealId), get_email on pricing, contract or timeline threads.
- get_recording_transcript only for the closing call or a missing quote.

3. Extract
- Stakeholders: role, engagement (champion / decision maker / blocker / technical evaluator), 1–2 priority quotes.
- Pain points: verbatim, with the source call.
- Commitments: promised by the AE or agreed by the customer (timelines, integrations, pricing exceptions, custom terms), on calls or in email.
- Technical requirements: CRM, SSO, API, security, data residency.
- Success criteria, in the customer's words.
- Risks: unresolved objections, hesitant stakeholders, scope concerns, tools still in evaluation.

4. Deliver
- If [NOTION_PARENT_PAGE] is set and the Notion MCP is connected, write the handover there. Otherwise, or if the write fails, output it as Markdown in chat.
- Optional, ask first: sync to HubSpot via create_deal_field (RichText, crmField) and generate_deal_field, estimateOnly: true first.

🧩 HANDOVER STRUCTURE
- Company snapshot (industry, size, deal value, contract, close date, cycle length, AE → CSM)
- Stakeholder map (role, what they care about, 🟢/🟡/🔴/⚪, one quote)
- Deal timeline (milestones with dates, turning points)
- What was sold (features, integrations, custom commitments, plan)
- Customer context (pains, what they're replacing, success criteria, risks)
- Onboarding plan (week 1 priorities, quick wins, who to involve, watch-outs)

🧾 OUTPUT FORMAT
- Markdown, headers and bullets, emojis for scannability (🟢 🟡 🔴 ⚠️ ✅).
- One page max: 5 stakeholders, 5 milestones. Never cut the commitments.
- Flag risks and open items with ⚠️.
- Short quotes, one sentence each.
- Factual, no hype. English, or the customer's language if specified.

5️⃣ You're ready

Open a chat in your AI and give it a customer name: "Create a handover document for [Customer Name]".

🎨 How do you customize Sales → CS Handover?

Trigger

  • Run it manually after close, or schedule it in your AI to cover the deals won that week (a scheduled task in Claude or ChatGPT, an Automation in Grok).
  • Can also be triggered at any stage transition (e.g. after demo, before negotiation) for deal reviews.

Depth

  • For enterprise deals with 10+ calls, the agent reads call summaries and tagged quotes (PainPoints, Objections, CompetitorMentions) first, and opens a full transcript only for the closing call or a missing quote.
  • For SMB with 1–2 calls, the agent adapts automatically to shorter context.

CRM enrichment

  • Deal amount, stage and owner already come from Claap's CRM sync. Connect the HubSpot or Salesforce MCP only for contract terms or SKUs, or ask the agent to write the handover back to a HubSpot deal property.
  • Add product usage data via Metabase / Amplitude MCP for expansion-ready handovers.

Output destination

  • Slack: post to #cs-handovers with a formatted summary.
  • Notion: create a page in your CS database with structured properties.
  • Google Doc: export for teams that live in Docs.
  • CS tools: adapt the output for Vitally, ChurnZero, or Gainsight intake templates.

Template

  • Adapt sections to your CS intake process. Some teams want a risk score, others want an onboarding checklist.
  • Add sections for competitive context, expansion potential, key dates (renewal, QBR), product usage baseline.

❓ Need help customizing?

Contact us at support@claap.io.

Questions about Sales → CS Handover

Can ChatGPT write a Sales to CS handover from my sales calls?

Yes, once Claap is connected to ChatGPT as a custom app through Developer mode on a paid plan. ChatGPT then reads the deal's calls, AI summary and emails from Claap, and Sales → CS Handover writes the one-pager with a source for each point. Plus and Pro can read Claap data, which covers the handover; the optional HubSpot sync writes to Claap and needs Business or Enterprise.

Does Sales → CS Handover work in Claude and Grok?

Yes. In Claude, add Claap as a custom connector on any plan (one on Free). In Grok, add it at grok.com/connectors under Custom. The tabs above show each path.

What does Sales → CS Handover need?

A Claap workspace where sales calls are recorded and linked to deals synced from your CRM. Notion is optional for storing handovers, and a HubSpot or Salesforce connection is only needed for contract terms or SKUs.

Does it change anything in my CRM or in Claap?

By default it only reads, and writes the handover to Notion if you set a page. Syncing the handover to HubSpot through a Claap AI field happens only if you approve it, after the agent shows the credit cost.

How often should it run?

Once per closed deal, right after the close. You can also schedule it weekly to cover the deals won that week, or run it at a stage change for a deal review.

Share
All agents