# Complaint-to-retention metadata packet template | SourceX

Canonical: https://refer.sourcex.si/resources/complaint-to-retention-decision-metadata-packet
Last updated: 2026-11-04

A referral partner can collect eight kinds of facts about a complaint-to-retention-decision history without reading a ticket, a company record or an invoice: which support desk, CRM and accounting systems hold the chain and since when, a rough volume band, the key used for each join, how many legal entities bill customers, who owns each system, and what nobody yet knows. That is the whole packet. Names, ticket text, credit amounts and invoice details stay out.

This template belongs to the [complaint-to-retention-decision guide](/guides/chain-complaint-to-retention-decision), which explains how Freshdesk, HubSpot and Xero join. The packet is what you hand SourceX with an introduction.

## The blank packet

Copy these fields into a short document and fill them in during a call. Each field has a single confirmer, so a gap points to the person who can close it.

| Field | What to write | Typical confirmer |
|---|---|---|
| Support desk | Tool, start year, whether archived tickets exist | Customer support manager |
| Conversation depth | Whether conversations were ever pulled beyond the ticket list | Customer support manager |
| CRM | Tool, start year, which company properties hold retention decisions and since when | Customer operations lead |
| Accounting | Tool and number of organizations, one per legal entity or shared | Controller |
| Volume band | Tickets per year in bands; retention decisions per year in bands | Customer operations lead |
| Hop 1 join | Key from support ticket to CRM company | Customer operations lead |
| Hop 2 join | Key from CRM decision to credit note | Controller |
| Entity map | Whether a list maps each customer to its billing entities | Controller |
| Owners | One name per system, plus who can authorize licensing | Customer operations lead |
| Unknowns | Anything nobody could answer, with who will find out | Whoever owns it |

Bands, not counts: "thousands of tickets a year" is enough and avoids anyone running reports for you.

## Why each field earns its place

**Conversation depth.** Freshdesk's ticket list export lets an admin choose fields and a format but does not include the full conversation or archived tickets. A company that only ever ran that export holds subjects and statuses, not complaints. Knowing which one exists changes the whole description.

**CRM decision properties.** Retention decisions logged in a dated property are joinable; decisions written in notes are not. Note also that HubSpot's property history export is limited to recent revisions, up to 20 for company and deal properties, so a long-running account may show only its latest decisions in an export even if the record shows more on screen.

**Accounting organizations.** Xero lets a subscriber add as many organizations as they like, each on its own plan. A group with a U.S. company and a Canadian subsidiary commonly runs two, and the same customer may be set up separately in each. That is why the entity map field exists.

**Unknowns.** An honest blank is more useful than a guess. A packet with three named unknowns tells SourceX exactly what to ask first.

## An Illustrative filled packet

A fictional 300-person facilities services group with a U.S. operating company and a Canadian subsidiary, filled in from one call and one follow-up email.

| Field | Entry (Illustrative) |
|---|---|
| Support desk | Freshdesk since 2018; archived tickets present |
| Conversation depth | Ticket list exports only so far; conversations never pulled in bulk |
| CRM | HubSpot since 2019; retention offer and churn reason properties on company records since 2021 |
| Accounting | Xero, two organizations: U.S. company and Canadian subsidiary |
| Volume band | Thousands of tickets a year; dozens of retention decisions a year |
| Hop 1 join | Freshdesk company to HubSpot company by email domain |
| Hop 2 join | HubSpot decision to Xero credit note by a reference field, used since 2022 |
| Entity map | Spreadsheet kept by the controller mapping customers to billing entities |
| Owners | Support manager (Freshdesk), customer operations lead (HubSpot), controller (Xero); CEO can authorize |
| Unknowns | Whether service contracts limit use of customer communications (general counsel) |

Read as a whole, this says: a complaint history from 2018, decisions dated from 2021, credits joinable from 2022, two entities bridged by a spreadsheet, and one legal question open. That is a precise picture, and no record was opened to produce it. The [missing-context comparison](/guides/complaint-to-retention-decision-missing-context) shows one case running through these same systems.

## What to leave out, and what to add only when real

Leave out customer names, ticket text, credit and invoice amounts, screenshots and samples. If someone offers a file, decline it; the packet does not need one.

Add timing only when it is documented. If an [ERP replacement](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) or a support desk migration has a date in a project plan, note it with its source: that is real timing, not pressure. The [HubSpot inventory template](/resources/a-metadata-only-hubspot-inventory-template-for-company-introductions) follows the same metadata-only rule for a CRM on its own, and [architecture decision records](/data-types/architecture-decision-records) and [shared mailbox retention](/guides/shared-mailbox-retention) cover other places decisions get written down.

## Sending the packet with the introduction

Attach the packet when you introduce the authorized contact. Before you do, confirm the company has 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and a contact with authority over every entity listed. 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.

Sign the Channel Partner Agreement first. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, one partner per company. Tell the client that SourceX funds any reward separately and never deducts it from the company's payout; the [rewards page](/rewards) has every condition. Unknown until SourceX reviews it: what contracts allow, which cases join across entities, and whether a buyer wants the set. The [completeness checklist](/resources/complaint-to-retention-decision-completeness-checklist) can be run alongside the packet if you want a scored view.

## 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 you can fill every field of the packet, or name who will fill the gaps, [register as a partner](/register), confirm [who qualifies](/who-qualifies) and read the [terms](/terms) before you send the introduction.

## Sources

- https://support.freshdesk.com/support/solutions/articles/225158-how-do-i-export-my-tickets-from-freshdesk-
- https://knowledge.hubspot.com/properties/export-property-history
- https://www.xero.com/us/about/common-questions/
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
