Complaint-to-retention-decision completeness scorecard: five gap checks and a two-entity test, scored pass, partial or fail

Short answer

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.

Visual briefFull-size diagram
Five gap checks (identifier, timestamp, version, outcome, entity) tick one by one beside a horizontal completeness bar that fills to three passes and two partials, with the entity check marked partial.
Illustrative score for a fictional services group: three passes, two partials, the entity check the weakest.

This scorecard supports the complaint-to-retention-decision guide. 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

CheckHow it shows up when it failsHow to check it at metadata levelPassPartialFail
1. IdentifierThe customer is named differently in each systemAsk whether a shared customer ID or email domain links Freshdesk, HubSpot and XeroShared ID or domain in all threeMatches in two systems onlyMatched by reading names
2. TimestampRetention decision sits in a free-text noteAsk whether the decision is captured in a dated CRM propertyDated property since early in the periodProperty added recentlyNotes only
3. VersionProperty overwritten many times; early values gone from exportAsk how often retention properties change per account and how long accounts runFew changes per accountLong-running accounts with many changesHistory unknown
4. Outcome linkCredit note does not mention the case or dealAsk whether credit notes carry a ticket or deal referenceReference field used consistentlyUsed for some credits onlyNo reference
5. EntityCustomer billed by two organizationsAsk how many legal entities bill customers and whether a cross-entity customer list existsOne entity, or a maintained cross-entity IDSpreadsheet map kept by financeNo 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 checkWhy it mattersPassPartialFail
Conversation depthFreshdesk's ticket list export leaves out the full conversation and archived ticketsConversations pulled, archived includedConversations for recent years onlyTicket list only
Credit timingIn Xero, a credit against a paid invoice waits for a later invoice before it is appliedCredits applied with a referenceApplied later without a referenceUnknown

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.

AnswerWhat it means for the trailMark for check 5
One entity bills everyoneDecision and cost sit in one ledgerPass
Several entities, with a shared customer IDCost can be reunited with the decisionPass
Several entities, with a spreadsheet mapJoinable, but by a manual listPartial
Several entities, no mapCredits and the invoices they offset may never meetFail

The answer tells SourceX whether a decision and its cost can be put back together. The missing-context comparison 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.

CheckMarkNote
1. IdentifierPassEmail domain shared across all three systems
2. TimestampPassRetention offer property on company records since 2021
3. VersionPartialSome long-running accounts changed many times
4. Outcome linkPassCredit notes carry a deal reference, consistently since 2022
5. EntityPartialTwo 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 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 is planned with a documented date, note it. Related reading: former employee complaints and company data and 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, check who qualifies and read the terms before introducing the company.

  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

What score is good enough to introduce a company?

There is no threshold. The scorecard makes the description accurate; SourceX's review decides fit. A company with two partials and an honest note about them is a better introduction than one described as complete without checking.

Why is the entity check scored separately from identifiers?

Because it fails in a different way. Identifiers can match perfectly inside one set of books and still break when the customer is billed by two legal entities, each with its own Xero organization.

Can a fail be fixed before the introduction?

Sometimes, but that is the company's choice and not the partner's job. Record the result as it stands and let the company decide what, if anything, to change.

Sources

  1. support.freshdesk.com/support/solutions/articles/225158-how-do-i-e…
  2. knowledge.hubspot.com/records/view-record-property-history
  3. knowledge.hubspot.com/properties/export-property-history
  4. xero.com/us/about/common-questions
  5. central.xero.com/s/article/Common-scenarios-for-credit-notes-US
  6. refer.sourcex.si/terms

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