This memo template is part of the customer escalation recovery guide, which covers what to inventory before a customer platform renewal.
The fill-in memo
Copy the text below and replace each bracket. Keep it to one paragraph per line so the director can correct a single line without rewriting the rest.
Subject: Escalation recovery records, for a licensing discussion
- We are a [sector] company in [country] with about [number] full-time staff at peak.
- We handle escalations where [describe the hard case, for example one customer issue that needs several product teams].
- For about [years] we have kept [record classes] in [systems].
- We count roughly [number] escalations a year from [the tag, priority or report used], without opening them.
- [Any documented date: platform contract renewal, migration, archive rule, or "no access event is planned".]
- Open question: [the one thing nobody yet knows about rights or completeness].
- [Role] would sponsor a discussion and [role] would decide, with [counsel or privacy lead].
Seven lines are enough. Anything longer usually means a record has crept in.
How to answer each bracket
Line 1, the company. Headcount means full-time employees at peak, not contractors. If the director is unsure, write "about" and the source, such as the HR system.
Line 2, the hard case. Name the kind of escalation that makes the history worth describing. A critical issue spanning several product teams is a strong example, because the evidence of who did what is spread across systems; the worked exception case shows one end to end. One sentence is enough.
Line 3, records and systems. List record classes, not documents: health score history, escalation tickets with their change history, executive update emails, billing credits, renewal and churn decisions. Then the systems. Precision helps here. In Zendesk, ticket audits are a read-only history of every update to a ticket, so "tickets with full audit history" is a meaningful claim. If health or renewal fields sit in Salesforce without Field Audit Trail, field history only reaches back 18 months (24 through the API); say so rather than claiming six years of score history.
Line 4, volume. A count from tags or priority fields is metadata. Note whether it includes archived tickets: Zendesk archives tickets 120 days after close and they drop out of views, so a view-based count can undercount older years.
Line 5, the date. Only a documented event belongs here, such as a platform contract renewal or a planned migration. If none exists, say so. Do not invent urgency.
Line 6, the open question. This is the most useful line, because it tells SourceX where its rights review starts. Write a fact plus an uncertainty.
Line 7, sponsor and signer. Usually the customer success director sponsors and the CEO decides. The who-can-license tree explains the roles in more detail.
Completed memo (Illustrative)
The company below is fictional, invented for this page. The figures are placeholders, not a real company's data or a completed deal.
Subject: Escalation recovery records, for a licensing discussion
- We are a B2B scheduling software company in the U.S. with about 480 full-time staff at peak.
- We handle escalations where one customer issue needs several product teams, such as API, billing and mobile.
- For about six years we have kept escalation tickets with audit history in our helpdesk, health score and renewal history in our success platform and CRM, and executive updates in email.
- We count roughly 300 escalations a year from the escalation tag, without opening them; the count includes archived tickets.
- Our success platform contract renews in the spring and we have not decided whether to switch.
- Open question: our enterprise contracts restrict use of customer data, so counsel would need to review scope.
- Our customer success director would sponsor a discussion and our CEO would decide, with general counsel.
Checking the memo before it is forwarded
Run each line through one test before the director sends it on.
| Line | Test | Fails if |
|---|---|---|
| 1 Company | Headcount is full-time staff at peak | Contractors are counted, or the figure has no source |
| 2 Hard case | Describes a kind of case, not a specific one | It names a customer or an incident date |
| 3 Records and systems | Lists record classes and systems with honest coverage | It claims years of history a system's defaults do not keep |
| 4 Volume | Comes from a tag or report count | Someone opened tickets to count or classify them |
| 5 Date | Is documented by a contract or plan | It is a guess or a pressure tactic |
| 6 Open question | States a fact plus an uncertainty | It is a sales claim such as "great data" |
| 7 Sponsor and signer | Names roles that exist at the company | The signer is a platform admin |
If any line fails, fix it before the memo moves. A memo that overstates coverage costs more time in review than one that admits a gap.
Who receives the memo, and what qualifies
Send the draft to the customer success director first. Once they have corrected it, they forward it to the CEO; the warm introduction brief has wording for the covering note, and the client opportunity brief generator produces a similar summary for other workflows. Related record types are described on the pages for support escalation records, sales-to-customer-success handoff notes and AI-to-human handoff data.
The introduced company needs 50+ full-time employees at peak (contractors excluded), a 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. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application. SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout. Dataset demand, the rights result, de-identification and any offer stay unknown until SourceX reviews the opportunity.
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.
When every line of the memo passes its test and the director is ready to forward it, register as a partner, check the company on who qualifies and read the program terms first.