# Complaint-to-retention completeness scorecard | SourceX

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

Five gaps break a complaint-to-retention-decision trail: customer identifiers that do not match across Freshdesk, HubSpot and Xero; retention decisions logged without a date; property values overwritten until early decisions drop out of the export; credit notes with no reference back to the complaint; and billing split across legal entities. Score each from metadata, then run the two-entity test, because that gap is the one most likely to go unnoticed until someone tries to join the records.

This scorecard supports the [complaint-to-retention-decision guide](/guides/chain-complaint-to-retention-decision). Run it before describing any company's retention history as complete.

## Scoring rules

Use three marks. **Pass**: the record exists with the key or date the check asks for, across most of the period. **Partial**: it exists for part of the period, for some records, or through a workaround such as a spreadsheet. **Fail**: missing, or no one can say.

Write down who answered each check and how they know. A feature that exists in the software is not a pass; the question is whether the company used it and from when. The finished scorecard holds only systems, dates, bands and owners.

## The five gap checks

| Check | How it shows up when it fails | How to check it at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1. Identifier | The customer is named differently in each system | Ask whether a shared customer ID or email domain links Freshdesk, HubSpot and Xero | Shared ID or domain in all three | Matches in two systems only | Matched by reading names |
| 2. Timestamp | Retention decision sits in a free-text note | Ask whether the decision is captured in a dated CRM property | Dated property since early in the period | Property added recently | Notes only |
| 3. Version | Property overwritten many times; early values gone from export | Ask how often retention properties change per account and how long accounts run | Few changes per account | Long-running accounts with many changes | History unknown |
| 4. Outcome link | Credit note does not mention the case or deal | Ask whether credit notes carry a ticket or deal reference | Reference field used consistently | Used for some credits only | No reference |
| 5. Entity | Customer billed by two organizations | Ask how many legal entities bill customers and whether a cross-entity customer list exists | One entity, or a maintained cross-entity ID | Spreadsheet map kept by finance | No map |

Three checks rest on documented behavior. HubSpot shows a record's past property values with the date and source of each change, which is what makes check 2 a pass when the property is used. Its property history export, however, is limited to recent revisions, up to 20 for company and deal properties, which is why check 3 asks about change frequency. Xero lets a subscriber add as many organizations as they like, so a group with several legal entities often keeps several sets of books, the root of check 5.

## Supporting checks on the complaint side

Two quick questions sharpen check 1 and the outcome link.

| Supporting check | Why it matters | Pass | Partial | Fail |
|---|---|---|---|---|
| Conversation depth | Freshdesk's ticket list export leaves out the full conversation and archived tickets | Conversations pulled, archived included | Conversations for recent years only | Ticket list only |
| Credit timing | In Xero, a credit against a paid invoice waits for a later invoice before it is applied | Credits applied with a reference | Applied later without a reference | Unknown |

The second row explains a common false fail: a credit that looks unrelated to the complaint because it was applied weeks later to the next bill.

## The two-entity test

Ask the controller one safe question: how many legal entities bill customers, and does anyone keep a list mapping each customer to each billing entity? Then read the answer.

| Answer | What it means for the trail | Mark for check 5 |
|---|---|---|
| One entity bills everyone | Decision and cost sit in one ledger | Pass |
| Several entities, with a shared customer ID | Cost can be reunited with the decision | Pass |
| Several entities, with a spreadsheet map | Joinable, but by a manual list | Partial |
| Several entities, no map | Credits and the invoices they offset may never meet | Fail |

The answer tells SourceX whether a decision and its cost can be put back together. The [missing-context comparison](/guides/complaint-to-retention-decision-missing-context) shows what the split looks like in one case.

## A scored example (Illustrative)

A fictional 300-person facilities services group with a U.S. operating company and a Canadian subsidiary, answered by the customer operations lead and the controller.

| Check | Mark | Note |
|---|---|---|
| 1. Identifier | Pass | Email domain shared across all three systems |
| 2. Timestamp | Pass | Retention offer property on company records since 2021 |
| 3. Version | Partial | Some long-running accounts changed many times |
| 4. Outcome link | Pass | Credit notes carry a deal reference, consistently since 2022 |
| 5. Entity | Partial | Two Xero organizations; controller keeps a spreadsheet map |

Three passes, two partials. The description that follows is honest and specific: decisions and credits join from 2022, with the entity link depending on a finance spreadsheet. The [metadata packet](/resources/complaint-to-retention-decision-metadata-packet) records the same facts as fields.

## Before you introduce

The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact: the CEO, with authority over every entity in the scorecard. 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.

Unknown until SourceX reviews it: what customer contracts allow, what must be removed, and whether a buyer wants the set. If an [ERP replacement](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) is planned with a documented date, note it. Related reading: [former employee complaints and company data](/guides/former-employee-complaint-company-data) and [complaint handling records](/data-types/complaint-handling-records).

## 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 scorecard gives you an accurate picture and an officer over every billing entity will take the call, [register as a partner](/register), check [who qualifies](/who-qualifies) and read the [terms](/terms) before introducing the company.

## Sources

- https://support.freshdesk.com/support/solutions/articles/225158-how-do-i-export-my-tickets-from-freshdesk-
- https://knowledge.hubspot.com/records/view-record-property-history
- https://knowledge.hubspot.com/properties/export-property-history
- https://www.xero.com/us/about/common-questions/
- https://central.xero.com/s/article/Common-scenarios-for-credit-notes-US
- https://refer.sourcex.si/terms
