# Churned-account request alert view with Slack notifications

> Subscribe the team to a customer-request view for churned accounts so important comeback signals show up fast instead of hiding in a backlog.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/churned-account-request-alert-view-with-slack-notifications/
- Source: [linear.app](https://linear.app/docs/customer-requests)
- GrowthDex source hub: [Linear Docs](/sources/linear-docs-linear-app/)
- Last checked: 2026-05-26
- Rarity: uncommon
- Budget: free
- Channels: Slack, Retention, Product
- Stages: retention, win-back, customer evidence, notifications
- Key metric: Alert on Customer status includes Churned and order the view by customer revenue

## Why this can grow

Churn feedback is easy to respect in theory and easy to bury in practice. A dedicated alert view gives the team a standing place to watch what former customers are still asking for, especially when those accounts carry meaningful revenue. That can turn reactivation opportunities into visible work instead of scattered notes across support threads and renewal calls.

## 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. 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 churned-account request alert view with slack notifications can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Slack and Retention 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 recommend creating a custom view where Customer status includes Churned, ordering issues by customer revenue, and sending notifications to Slack for visibility.

## Adjacent tactics in the same lane

- [Customer page subscription for request lifecycle signals](/growth-ideas/customer-page-subscription-for-request-lifecycle-signals/) - same source, 2 shared channels, 2 shared stages
- [Shared Slack channel linked to the customer record](/growth-ideas/shared-slack-channel-linked-to-the-customer-record/) - same source, 2 shared channels
- [Enterprise-tier request-threshold view for roadmap planning](/growth-ideas/enterprise-tier-request-threshold-view-for-roadmap-planning/) - same source, 1 shared channel, 1 shared stage
- [Excluded internal domain list for clean customer views](/growth-ideas/excluded-internal-domain-list-for-clean-customer-views/) - same source, 1 shared channel, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [Feedback only helps when the customer stays attached](/blog/feedback-only-helps-when-the-customer-stays-attached/) - support-led growth, product strategy, switcher intent

## Advisory

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