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.
Source-backed 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-reported evidence
Source: Linear Docs · Browse Linear Docs tactics
Each linked request can carry the original message, source, sender, and timestamp
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Support and Product, using evidence from Linear Docs as context—not as a promised result.
- Record a baseline for: Users who resolve the issue and complete the next useful action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from Linear Docs
Explore related GrowthDex examples and evidence connected to Linear Docs.
Open Linear Docs source hub