# Custom Ask fields before triage routing at scale

> Add structured Ask fields before automating triage so Slack and inbox intake can scale without somebody decoding every first message by hand.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/custom-ask-fields-before-triage-routing-at-scale/
- Source: [linear.app](https://linear.app/docs/triage?tabs=36dbc0f97e0d)
- GrowthDex source hub: [Linear Docs](/sources/linear-docs-linear-app/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: low
- Channels: Slack, Product, Operations
- Stages: triage, automation, ops, intake quality


## Why this can grow

Routing rules get brittle when they are forced to infer everything from unstructured prose. Custom intake fields give the team a cleaner signal to route on, which means requests reach the right queue faster and less context is lost in the shuffle. It is one of those dull operational moves that quietly decides whether a request system becomes trusted or ignored.

## 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 custom ask fields before triage routing at scale can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Slack 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 Triage docs recommend combining triage routing with custom Asks fields to create a scalable system for intaking issues from Slack.

## 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, 1 shared stage
- [Priority required before triage exit](/growth-ideas/priority-required-before-triage-exit/) - same source, 2 shared channels, 1 shared stage
- [Snoozed triage that returns on new activity](/growth-ideas/snoozed-triage-returns-on-new-activity/) - same source, 2 shared channels, 1 shared stage
- [Monorepo path filters for customer-facing release lanes](/growth-ideas/monorepo-path-filters-for-customer-facing-release-lanes/) - same source, 2 shared channels

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