# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/quoted-original-request-evidence-on-linked-issues/
- Source: [linear.app](https://linear.app/docs/customer-requests)
- GrowthDex source hub: [Linear Docs](/sources/linear-docs-linear-app/)
- Last checked: 2026-05-27
- Rarity: rare
- Budget: free
- Channels: Support, Product, Customer Success
- Stages: customer evidence, voice of customer, roadmap trust, feedback loop
- Key metric: Each linked request can carry the original message, source, sender, and timestamp

## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where quoted original request evidence on linked issues can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Support and Product channel.
3. Use the evidence from linear.app to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [Dedicated feedback team for customer request intake](/growth-ideas/dedicated-feedback-team-for-customer-request-intake/) - same source, 3 shared channels, 1 shared stage
- [Customer email-domain auto-mapping for feedback identity](/growth-ideas/customer-email-domain-auto-mapping-for-feedback-identity/) - same source, 3 shared channels, 1 shared stage
- [Shared Slack channel linked to the customer record](/growth-ideas/shared-slack-channel-linked-to-the-customer-record/) - same source, 2 shared channels, 1 shared stage
- [Enterprise-tier request-threshold view for roadmap planning](/growth-ideas/enterprise-tier-request-threshold-view-for-roadmap-planning/) - same source, 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The request should stay attached to the customer](/blog/the-request-should-stay-attached-to-the-customer/) - support-led growth, product ops, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.