This scorecard supports the complaint-to-product-change guide. Use it before telling anyone a company's records are a fit.
How to score
Each check gets one of three marks. Pass means the record exists, is dated and covers most of the period the company would discuss. Partial means it exists for part of the period or only for some records. Fail means it is missing, or nobody can say. Record who gave each answer and how they know. Do not mark a pass because a feature exists in the product; ask whether the company used it, and from when.
A completed scorecard is a page of metadata. It holds systems, dates, counts and owners. It never holds customer names, message text or screenshots.
The six checks
| Check | What it tests | How to check it at metadata level | Pass | Partial | Fail |
|---|---|---|---|---|---|
| 1. Coverage | Conversations exist for the period | Ask the support lead which years the Intercom workspace covers and whether older tools were migrated | Three or more years in one workspace | Gaps, or older years in an unmigrated tool | Under a year, or unknown |
| 2. Conversation-to-issue links | Complaints point to product issues | Ask when the Linear integration was switched on and roughly what share of product-feedback conversations carry a link | Linked since early in the period | Linked only recently | No links |
| 3. Decision dates | Product decisions are recorded with dates | Ask whether decisions are written as dated issue comments or only in meetings | Decisions dated in the issue | Only completion dates | No record |
| 4. Policy versions | Internal policy pages keep history | Ask which Notion plan holds the policy pages and whether changed pages are exported | Enterprise history, or exported copies | Business or Plus history only | Free plan, no copies |
| 5. Outcomes | The effect of a change is recorded | Ask whether anyone tracked complaint volume on the topic after the fix | Tracked in a report or tag | Anecdotal only | Not tracked |
| 6. Article versions | Help articles keep dated history | Ask whether the help center is in Intercom and whether articles are edited in place | Article history kept | History kept for some collections | Articles replaced without history |
Three of these checks lean on documented product features. Linear's Intercom integration attaches conversations to issues as links, allows several conversations per issue, and posts an internal note to linked conversations when an issue is completed. Intercom keeps public article versions showing which teammate changed what, and the versions do not expire. Notion's page history is the one with a plan-dependent window: 7 days on Free, 30 on Plus, 90 on Business and unlimited on Enterprise. That is why check 4 has an export question.
The stale-article test
The checks score each record. This test scores the joins, and it is the one most likely to separate a strong trail from a weak one.
Ask the support lead for one recent policy change and three dates: when the decision was made, when the internal policy page changed and when the help article changed. Then read the gaps.
| Result | What it shows | Mark |
|---|---|---|
| All three dates found, article edit within a few days of the policy edit | Process is tight and fully recorded | Pass |
| All three found, article edit weeks later | Process lag is recorded; every answer in that window cited a stale source | Pass for completeness, worth noting as a finding |
| Two of three found | One step lives in memory, not records | Partial |
| One or none found | The trail cannot be rebuilt | Fail |
The second row is not a failure. A company that can show its own lag across many policy changes holds a useful record of how decisions reach customers. In the Illustrative case on the record chain page, the policy changed on May 2 and the article on May 20, an 18-day window. The missing-context comparison shows what one reply sent inside such a window looks like with and without its context.
A filled scorecard (Illustrative)
A fictional 300-person retailer of home fitness equipment, answered by its CX lead and head of product in one call.
| Check | Mark | Note |
|---|---|---|
| 1. Coverage | Pass | Intercom since 2019, single workspace |
| 2. Conversation-to-issue links | Partial | Linear integration switched on in 2023 |
| 3. Decision dates | Pass | Decisions logged as dated issue comments since 2019 |
| 4. Policy versions | Partial | Notion Plus plan; no exports before last year |
| 5. Outcomes | Pass | Complaint tags reviewed monthly |
| 6. Article versions | Pass | Intercom help center, edited in place |
| Stale-article test | Pass | Three dates found; 18-day lag on the sampled change |
Four passes, two partials, and a documented lag. That is enough to describe the trail accurately: complete from 2023, thinner before, with the policy history as the weakest piece.
Before you introduce
Pair the scorecard with the fit check. 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, usually the owner in an owner-run company, rather than the CX lead. 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.
Tell the owner that SourceX funds any referral reward separately and never deducts it from the company's payout; the rewards page lists every condition. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Unknown until SourceX reviews it: whether customer terms allow licensing, how conversations would be de-identified, and whether a buyer wants the set. Related reading: former employee complaints and company data, complaint handling records and AI data license change in law.
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 shows a trail you can describe honestly and an executive will take the call, register as a partner, check who qualifies and read the terms before you introduce the company.