# Escalation recovery records before renewal | SourceX

Canonical: https://refer.sourcex.si/guides/workflow-customer-escalation-recovery
Last updated: 2026-11-04

Before a customer success platform renewal, inventory the record classes that show how at-risk accounts were recovered: health score changes, escalation tickets, executive updates and the renewal decision that followed. Note which system holds each class, how many years it covers, who owns it and when access to the old platform really ends. Keep the inventory at metadata level, then introduce the person who can authorize a licensing discussion, usually through the customer success director.

A customer escalation recovery is the work that pulls an account back from the edge: a critical issue, a falling health score, a run of executive updates, and finally a renewal or a churn. The renewal of the platform that holds that story is a decision point, because health scores, playbook tasks and timeline entries often live only there.

## What should be inventoried before a customer platform renewal affects customer escalation recovery history?

Inventory four things: the record classes, the years each system covers, the owner of each system, and the real date when access to the current platform ends if the company switches at renewal.

Ask the customer success director or operations lead:

1. **Which recovery records exist?** Health score history, escalation flags or playbooks, executive update emails, closing summaries, renewal and churn reasons.
2. **How far back does each go?** Count years per system from what the system shows, not from memory.
3. **Who administers each system?** Customer success ops, support ops, RevOps or IT. Administration is not ownership of the content.
4. **What does the contract say about access after the term?** The real deadline is the vendor contract's end of read access and any export window, confirmed by the company.

What not to do: do not recommend keeping data the company has no authority or reason to keep, and do not ask for samples, screenshots or exports for a licensing conversation. If the company already plans to retain its history through the switch, that is its own decision. The inventory only describes what exists so a decision-maker can weigh it.

A useful test for whether the archive is worth introducing: can the company name one escalation from two or more years ago and still find the health signal, the executive update and the renewal decision for it? If the answer is yes for many accounts, the history is likely deep enough to describe.

## Which recovery records may already be thinner than the team assumes?

Some of the history has a default clock of its own, separate from the renewal. Two examples from common systems in a success stack:

| Record | System default | What to ask |
|---|---|---|
| Field history on accounts and opportunities (owner, stage, risk fields) | Salesforce keeps field history up to 18 months, or 24 months through the API, when Field Audit Trail is off | Is Field Audit Trail on, and since when? Were older changes exported? |
| Closed support tickets linked to the escalation | Zendesk archives tickets 120 days after they close; they stay accessible but drop out of views | Do reports and exports the team relies on include archived tickets? |
| Ticket change history | Zendesk audits are a read-only record of every update, but the global audits endpoint skips archived tickets | Would an export pull audits ticket by ticket, or miss the archived ones? |
| Health score history | Set by the success platform and its contract | Does the platform store past scores, or only the current one? |

None of this is a reason to copy anything. It changes what the inventory should record: not "we have five years of escalations", but "five years of executive update emails, 18 months of risk field history, current health scores only". That precision is what lets SourceX and the company judge the archive later.

## How should the inventory line up with the renewal calendar?

Count back from the renewal date. The schedule below is Illustrative, for a fictional company that might switch platforms at renewal.

| Day (Illustrative) | Step | Output |
|---|---|---|
| Day -120 | List record classes with the customer success director | One line per class: system, years, owner |
| Day -90 | Confirm system owners and admins in writing | Named owner for each class |
| Day -60 | Check the contract's export window and post-term read access | The real access end date |
| Day 0 | Renewal decision | Stay, switch or run both |
| Day +30 | Read access ends, if the contract allows a 30-day tail | Inventory is complete before this date |

If the company renews and stays, the inventory is still useful: it records what exists before the next migration project starts.

## Does the company qualify?

The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, 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 with the company: whether customer contracts allow the records to be licensed, how customer and employee details would be de-identified, whether there is dataset demand, and any offer. Partners must sign the Channel Partner Agreement before submitting introductions, and attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. The [industries hub](/industries), the [software and SaaS page](/industries/software-and-saas) and the [CX consultant program page](/for/cx-consultant-referral-program) describe the wider fit, and [support escalation records](/data-types/support-escalation-process) covers the ticket-level view.

## Go deeper on customer escalation recovery

- [Customer escalation recovery referral brief template](/resources/customer-escalation-recovery-referral-brief-template): a fill-in template for the introduction note.
- [Customer escalation recovery exception examples](/guides/customer-escalation-recovery-exception-examples): worked cases of escalations and the records that explain how each was handled.
- [Customer escalation recovery records across systems](/guides/customer-escalation-recovery-records-across-systems): a map of the links between success platform, helpdesk, CRM and email.
- [Who can license customer escalation recovery records](/questions/who-can-license-customer-escalation-recovery-records): a short answer on which decision-maker to introduce.

## 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 your client can trace old escalations from health signal to renewal and the platform renewal is approaching, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before the inventory deadline passes.

## Sources

- https://refer.sourcex.si/terms
- https://developer.zendesk.com/api-reference/ticketing/tickets/ticket_audits/
- https://support.zendesk.com/hc/en-us/articles/4408887617050-About-ticket-archiving
- https://help.salesforce.com/s/articleView?id=xcloud.tracking_field_history.htm&language=en_US&type=5
