This map is part of the customer escalation recovery guide. It answers one question: can the company still follow a recovery from system to system, and for which years?
Six systems, their records and the keys between them
A recovery rarely lives in one tool. The table lists where each record type usually sits in a B2B software company, the identifier that lets it find the next record, and who administers it.
| System | Records it holds | Linking key | Usual owner |
|---|---|---|---|
| Success platform | Health score history, risk flags, playbook tasks, timeline notes | CRM account ID synced onto the account | Customer success operations |
| Helpdesk | Escalation tickets, comments, ticket audits, tags | Organization external ID; ticket number | Support operations |
| Engineering tracker | Issues, fix status, linked releases | Ticket number quoted in the issue, or a linked-ticket field | Engineering managers |
| Billing system | Credits, invoice adjustments, approvals | Account number; ticket number in the approval note | Finance |
| Email or timeline | Executive updates, closing summaries | Account or ticket named in the subject line | VP customer success |
| CRM | Renewal opportunity, seat count, churn reason | CRM account ID | Revenue operations |
The CRM account ID is the spine. In Zendesk, for example, an organization can carry an external_id, a unique identifier meant to associate the organization with an external record, as well as the email domains associated with it. If the company stored its CRM account ID there, every ticket on that organization joins cleanly to health and renewal data. If it relied on domains alone, the join is weaker: subsidiaries, renamed customers and personal email addresses break it.
The four joins and how to test each one
Each join can be tested with a yes or no question to the system owner. Nobody needs to open a ticket.
- Account join. Does the helpdesk organization store the CRM account ID, or only a name and domain? Ask support operations.
- Work join. When a ticket goes to engineering, does the issue carry the ticket number in a field, or only in free text, or not at all? Ask an engineering manager.
- Money join. Do credit approvals quote the ticket or the account number? Ask finance.
- Narrative join. Are executive updates logged on the account timeline, sent from a shared address, or kept in personal inboxes? Ask the VP of customer success.
Score each answer as strong (structured field), partial (free text or naming convention) or missing. Three strong joins out of four is a good sign; a missing narrative join is a frequent gap, because executive updates are often written from personal mailboxes.
One fully joined case (Illustrative)
The identifiers below are invented for a fictional 480-person software company. They show what "fully joined" means in practice, not a real account.
| Step | System | Record | Key that joins it |
|---|---|---|---|
| Warning | Success platform | Score drops to red, day 0 | Account ACCT-0417 |
| Problem | Helpdesk | Priority ticket 58213, tagged API, billing, mobile | Organization external ID ACCT-0417 |
| API work | Engineering tracker | Issue ENG-2291, done day 9 | Ticket 58213 in the linked-ticket field |
| Mobile work | Engineering tracker | Issue MOB-774, released day 26 | Ticket 58213 in the linked-ticket field |
| Remedy | Billing system | Credit on two invoices, approved day 18 | Ticket 58213 in the approval note |
| Commitments | Three executive updates, days 3, 9 and 40 | Subject line names ticket 58213 | |
| Outcome | CRM | Renewal at the same seat count, day 74 | Account ACCT-0417 |
Every row points back to either ACCT-0417 or ticket 58213. That is what lets the company, and later SourceX under an agreement, reconstruct the sequence. The worked exception case tells the same story decision by decision; this table shows only the joins.
Where joins break, and which years they still hold
A join can exist today and still fail for older cases, because each system keeps history on its own clock.
| Gap | Cause | What to record in the inventory |
|---|---|---|
| Old tickets missing from views and the global audits list | Zendesk archives tickets 120 days after close; the global audits endpoint skips archived tickets, so their history is pulled ticket by ticket | Whether past exports or reports included archived tickets |
| Health or risk field changes missing after 18 months | Salesforce keeps field history up to 18 months, or 24 through the API, unless Field Audit Trail is on | Whether Field Audit Trail is on, and since when |
| Account join broken before a certain year | External IDs added to the helpdesk only after an integration project | The year structured account IDs start |
| Engineering join in free text only | Linked-ticket field adopted late | The year the field became standard |
| Executive updates absent | Written from personal inboxes | Whether a shared address or timeline logging was used, and since when |
None of these means data is lost. It means a company should state coverage per join and per year: "account join from 2021, field history 18 months, updates on timeline since 2022". The Zendesk systems page and Salesforce systems page describe each platform more broadly, and the ConnectWise PSA ticket history page covers a common alternative in managed services.
Describing join coverage in an introduction
A partner's job is to carry this map at metadata level, never the records. A useful line in an introduction reads: "Escalations since 2020; tickets joined to CRM accounts by external ID since 2021; engineering issues linked by field since 2022; executive updates logged on the success platform timeline; renewal outcomes in the CRM." That tells SourceX where the evidence is strong and where it thins out.
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's review: whether customer contracts permit use of escalation content, how customer and employee details would be de-identified, whether there is dataset demand and any offer. The who-can-license answer names the people to introduce, and the pages on customer support workflows and sales-to-customer-success handoffs cover adjacent record types. Partners sign the Channel Partner Agreement before submitting, and the first valid introduction within the 90-day window is credited when the company submits a verified application.
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 the system owners confirm that at least three of the four joins hold for several years, register as a partner, check the company on who qualifies and read the program terms before you describe the coverage.