# Closed deals handed to success in full. Success handoff is an AI agent for the sales to customer success handoff. Name a closed deal and it reads it in HubSpot and in your discovery notes, then sends one Slack message: what they bought, why they bought, every promise made and whether the contract covers it, who's who on both sides, risks and first steps. ## Why do customers repeat themselves after the sale? Because what sales learned rarely survives the handoff. The deal facts are in the CRM, the reasons and promises are in a rep's notes, and the template asking for both gets filled in on a busy Friday, if at all. Customer success starts the first call asking what the customer already told sales. Without it: - The customer explains their goals all over again. - A training promised in the sale that nobody books. - Success meets the IT lead for the first time at a blocker. - The handoff doc left half filled in. With Success handoff: - A handoff for every closed deal, in one message. - HubSpot's facts next to the discovery notes. - Every promise checked against the contract. - Risks and first steps before the kickoff. ## What goes into a sales to customer success handoff? Four things customer success needs on day one, then the risks and the first steps. ### What they bought Amount, stage, close date, plan, seats and term, with HubSpot as the source for the numbers. For example: Amount, Seats, Term. ### Why they bought The reasons from discovery, in the customer's own terms, so onboarding starts from them. For example: Goals, Must-haves. ### What was promised Every promise made during the sale, one per line, each marked if it's outside the contract. For example: Training, Dates, Roadmap. ### Who's who The people on their side and yours, one short line each: who signed, who owns it, who can block it. For example: Buyer, Owner, Approver. ## How does an AI handoff agent work? Every run follows the same five steps for one deal, then sends one handoff. HubSpot is only read, and only the last step writes anything. 1. **Finds the deal** (HubSpot, reads): Amount, stage, close date, company and contacts. 2. **Names the owner** (HubSpot, reads): The deal owner on your side, looked up by their HubSpot ID. 3. **Reads the discovery notes** (Document search, reads): Contract terms, why they bought, promises, people and risks. 4. **Checks promises against the contract** (Document search, reads): Anything outside the terms is marked 'not in contract'. 5. **Sends the handoff** (Slack, posts): Seven short sections, under 300 words, ending with its sources. When it runs: - @mention: @success-handoff Customer N closed on Thursday - Webhook: Run from a shortcut, with the deal's name, when you want a handoff - Schedule: Every Friday at 15:00, for the deal named in the sentence ## From one sentence to a handoff. Describe the job, let Arclyx draft the agent, test it once on a real deal, create it, then read the handoff that lands in your Slack messages. Every promise says whether the contract covers it. Example output in your Slack DMs, "Handoff · Customer N · Business plan" (placeholder companies): - Customer N · Deal: $33,600 a year for 35 seats, closed won 22 October, 12 months from 1 November. A 10% first-year discount, tied to a case study by month six. Source: example-a.com/deal - Customer N · Why they bought: Drafts-only email, so a person approves every message to their customers, and agents their ops staff can build without an engineer. A weekly report in Slack was the third reason. Source: example-a.com/discovery-notes - Customer N · Promises: Two training sessions in the first 30 days, two agents live by 30 November, a security questionnaire by 7 November. Each marked 'not in contract': none is in the signed terms. Source: example-a.com/discovery-notes - Customer N · Who's who: Their COO signed; the operations manager owns it day to day; the IT lead approves every connection. Ours: the account executive, and the sales engineer running the first training. Source: example-a.com/deal - Customer N · Risks: The IT lead is wary of connecting tools. Two of their sites never used the trial. First steps: send the questionnaire, book the training, win back the two sites. Source: example-a.com/discovery-notes Sources: HubSpot deal, discovery notes · under 300 words ## One handoff, four teams. The same handoff answers a different question for each person who picks up the customer. - CSMs: The whole story of the deal before the kickoff call. - Account executives: A handoff written for them, from their own notes. - Onboarding: What was promised and by when, with first steps. - Success leads: Every promise outside the contract, flagged early. ## How do you write a customer success handoff with AI? Keep the deal in your CRM and the discovery notes in one document. When the deal closes, ask an AI agent to read both and write the handoff: what they bought and why, every promise checked against the contract, who's who, risks and first steps. In Arclyx that's five steps, starting with one sentence. 1. **Describe the job**: One sentence: which deal, what the handoff covers, and where it goes. 2. **Connect HubSpot**: The agent gets only search and read tools for deals, companies, contacts and users, so it can't write back. 3. **Add your discovery notes**: Upload the deal notes as a document, terms included if you have them. 4. **Watch a dry run**: Optional. Hand off a real deal and read it before anything is sent. 5. **Ask for a handoff**: @mention it with the closed deal's name. It runs when you ask, one deal at a time. The sentence that built it (@mention, When you ask): > When I name a closed deal, read it in HubSpot and our discovery notes, and send me the handoff for customer success: what they bought, why they bought, what we promised, who's who on both sides, risks and the first onboarding steps. ### Or start from one of these sentences - Straight to the CSM: "When I name a closed deal, write the customer success handoff from HubSpot and our notes and post it to #cs-handoffs for the assigned CSM." - Promises only: "When I name a closed deal, list every promise from the sales notes and mark each one that isn't in the contract." - Kickoff agenda: "When I name a closed deal, write the handoff and add a kickoff call agenda built from why they bought and what we promised." - First 90 days: "When I name a closed deal, write the handoff and list every date we promised for the first 90 days, soonest first." ## AI handoff vs a template and the CRM. A handoff template and the HubSpot deal record each hold part of what success needs. Here is what each one gives you, and doesn't. | What you need | Handoff template | HubSpot deal record | Success handoff | | --- | --- | --- | --- | | Deal facts | Typed in by the rep | Amount, stage and close date | Read from HubSpot, which wins a conflict | | Why they bought | If the rep writes it | In logged notes and calls | From the discovery notes | | Promises checked against the contract | Rarely | No | Each one marked if it's outside the terms | | Who's who | If someone fills it in | Associated contacts | Both sides, one line each | | What you get | A doc to fill in | A record and its timeline | One handoff in Slack | Source: [HubSpot knowledge base: record timelines](https://knowledge.hubspot.com/records/filter-activities-on-a-record-timeline), checked 24 October 2026. ## Is it safe to give an AI agent your CRM? It only reads HubSpot and your notes, and writes one message to you. Every run is recorded and has a spend ceiling by default. ### Every run is recorded - Every step, in order: Every run records the tools it called, with a short preview of each result. Only the person who started a run can open its content. - Every source, named: The last line says whether the HubSpot deal and the notes were found, and conflicts are stated. - What each run cost: Tokens and cost are recorded per run and per agent, next to your plan's limits. - A spend ceiling, on by default: Each run has a dollar ceiling unless you remove it. A run stops before it goes over it, and tells you. ### It can - Search and read HubSpot deals, companies, contacts and users - Read the documents you can access in Arclyx - Message you on Slack, post to one channel you name, or email you ### It can't - Create or change anything in HubSpot - Contact the customer - Invent a promise, contact or date - Email anyone but you ## Sales to customer success handoffs, answered. ### What is a sales to customer success handoff? The note sales writes when a deal closes, so customer success starts with the full story: what the customer bought, why, what was promised along the way and who matters on their side. Without it, the customer explains everything again in the first call. ### What does it put in the handoff? Seven sections: the deal snapshot, what they bought, why they bought, every promise made, who's who on both sides, risks, and up to four first onboarding steps. It ends with a line saying whether HubSpot and the notes were found. ### Does it change anything in HubSpot? No. It's given only HubSpot tools that search and read deals, companies, contacts and users. It can't create, update or delete a record, so the deal stays exactly as sales left it. ### What if HubSpot and the notes disagree? HubSpot wins on amount, stage and dates, and the handoff says the notes differ. If the deal isn't in HubSpot at all, it says so at the top and writes the handoff from the notes alone. ### How does it treat promises outside the contract? When the notes include contract terms, every promise outside them is marked 'not in contract' on its own line. With no terms to check against, it marks each one as promised in the sales notes, with contract coverage unverified. ### Does it contact the customer? No. It writes the handoff for your team, and its one message goes to you or a channel you choose. It never invents a promise, contact, amount or date: what it can't find, it marks 'not found'. ### Can it hand off several deals at once? One deal per run, so each handoff stays under 300 words. Name several and it hands off the first and asks whether to carry on. ### Do I need to write code? No. Describe the job in one sentence. Arclyx drafts the agent, you sign in to HubSpot once and add your discovery notes, and you can watch a dry run before you create it. ## Agents that work well with it - [Customer call brief](https://arclyx.ai/agents/customer-meeting-prep): A brief before every customer call - [Renewal risk radar](https://arclyx.ai/agents/churn-prediction): Every renewal in the next 90 days, rated - [Meeting brief](https://arclyx.ai/agents/meeting-prep): A brief for every external meeting [AI for customer support and success](https://arclyx.ai/solutions/customer-support): AI customer service agents that work behind the scenes: the queue sorted, replies drafted for you, renewals at risk rated and every handoff written. ## Early access Build your success handoff. One sentence in, a working agent out. Join the beta and we'll set you up. Join at https://arclyx.ai/#join or write to hello@arclyx.ai. Last updated 24 October 2026.