# Complaint-to-product-change record chain | SourceX

Canonical: https://refer.sourcex.si/guides/complaint-to-product-change-record-linkage
Last updated: 2026-11-04

A company connects complaint-to-product-change records by keeping a key at every hop: the conversation carries a link to the product issue, the issue names the policy page it changes, the policy page has dated versions, and the help article has its own version history that can be lined up against the policy edit. Five hops, five keys. Where a hop has no key, the chain survives only as a guess from dates and wording.

This record chain is part of the [complaint-to-product-change guide](/guides/chain-complaint-to-product-change), which covers the metadata packet a partner collects. Here the job is narrower: follow one case from first complaint to corrected answer and name the key at each step.

## The chain, hop by hop

Illustrative. A fictional 300-person retailer of home fitness equipment hears from customers that returns fail for oversized items. The case runs through three tools: Intercom for conversations and help articles, Linear for product issues, Notion for internal policy pages.

| Step | Record | Key that points to the next step | System |
|---|---|---|---|
| 1. Complaint | 212 conversations about oversized returns, March 14 to April 20 | Linked Linear issue on each conversation | Intercom |
| 2. Issue | One issue grouping the 212 conversations | Conversation links on the issue | Linear |
| 3. Decision | April 3 comment: offer pickup returns for oversized items | Issue references the policy page by URL | Linear |
| 4. Fix shipped | April 28: issue completed, internal note posted to linked conversations | Issue status change and its date | Linear and Intercom |
| 5. Policy update | May 2: returns policy page rewritten to the pickup rule | Page version dated May 2 | Notion |
| 6. Public answer | May 20: help article rewritten to describe pickup returns | Article version dated May 20 | Intercom |

Read top to bottom, every step except one carries a pointer. Steps 1 and 2 share a link that runs both ways. Linear documents that its Intercom integration attaches conversations to issues as links, allows several conversations per issue and several issues per conversation, and posts an internal note back to the conversation when the issue is completed or canceled, reopening it by default. That is why step 4 lands in both tools.

Step 3 to step 5 holds only if someone pasted the policy page URL into the issue. Step 5 to step 6 has no pointer at all: the article was rewritten 18 days after the policy, and nothing in either record names the other.

## Keys by type: what each one proves

Not every key is equally strong. Sort them before you describe the chain to anyone.

| Key type | Example in this chain | Strength | What it proves |
|---|---|---|---|
| System link | Conversation-to-issue link from the integration | Strong | These complaints were grouped into this issue by someone at the time |
| Typed reference | Policy page URL pasted into the issue | Medium | The person deciding knew which page the decision affected |
| Version timestamp | Notion page version, Intercom article version | Medium | What the text said on a given date, if history still covers that date |
| Status date | Issue completed on April 28 | Medium | When the fix shipped, not when it was decided |
| Date and topic match | Article edit on May 20 matched to policy edit on May 2 | Weak | Only that the two edits are plausibly related |

A chain made of system links and version timestamps can be followed by anyone. A chain held together by date matches needs the people who were there.

## Where the chain snaps

Four places account for most breaks, and each has a recognizable signature in the metadata.

**Before the integration.** Conversations from before the company connected Linear to Intercom have no issue link. The signature: a clean cutover date, after which most product-feedback conversations carry links and before which almost none do. Ask when the integration was switched on.

**Decisions outside the issue tracker.** If the April 3 decision was taken in a meeting and only the completion was logged, step 3 has no record and step 4's date stands in for it. The signature: issues that go from open to completed with no comments.

**Policy history that has expired.** Notion keeps page history for a period set by the plan: 7 days on Free, 30 on Plus, 90 on Business and unlimited on Enterprise. On a Plus plan, the May 2 version of the policy page exists in history for about a month; a year later only the current text remains. The signature: policy pages whose history starts recently even though the page is old.

**The article that never references the policy.** Intercom keeps a version history for public articles showing which teammate changed what, and previous versions do not expire, so the May 20 edit is dated. What is missing is the pointer from the policy change to the article. This is the weak link, and it matters most: in the 18 days between May 2 and May 20, any agent who sent the old article gave an answer that was out of date, as the [missing-context comparison](/guides/complaint-to-product-change-missing-context) shows step by step.

## Repairing the weak link

The repair is a small habit, not a new system. Each fix below adds a key that a reviewer can follow later.

| Weak link | Repair | Key it creates |
|---|---|---|
| Policy page to help article | Link the article URL on the policy page, or note the policy version in the article edit | Typed reference both ways |
| Decision to issue | Record the decision as a dated issue comment | Decision timestamp |
| Policy history expiry | Export the policy page when it changes, or keep a dated changelog page | Version that outlives the plan's history window |
| Pre-integration conversations | Tag historic product-feedback conversations by topic | Weak but searchable grouping |

For a referral, the point is not to fix anything. It is to know which hops already carry keys, from when, and who owns each one. The [completeness checklist](/resources/complaint-to-product-change-completeness-checklist) turns those questions into a pass, partial or fail score.

## Who owns each hop, and what stays unknown

Support or CX leads own steps 1 and 6, the head of product owns steps 2 to 4, and an operations or policy owner holds step 5. Any of them can describe their hop from admin views without opening a customer message. Authorizing a licensing discussion across all three takes the CEO, usually the owner in an owner-run company.

The company baseline: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. 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.

Partners stay at metadata level: which hops exist, the years covered, rough volumes and owners. They do not export, read or forward conversations. Unknown until SourceX reviews it: whether customer terms allow licensing, how messages would be de-identified, whether a buyer wants this chain, and how changes in law could affect a license, a topic covered in [AI data license change in law](/questions/ai-data-license-change-in-law). Single-system detail sits on the [Linear issue exports](/systems/linear-export-issues), [Intercom](/systems/intercom) and [Notion](/systems/notion) pages, and the record type on [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 your client can name the key at each hop and an executive over support and product will take a call, [register as a partner](/register), confirm [who qualifies](/who-qualifies) and read the [terms](/terms) before you introduce them.

## Sources

- https://linear.app/docs/intercom
- https://www.intercom.com/help/en/articles/9357931-create-and-manage-public-articles
- https://www.notion.com/help/duplicate-delete-and-restore-content
- https://refer.sourcex.si/terms
