Feature request triage
Cluster the week's feature requests, dedupe them, and route the top themes to the PM lead with linked support volume.
Eluu — feature-request-triage
Shown in preview 
Runtime ~4 min per run
Tokens ~14K per run
Owner a PM colleague
Works with
Pick whichever tool your team already uses.
- Support Intercom
Zendesk 
Help Scout - Docs Notion
Google Docs 
Confluence - PM / Tickets Linear
Jira 
Asana
What it does
Feature requests come in every day across support tickets, sales calls, and customer threads — and most of them never reach the PM team in any structured way. This recipe pulls the week’s requests, clusters by theme, dedupes against the existing roadmap, and routes the top themes (weighted by ARR) to the PM lead.
How it works
- Pull requests. Conversations tagged feature-request from the last 7 days are pulled with their associated account size and ARR.
- Cluster + dedupe. Requests are clustered by theme; existing Linear FEAT tickets are checked for overlap; themes are scored by mentions × ARR; already-on-roadmap themes are dropped.
- Route. Per-theme detail with verbatim quotes goes into a Notion digest. Top 3 themes are routed to Linear (new ticket or comment on existing). PM lead is DM’d.
Setup
- Connect a support tool (Intercom, Zendesk, or Help Scout).
- Connect a PM/tickets tool (Linear, Jira, or Asana).
- Connect a docs destination (Notion, Google Docs, or Confluence).
Variations
- Run daily for high-volume products instead of weekly.
- Add an enterprise-only filter that surfaces themes from your top accounts.
- Auto-update Linear ticket priority based on new request volume.
