# Manual request capture from meetings and offline feedback

> Turn a sales call, in-person meeting, or stray message into a structured request immediately, instead of waiting for the evidence to be rewritten later from memory.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/manual-request-capture-from-meetings-and-offline-feedback/
- 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: Sales, Product, Support
- Stages: feedback capture, ops hygiene, customer research, support-led growth
- Key metric: Manual request capture is available from issues, projects, and customer pages, including Ctrl+R

## Why this can grow

Some of the best product evidence never arrives through a clean integration. It shows up on calls, in workshops, or in Slack threads that never get formalized. A quick manual capture path keeps those requests from evaporating. The result is a backlog that reflects the full demand picture, not just the channels with the nicest plumbing.

## 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 manual request capture from meetings and offline feedback can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Sales 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 teams can add requests manually from an issue, project, or customer page, including with the Ctrl+R shortcut, when the feedback came from a meeting or another channel without an integration.

## Adjacent tactics in the same lane

- [Triage responsibility rotation linked to on-call schedules](/growth-ideas/triage-responsibility-rotation-linked-to-on-call-schedules/) - same source, 2 shared channels, 2 shared stages
- [Dedicated feedback team for customer request intake](/growth-ideas/dedicated-feedback-team-for-customer-request-intake/) - same source, 2 shared channels, 1 shared stage
- [Customer page sorted by important and in-progress work](/growth-ideas/customer-page-sorted-by-important-and-in-progress-work/) - same source, 2 shared channels, 1 shared stage
- [Priority required before triage exit](/growth-ideas/priority-required-before-triage-exit/) - 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.