prioritized.
Customer Requests captures every voice — Slack, support tickets, sales calls, NPS verbatims, the in-product widget — then ranks the demand and links it to the engineering work that resolves it.
Customer Requests in short
A purpose-built object distinct from issues: requester, account, ARR weight, sentiment, and a freeform quote. Adapters cover Intercom, Zendesk, Front, Gong, HubSpot, Salesforce, and the in-product widget — every request deduplicated against a vector index.
A weighted scoring function combines account ARR, plan tier, recency, frequency, and explicit upvotes into a single rank. Weights are workspace-configurable, the formula is visible — no black box. Leaderboards update in realtime via Centrifugo.
Link a customer request to one or many engineering issues. The link is bidirectional, typed (requests, partially-resolves, out-of-scope), and exposed on both objects. When an issue closes, every linked request transitions and the requester gets notified.
Intercom conversations get a Planoda deeplink; Salesforce opportunities show the open feature gap; HubSpot deals show requested-but-not-shipped. Sync runs on a Trigger.dev queue with idempotency keys, retries, and dead-letter routing.
A weekly digest emailed to PMs and account teams, ranked by ARR-weighted demand growth and resolution gap. Each digest is a permalink with shareable filters — paste it into Notion, Slack, or the board deck and it stays live.
FAQ
How every customer voice is captured, ranked, and linked to the work that ships it.
Customer Requests · Business
ARR-weighted ranking, bi-directional sync, and visible formulas — no black box.