The business task: from a reported issue to a changed policy
A customer reports that something is wrong. Support logs the exchange and, if it is a product problem, flags it for the product team. Product decides what to change and ships it. Operations then rewrites the internal rule so the rest of the company knows what changed, and support updates the public help content customers are sent. Five people touch the decision, and each of them writes in a different tool. For a software or subscription business, that sequence is how customer pain turns into roadmap priorities, refund rules and support scripts, which is exactly the kind of reasoning that rarely appears in public text.
In the setup this page uses, Intercom holds the reported issue and the help article, Linear holds the product decision, and Notion holds the internal policy page. Linear's documented Intercom integration links support conversations to product issues, many to many, and when a linked ticket is completed or canceled it posts an internal note back and reopens the thread by default. That is a recorded join between the complaint and the decision. The join from the decision to the policy page is usually a person remembering to paste a link.
What metadata can a referral partner collect about complaint-to-product-change without reading private content?
Counts, dates, object types, link fields, owners and unknowns: enough for a one-page packet, and nothing from inside a support thread, a ticket or a policy page. Ask for one line per system and fill it in during the call. A customer systems advisor usually has admin views that show most of it.
| Packet item | Support tool (reported issue) | Product tracker (product decision) | Wiki (policy update) |
|---|---|---|---|
| Objects | Conversations, tags, help articles | Issues, projects, comments | Policy and process pages |
| Period covered | Since the workspace started | Since the team adopted the tracker | Since the wiki was set up |
| Rough volume | Threads per month; share tagged as product feedback | Tickets per quarter with a linked thread | Number of customer-facing policy pages |
| Versioning | Article version history | Ticket history and status changes | Page history, limited by plan |
| Join | Linked ticket on the thread | Thread links on the ticket | Issue or decision link on the page, if any |
| Owner | Support or CX lead | Head of product | Operations or policy owner |
| Unknown until review | Whether old threads were exported before any migration | How decisions made in meetings were recorded | Which wiki plan, and so how much history survives |
The last row matters more than it looks. On a Plus plan, a policy page edited two years ago may only show its current text, so the evidence of what the policy said at the time of a complaint may have to come from somewhere else, such as an exported copy or the help article's own history. Ask, do not assume. For Notion specifics, see the Notion systems page; for Intercom, the Intercom page.
What breaks when the final answer uses an obsolete help article
The chain looks complete in every system and still gives the customer the wrong answer. The graphic on this page shows the pattern with Illustrative dates. Linear marks the fix shipped on April 28. The Notion policy page is updated on May 2. On May 10 a support agent answers a complaint by sending the Intercom help article, which still describes the old behavior. The article is only updated on May 20. For 18 days the decision and the public answer disagreed.
Nothing in that sequence is an error a single system would flag. The Linear issue is closed, the Notion page is current, and the May 10 conversation is resolved. The gap only shows when the three dates are read side by side, which is why the packet asks about versioning, not just volume.
Three metadata questions settle whether the company can reconstruct windows like this one:
| Question | Why it matters | Who usually knows |
|---|---|---|
| Do help articles keep version history, and since when? | Intercom keeps public article versions with the teammate who made each change, and previous versions do not expire, so the May 20 edit is dated. | Support or CX lead |
| How far back does policy page history go? | Notion page history depends on plan: 7 days on Free, 30 on Plus, 90 on Business, unlimited on Enterprise. | Operations or workspace admin |
| Do agents link the article they sent to the conversation? | Without it, the May 10 answer can only be matched by wording, not by article ID. | Support or CX lead |
If the answers are yes, limited and sometimes, say so. A partner does not need to count stale windows; SourceX's review does that under the company's own agreement. Describing whether they can be counted is enough.
Who can authorize the introduction
Complaints belong to support, decisions to product, policy to operations. The person who can authorize a licensing conversation across all three is the CEO, usually the owner in an owner-run company, often with the COO as sponsor. Product and CX leads are good sources of metadata, not signatories.
Before you introduce, check:
- 50+ full-time employees at peak, contractors excluded, and a documented operating history.
- The company owns its conversation, issue and policy records, and its customer terms do not rule out licensing.
- A decision-maker has agreed to a first call.
- 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.
Left for SourceX's review: how customer messages would be de-identified, which periods and product lines a buyer would value, what customer contracts allow and what the company would be paid. Partners do not receive or forward records at any stage. For how product decision records are assessed more broadly, read assessing product planning records, or browse the systems hub.
Go deeper on complaint-to-product-change records
- How Intercom, Linear and Notion records link end to end: a record-chain table of each step, its record, its key and its system.
- Complaint-to-product-change completeness checklist: a pass, partial or fail scorecard for judging whether the records are complete enough to discuss.
- What a single-system export of a complaint leaves out: one Illustrative case read before and after its surrounding context is added.
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 give you the three dates for a recent policy change and name an executive over support and product, register as a partner, confirm who qualifies and read the terms before making the introduction.