# Customer-adjustable request importance with added context

> Let customers raise or lower a request's importance and add fresh context after they submit it so feedback gets richer as urgency changes.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/customer-adjustable-request-importance-with-context/
- Source: [productlane.com](https://productlane.com/changelog/2025-03-31-portal-upgrades)
- GrowthDex source hub: [Productlane Changelog](/sources/productlane-changelog-productlane-com/)
- Last checked: 2026-05-26
- Rarity: rare
- Budget: low
- Channels: Product, Customer Success, Support
- Stages: feedback loop, prioritization, retention, support-led growth


## Why this can grow

A plain upvote freezes the signal too early. Real demand changes after rollout delays, new blockers, or internal deadlines. When customers can adjust importance and attach more detail later, the queue stays closer to current pain instead of original wording. That makes prioritization more trustworthy and gives customer-facing teams a better answer when an account asks whether the team still understands the request.

## 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 customer-adjustable request importance with added context can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Product and Customer Success channel.
3. Use the evidence from productlane.com 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

Productlane updated its portal so customers can adjust request importance and add more context on the request itself after feedback creates a Linear request.

## Adjacent tactics in the same lane

- [Request trend view separating weekly demand from spikes](/growth-ideas/request-trend-view-separating-weekly-demand-from-spikes/) - same source, 2 shared channels, 2 shared stages
- [Separate AI replies from the human support lane](/growth-ideas/separate-ai-replies-from-human-support-lane/) - same source, 2 shared channels, 2 shared stages
- [SLA trend review for response and resolution bottlenecks](/growth-ideas/sla-trend-review-for-response-and-resolution-bottlenecks/) - same source, 2 shared channels, 2 shared stages
- [Request page with the prior mail thread visible](/growth-ideas/request-page-with-prior-mail-thread-visible/) - same source, 3 shared channels, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The roadmap starts working when it answers back](/blog/the-roadmap-starts-working-when-it-answers-back/) - support-led growth, roadmap strategy, brand trust

## Advisory

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