Complaint-to-retention-decision metadata packet: a fill-in template for Freshdesk, HubSpot and Xero, with an Illustrative filled copy

Short answer

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.

Visual briefFull-size diagram
A packet of eight metadata fields (support desk, CRM, accounting, volume band, two joins, entity map, unknowns) fills in on the right while the raw records on the left, tickets, company records and credit notes, stay behind a lock.
Illustrative packet for a fictional services group. The fields describe the records; the records stay closed.

This template belongs to the complaint-to-retention-decision guide, 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.

FieldWhat to writeTypical confirmer
Support deskTool, start year, whether archived tickets existCustomer support manager
Conversation depthWhether conversations were ever pulled beyond the ticket listCustomer support manager
CRMTool, start year, which company properties hold retention decisions and since whenCustomer operations lead
AccountingTool and number of organizations, one per legal entity or sharedController
Volume bandTickets per year in bands; retention decisions per year in bandsCustomer operations lead
Hop 1 joinKey from support ticket to CRM companyCustomer operations lead
Hop 2 joinKey from CRM decision to credit noteController
Entity mapWhether a list maps each customer to its billing entitiesController
OwnersOne name per system, plus who can authorize licensingCustomer operations lead
UnknownsAnything nobody could answer, with who will find outWhoever 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.

FieldEntry (Illustrative)
Support deskFreshdesk since 2018; archived tickets present
Conversation depthTicket list exports only so far; conversations never pulled in bulk
CRMHubSpot since 2019; retention offer and churn reason properties on company records since 2021
AccountingXero, two organizations: U.S. company and Canadian subsidiary
Volume bandThousands of tickets a year; dozens of retention decisions a year
Hop 1 joinFreshdesk company to HubSpot company by email domain
Hop 2 joinHubSpot decision to Xero credit note by a reference field, used since 2022
Entity mapSpreadsheet kept by the controller mapping customers to billing entities
OwnersSupport manager (Freshdesk), customer operations lead (HubSpot), controller (Xero); CEO can authorize
UnknownsWhether 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 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 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 follows the same metadata-only rule for a CRM on its own, and architecture decision records and 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 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 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, confirm who qualifies and read the terms before you send the introduction.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

How long does it take to fill the packet?

Usually one call with the customer operations lead and a short follow-up with the controller. Most fields come from admin settings and the owners' own knowledge, not from searching records.

What if the client offers to send a sample export?

Decline it politely. The packet is deliberately metadata only, and samples are handled by SourceX under the company's own agreement if the review goes ahead.

Can the packet be reused for a different chain?

The structure can. The same fields (systems, years, volume bands, joins, owners, unknowns) work for any chain that crosses a support desk, a CRM and accounting. Change the hop descriptions to match.

Sources

  1. support.freshdesk.com/support/solutions/articles/225158-how-do-i-e…
  2. knowledge.hubspot.com/properties/export-property-history
  3. xero.com/us/about/common-questions
  4. refer.sourcex.si/terms
  5. refer.sourcex.si/rewards

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment