# Customer success handover records as AI data | SourceX

Canonical: https://refer.sourcex.si/guides/customer-success-handover-ai-data
Last updated: 2026-11-04

Commitments made at a customer-success handover link to outcomes through four records: the handover note that states the promise, the success-plan objective or task that tracks it, the support cases and escalations raised when it slipped, and the renewal or churn record at term end. The records matter as AI training and evaluation data only when a shared account ID, and ideally a commitment reference, joins them. Unresolved promises are the most telling part of that chain.

## What records connect customer-success commitments to escalations and renewal outcomes?

Four records, held in different systems, joined by keys the company already uses. Many software and services firms keep each piece without ever looking at them as one chain.

1. **The commitment.** The handover note or onboarding record that says what sales promised: a custom integration, a go-live date, a named contact, a service level. The [sales-to-customer-success handoff page](/data-types/sales-to-customer-success-handoff) covers what these notes contain.
2. **The tracked objective.** Customer-success platforms turn promises into tracked work. In Gainsight, for example, a success plan is made of Objective CTAs, each with an owner, due date, status and optional success criteria, and each objective keeps its own activity timeline.
3. **The escalation.** When a promise slips, it surfaces as support cases. Help desks and CRMs keep the history: Zendesk ticket audits are a read-only record of every update to a ticket, and Salesforce entitlement milestones track service levels such as first response and resolution time on each case, with warning and violation actions.
4. **The outcome.** The renewal, downgrade or churn record at term end, usually an opportunity or contract record in the CRM, often with a reason code.

The value is in the gaps between them. A promise with an objective, two escalations and a downgraded renewal tells a different story from one closed on time. An AI system meant to help with account management would need examples of exactly that: which commitments go unmet, how early the warning signs appear, and what follows.

## A worked record chain: one account, four systems

Illustrative. A 340-person payroll software vendor onboards a 900-employee healthcare customer. The names, dates and systems below are fictional and show structure only; a partner never sees these records.

| Record | Where it sits | Key fields | Joins to the next record by |
|---|---|---|---|
| Handover note, month 0 | CRM opportunity attachment | Commitment C-14: general-ledger export by go-live, day 60 | Account ID and commitment C-14 |
| Success-plan objective, month 0 | Customer-success platform | Objective "GL export live", owner, due day 60, status at risk on day 55 | Account ID; objective title cites C-14 |
| Escalation case, month 3 | Help desk | Priority raised twice, resolution milestone missed, fix shipped day 118 | Account ID; case tag cites C-14 |
| Renewal record, month 12 | CRM renewal opportunity | Renewed at fewer seats, reason code "implementation delay" | Account ID |

Read down the right-hand column. The account ID joins all four records; the commitment reference joins three. Without that second key, a reviewer can only guess that the escalation and the downgrade were about the same promise. With it, the chain records an unresolved promise from statement to consequence.

## How to tell whether a company's chain is intact

Ask about joins, not contents. These questions stay at metadata level and can be answered by a CS operations lead in one conversation.

| Question | A strong answer | A weak answer |
|---|---|---|
| Is the handover recorded in a system, not only in email? | A template in the CRM or CS platform since a known year | Ad hoc emails and slide decks |
| Do objectives or tasks reference the original commitment? | Yes, by ID, tag or a required field | Free text, inconsistently |
| Do support cases carry the account ID? | Always, synced from the CRM | Only for some queues |
| Is the renewal outcome recorded with a reason? | Reason codes on every renewal and churn | Won or lost only |
| How many years and accounts does it cover? | Several years, hundreds of accounts | One year, a handful |

A company with strong answers in three or more rows is worth raising with the owner. One with weak answers throughout may still have useful support history; the [support escalation page](/data-types/support-escalation-process) covers that case on its own.

## Company qualification questions

- **Which records exist?** Note system names in plain text (for example, Salesforce, Gainsight, Zendesk), the record types and the rough span.
- **Who owns them?** The company, subject to its customer contracts. The question is whether those contracts restrict reuse of account data; the partner notes yes, no or unknown.
- **Who can authorize a licensing discussion?** The CEO, often with the COO or CFO preparing the case and counsel advising. The head of customer success knows where the records are but rarely decides.
- **Does the company meet the basics?** 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

What stays unknown until SourceX reviews it: whether buyers want this record chain, how customer identities would be handled in de-identification, the rights review result and any offer. Partners never request exports, screenshots or sample accounts.

## Limits and unanswered questions

The chain is only as good as its weakest join. Many companies changed CS platforms or help desks partway through, which can break the account ID history; a [shift handover log](/data-types/shift-handover-log) has the same problem across teams. Some renewal reasons are entered after the fact and may be unreliable. And a company preparing for a sale should handle records under its transaction plan first; the [IT handover checklist for a sale of business](/resources/it-handover-checklist-sale-of-business) covers that situation. For churn analysis as an internal exercise, see [B2B customer churn analysis](/guides/customer-churn-analysis-b2b).

Keep two payments distinct in any conversation. Company compensation is what SourceX pays the company for a qualifying completed handoff under its own agreement. The referral reward is paid separately by SourceX and never reduces the company's payout. Illustrative: an Actual Supplier Payout of $250,000 would mean a default reward of $62,500.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client's handover, escalation and renewal records join on a shared account ID, [register as a partner](/register), confirm the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its owner.

## Sources

- https://support.gainsight.com/gainsight_nxt/Success_Plans/About/Success_Plan_Overview
- https://help.salesforce.com/s/articleView?id=sf.entitlements_milestones_overview.htm&language=en_US
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- https://refer.sourcex.si/terms
