Quoted original request evidence on linked issues
Keep the original customer message, source link, sender name, and timestamp on the linked issue so the request does not get cleaned into something nobody actually said.
Why this can grow a startup
A feature request gets weaker each time it is paraphrased. Keeping the original quote and source on the issue preserves the actual language, account context, and moment of urgency. That makes prioritization sharper, gives support and success something concrete to point to, and reduces the common drift where the backlog starts describing a different problem from the one the customer raised.
Company example
Linear's Customer Requests docs say requests created from integrations include the original user message, a link to the source conversation, the user's name, and the timestamp.
Source and metric
Source: Linear Docs · Browse Linear Docs tactics
Each linked request can carry the original message, source, sender, and timestamp
Source discovered: May 27, 2026
When to use it
Use this when Support, Product, Customer Success is relevant to customer evidence, voice of customer, roadmap trust and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Linear Docs and identify what is directly supported.
- Choose one channel context: Support, Product, Customer Success.
- Define the test around Each linked request can carry the original message, source, sender, and timestamp.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.