Use Customer Requests in Linear
Attach customer feedback to the relevant issue or project while retaining its source. A request is evidence of demand, not an automatic commitment to implement it.
Step-by-step guide
Check access and scope
An administrator must enable Customer Requests. Decide who owns customer records and what information is appropriate to store.
Enable Customer Requests
Confirm Customer Requests is enabled in workspace settings. The documented control is Workspace Settings > Customer requests; an administrator enables it before collaborators add requests.
Find the customer
Find or create the correct customer record without duplicating it.
- Worked example: Three accounts report invite expiration confusion. Link each source to the same underlying improvement, but keep a request for administrator-controlled expiry separate if it changes product scope.
Attach feedback to work
Attach the request to an existing issue or project when the need already exists.
Preserve source context
Preserve source context and describe the outcome the customer needs.
Review demand with colleagues
Review related requests with customer-facing colleagues before prioritizing.
Verify the result
The customer record and linked product work provide a traceable path back to the feedback source.
Common mistakes
Avoid the main failure mode
Counting repeated messages from one account as independent market demand exaggerates the signal. Inspect customer identity and the actual request.
Check the handoff edge case
Treating a request link as a delivery promise creates avoidable customer expectations. Communicate prioritization separately from evidence capture.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.