# Weekly CX on-call for off-platform feedback

> Rotate one person each week to watch off-platform feedback from social, community, and app-store surfaces so useful demand does not die outside the product queue.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/weekly-cx-on-call-for-off-platform-feedback/
- Source: [linear.app](https://linear.app/now/cx-in-linear)
- GrowthDex source hub: [Linear](/sources/linear-linear-app/)
- Last checked: 2026-05-27
- Rarity: rare
- Budget: free
- Channels: Communities, Support, Product
- Stages: support-led growth, voice-of-customer, operations, retention


## Why this can grow

A lot of product evidence never reaches the backlog because it shows up in places that are nobody's formal job. A weekly on-call owner fixes that with very little process. The team knows who is watching, the watcher knows the handoff path, and customers stop feeling like their best bug report only counted if it arrived through the official form.

## 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. I would treat this as earning the right to be in the room, not dropping a campaign into a room. In community-led growth, the first job is to notice what people already care about, then bring a useful proof, tool, teardown, or question that makes the conversation better. For retention, I would watch the second and third use, not just the first click. A tactic is real when it changes a habit. 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 weekly cx on-call for off-platform feedback can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Communities and Support 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 CX team runs a weekly on-call rotation where one person watches channels such as X, Reddit, app-store reviews, and the community Slack so relevant feedback can be turned into issues.

## Adjacent tactics in the same lane

- [Channel-specific notification queues for external feedback](/growth-ideas/channel-specific-notification-queues-for-external-feedback/) - same source, 2 shared channels, 2 shared stages
- [Minimum required fields for fast feedback filing](/growth-ideas/minimum-required-fields-for-fast-feedback-filing/) - same source, 2 shared channels, 2 shared stages
- [Enterprise-tier bug routing with auto-urgent SLA](/growth-ideas/enterprise-tier-bug-routing-with-auto-urgent-sla/) - same source, 2 shared channels, 2 shared stages
- [Bug-vs-feature-request template split at intake](/growth-ideas/bug-vs-feature-request-template-split-at-intake/) - 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 system should sort pain before the roadmap sees it](/blog/the-request-system-should-sort-pain-before-the-roadmap-sees-it/) - 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.