Ji4Linear Customer Requests, explained
How Customer Requests tracks feedback and demand in Linear, which plans include it, and what handles the customer conversation itself.
Last updated: 19 July 2026
On this page
Customer Requests is Linear's way of linking feedback to the issues and projects it's actually about, so a decision to build something is grounded in who asked for it, not just a gut feeling about what matters.
What Customer Requests is
At its core, Customer Requests connects a piece of feedback (a feature ask, a complaint, a "when will this ship") to the specific issue or project it's about. Over time that builds a record of who wants what, so prioritization can be argued from demand rather than from whoever shouted loudest in a meeting.
How it works
Customers are first-class objects in Linear, not just tags: each one gets a unique domain, a name, and attributes like revenue, tier, or size. A customer's page shows every request they've made across every issue and project. Individual requests quote the original message and link back to where it came from, so nobody has to guess what was actually said.
A handful of features turn that record into something usable day to day:
- A mark-as-important flag, for separating a critical need from a nice-to-have.
- Custom views, for example every issue with 20 or more requests from Enterprise-tier customers.
- Notifications when a new request comes in on something you're tracking.
- CSV export and a GraphQL API, for reporting or wiring requests into other tools.
Where requests come from
Requests arrive automatically from Intercom, Zendesk, Front, Salesforce, Slack, and Asks integrations, or get added by hand with a quick Ctrl R. Attribute syncing from an external source runs in real time for Intercom and roughly every 12 hours for the others.
Which Linear plans include Customer Requests
Customer Requests itself is available on every plan, including Free. What's gated is where the requests come from automatically: creating them from Intercom, Zendesk, or Front requires Business or above, and Salesforce requires Enterprise. Adding requests manually works on any plan.
Where Customer Requests stops
Customer Requests tracks demand, it is not a conversation tool. There's no inbox, no reply workflow of its own, no SLAs, and no surface where the customer can see status. It answers "who wants this and how much does it matter," a product-prioritization question, not "how do we talk to this customer and keep them informed," a support one.
Where Ji4 fits
Customer Requests presupposes a conversation already happened somewhere: an Intercom thread, a Zendesk ticket, an email. Ji4 is that conversation layer. A customer's email becomes the Linear issue directly, the thread stays synced in both directions, and a customer portal shows the customer live status as the work ships, exactly the kind of signal Customer Requests aggregates.
See the full Linear integration for how the two-way sync between a customer's inbox and a Linear issue works end to end.
Related reading
Linear Customer Requests, explained FAQ
Simple answers about plans, billing, and your free trial.
Which Linear plans include Customer Requests?
The feature itself is on every plan, including Free. Creating requests automatically from Intercom, Zendesk, or Front requires Business or above; from Salesforce requires Enterprise. Adding a request manually works on any plan.
Does Customer Requests replace a help desk?
No. It tracks who wants what and how much it matters; it has no inbox, no reply workflow, and no SLAs of its own.
What's the difference between Customer Requests and Linear Asks?
Customer Requests links feedback to issues that may already exist and tracks demand; Asks turns a new request into an issue in the first place. See the guide to Linear Asks for the full breakdown.
Can customers see their own requests in Linear?
No, Customer Requests is an internal, product-facing view. For customers to see live status themselves, that's what a customer portal is for.
How do you add a customer request in Linear?
The fastest manual way is the keyboard shortcut Ctrl R on an existing issue, which lets you attach a new request, quoting the original message and linking back to where it came from. Adding a request manually works on every Linear plan, including Free. Automatic creation from a connected tool like Intercom, Zendesk, or Front is a separate, plan-gated path rather than something you trigger by hand.
Which integrations create customer requests automatically?
Requests arrive automatically from Intercom, Zendesk, Front, Salesforce, and Slack, or from Linear's own Asks. Attribute syncing runs in real time for Intercom and roughly every 12 hours for the others. Automatic creation from Intercom, Zendesk, or Front requires a Business plan or above, and Salesforce requires Enterprise; adding a request by hand works on any plan regardless of these gates.
Bring support into the tools
engineering already lives in
Start a 14-day trial in minutes. No card, no sales call, cancel anytime.