Skip to main content
A deal closes. The rep who spent four months learning what the customer actually wants writes a paragraph in a CRM field and moves to the next deal. Customer success inherits a signed contract and no context. Six weeks later somebody asks about a commitment made on a call in March and nobody in the room was on that call. The same thing happens when a rep leaves, goes on leave, or a territory gets redrawn. Handoffs produce the document that should have been written: what the customer is trying to achieve, what we promised, who matters, and what is still open.

Data Sources

Starter (required only): the deal record and the full call history, giving goals, decision drivers, key people, and commitments made on calls. Full (required + recommended): the same, plus what was agreed over email, what your team said internally, and any support history on the account. Commitments made in a thread rather than on a call are the ones most likely to get lost, which makes email the highest-value addition here. See the Context Graph for how each source feeds the handoff.

Choose your path

Build in Clearskies

For the closed-won case, which is the one that repeats. Build the workflow once and every deal that closes produces a handoff document for whoever takes over.

The Workflow

In the Clearskies app, open the workflow builder and describe what you want in plain language:
The app configures the trigger (a Salesforce field change), the data pulled, and the destination. Use the field-change trigger on the stage field rather than a schedule. It fires when the stage actually changes, so the handoff exists the same day rather than whenever the next sweep runs. The field has to be actively synced for the trigger to see it. The field-change trigger is Salesforce-only. On a HubSpot-only tenant, run the same workflow on a schedule that sweeps recently closed-won deals instead: a daily run finds anything closed since the last run and produces a handoff for each. Test the workflow against a deal that has already closed before publishing. Test runs are always dry, so nothing posts while you are still shaping the document.

Deploy to Slack

Once published, the handoff arrives the day the deal closes:

Customize the rollout

  • Trigger on closed won, or on any stage change or field change your process cares about
  • Match the document structure to the intake format your CS or implementation team already uses
  • Route it to a channel, the receiving owner’s DM, or both
  • Add sections your team needs: contract specifics, integration requirements, renewal date
  • Write the handoff summary back to the account record as well as posting it, so it lives where the next person looks

Build in Claude or ChatGPT

For every handoff that is not a closed deal. A rep leaves, someone is out for two weeks, a territory gets redrawn, an escalation moves to a different owner. These do not have a trigger to fire on, so ask for them.

The Prompt

Open Claude or ChatGPT with the Clearskies MCP connected and paste this (or modify to your needs). Replace the account name with your own.

Make it yours

  • Add Do this for every open deal owned by [rep] when covering a departure or leave, rather than one account at a time.
  • Add What should I ask them on my first call that the record cannot tell me to turn the handoff into a first-meeting agenda.
  • Add Flag anything that looks like it was promised but not delivered when the handoff is happening because something went wrong.

The Skill (Claude)

The clearskies:account-brief skill in the Clearskies plugin for Claude generates a full account brief from the Context Graph: CRM, calls, email, calendar, and Slack in one view. It is the closest ready-made version of this and a good starting point before a handoff format is customized for your team.
Want this packaged for your team? Reach out and we’ll help you customize the skill to your workflow.

The Plugin

Ready to make this part of your team’s workflow? We’ll set up the Clearskies plugin with you. Clearskies workflows, Claude skills, all tailored to how your team works. Book 15 minutes →

Next steps

  1. Sign in to Clearskies
  2. Connect your data sources
  3. Get your Clearskies MCP server and try with Claude or ChatGPT