> ## Documentation Index
> Fetch the complete documentation index at: https://clearskies.cc/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Handoffs

> When a deal closes or an account changes hands, whoever takes over gets everything: goals, commitments, key people, and what was promised to whom.

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

| Category         | Required | Recommended |
| :--------------- | :------- | :---------- |
| CRM              | ✓        |             |
| Calls            | ✓        |             |
| Email + Calendar |          | ✓           |
| Messaging        |          | ✓           |
| Support tickets  |          | ✓           |

**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](/docs/unifying-gtm-data/customer-context-graph) for how each source feeds the handoff.

### Choose your path

| Path                       | Best for                                                                                  | Output is delivered                   |
| :------------------------- | :---------------------------------------------------------------------------------------- | :------------------------------------ |
| Build in Clearskies        | Teams where closed-won should always produce a handoff, with nobody remembering to run it | To Slack DMs or channels              |
| Build in Claude or ChatGPT | Rep departures, leave cover, territory changes, and any handoff that is not a closed deal | In the Claude or ChatGPT conversation |

## 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:

```text theme={null}
When a Salesforce opportunity's stage changes to Closed Won, write a
handoff document from the Clearskies Context Graph. Cover what the
customer is trying to achieve, what we committed to and where, the key
people and their roles, open items, and anything that was raised and never
resolved. Post it to the #customer-success channel and to the account's
Slack channel.
```

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:

```text theme={null}
Handoff — Acme Corp
Closed Won Jul 31 · $84,000 · Renewal + analytics module
From: Daniel (AE) · To: customer success

What they are trying to achieve
Consolidate reporting that currently runs in three places. The renewal was
never in doubt; the analytics module is what they actually bought, and the
success criteria they named on the Jun 12 call is a single weekly report
their VP can read without asking an analyst to build it.

What we committed to
• 30-day pilot of the analytics module at no charge, offered May 21 on the
  renewal review call, because onboarding capacity before Q4 was the
  blocker. Pilot clock has not started.
• Introduction to the implementation lead, promised May 21, done May 23.
• Same paper for renewal and expansion. Done, signed Jul 31.

Key people
• Sarah Kim — champion, drove this from the start, on every call, replies
  within a day. Went noticeably more cautious after legal raised data
  retention on May 6.
• David Park — Director, Sales Ops. Joined Acme in April. Owns onboarding
  capacity and was the source of the Q4 concern. Never engaged over email,
  only on calls.
• Mark Chen — VP Sales, signed. Disengaged during the expansion
  conversation and was absent for 9 days at the point the deal size grew.

Still open
• Security review for the added module. Sarah said procurement may want
  one. Never confirmed either way.
• Data residency questions raised by Acme's legal team on May 10. Answered
  verbally on a call, never in writing.

Raised and never resolved
On the Jun 12 call Sarah asked whether the weekly report could be sent to
a distribution list rather than individual users. No answer was given and
it did not come up again.
```

### 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.

```text theme={null}
Using the Clearskies Context Graph, write a handoff document for Acme.
I am taking this account over and I have never spoken to them.

Cover:
- What they are trying to achieve, in their words
- Everything we have committed to, and where each commitment was made
- Who the people are, their roles, and what the record says about each
  relationship
- What is open right now
- Anything raised on a call or in a thread that never got resolved

Be specific about dates and sources. If a commitment is ambiguous, say
that it is ambiguous rather than resolving it for me.
```

### 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.

<Tip>
  Want this packaged for your team? [**Reach out**](mailto:support@clearskies.cc) and we'll help you customize the skill to your workflow.
</Tip>

## 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 →**](https://calendly.com/pouyan/new-meeting)

## Next steps

1. [Sign in to Clearskies](https://app.clearskies.cc/)
2. Connect your data sources
3. Get your [Clearskies MCP server](/docs/building-with-clearskies/mcp-server) and try with [Claude](/docs/building-with-clearskies/mcp-clients/claude) or [ChatGPT](/docs/building-with-clearskies/mcp-clients/chatgpt)