Customer Requests
Bring the voice of the customer into product development.
Overview
Customer Requests allow you to add detailed user feedback and customer attributes to Linear to better align product work with real user needs:
- Link customer requests to specific issues in Linear to make feedback accessible to your product team
- See customer pages displaying all requests made by specific customers along with attributes like revenue, size, and tier
- View and filter issues by customer name, count, stage, tier revenue, and size to identify high impact product work
What this video over to see how Customer Requests works:
Configure
Admins can enable Customer Requests in Workspace Settings > Customer requests. Once enabled, anyone in your workspace can view customer pages, create and update customers, and create customer requests in Linear or from a supported integration.
Requests are automatically created when an issue is created from an Intercom, Zendesk, Front, Asks, or Email. Requests can also be created manually and are viewable in issues and the customer's page.
From settings, add customizations. Choose a team to receive new issues created from a request by default. (we recommend selecting a team exclusively used to track feedback). You can also customize revenue units and tiers for different plans or products you offer. Revenue and Tier fields will be automatically populated if you use the Intercom integration, or can be filled when creating customers manually.
Customers
A Customer in Linear represents an organization using your product. Customers have a unique domain, name, logo, and attributes which can be viewed on their page.
Customer pages
Customer pages show all issues that have been associated with the customer through customer requests. You can group and order this list of issues to see what issues have been marked as important or what issues are in progress. Click on individual issues to open and view the request in full detail.
For customers created through Intercom or manually, you'll also see attributes like the customer's revenue, stage, tier, and size on the customer page. Individual customer pages can be favorited so that they're easy to access from the sidebar.
Open Customer pages
- Use O then Q, then search for the customer's name
- Open the full customer list with G then Q, then search to narrow down results
- Search for the customer in the Cmd/Ctrl + K menu
Create Customers
In most cases, customers will be created automatically through an integration at the same time their first request is created. Linear will use the customer's email domain to correctly map the request.
If your organization does not use these integrations, you can create Customers manually instead. To do so, open the command menu with CMD + K
, then type customer
, then Return
Customer requests
Customer requests link user feedback to specific issues in Linear.
Create requests
A customer request is created automatically whenever you create or link to an issue from a supported integration. The request will appear both on the issue and the associated customer's page.
When made from an integration, the customer request will quote the original message from the user. This request can be edited in Linear to add images, videos, or extra context. Requests also include a link to the source (e.g. Intercom conversation), name of the user associated with the request, and timestamp.
Requests can be created manually in Linear using the icon underneath an issue description, or the keyboard shortcut Ctrl
R
(macOS)/ Ctrl
Alt
R
(Windows). This is useful when a request comes in through a channel not necessarily associated with an integration, like if you have Linear open during an in-person meeting.
Remember to configure a default team in settings for customer requests, so that issues are created in that team when requests are created from individual customer pages.
Integrations
The following integrations can create customer requests:
Requests are created when you create new issues or link to an existing issue from the Intercom integration. Customer attributes such as size and revenue will be synced with and managed from Intercom.
Requests are created when you create issues or link to an existing issue from Zendesk or Front conversations.
Requests are created when issues are created via email. Find your team's unique email address in Team settings > settings.
We exclude certain common domains from creating Customers (e.g. @gmail.com) but you may also want to exclude additional emails in settings under "Ignore sources." For example, we exclude "@linear.app" so that "Linear" does not appear as a customer when we create issues by forwarding an email.
Whenever an Ask is created, a customer request will be associated with the issue and link the specific feedback and customer to the Ask.
The customer association for Asks follows the email of the person who sent the first message in the thread, not the person who created the Ask.
To ensure proper customer attribution despite varying Slack privacy settings in shared channels, we recommend directly linking any shared Slack channels to the customer page (select the three-dot menu, then link to Slack channel.) This way, all Asks created in that channel will automatically be associated with the customer.
When creating an issue from the Slack integration, optionally select "Customer" to associate a customer request with the issue you are creating. Otherwise, the message will be brought into Linear without being associated with a customer.
Requests and Customers can be created with customerNeedCreate and customerCreate respectively in our GraphQL API.
However, using our API to import customer data from a warehouse—commonly done through an rETL pipeline—can be challenging, as GraphQL is not optimized for bulk data transfers, and Linear does not currently offer a REST API. We plan to build more tooling in the future to simplify this process.
Mark as important
Requests can be flagged as important to specific customers. For instance, an issue may have requests from five different customers but be marked as important by only one of those customers. This binary indicator, shown as a triangle, lets customer-facing teams separate requests that represent a critical need from those expressing a nice-to-have feature.
Build customer views
All customer data brought into Linear can be used to create custom views to surface the impact of your work on your customers. For example, create a view of issues with requests from Enterprise customers ("Tier" property from Intercom), where each issue has at least 20 requests. Ordering this view by customer count surfaces the most highly requested issues to the top. Triangle icons indicating requests marked important surface urgent needs. Consider consulting this view when planning upcoming cycles to ensure what you ship aligns with the needs of the users.
Notifications
You'll receive Inbox notifications automatically when new requests are added to issues you subscribe to so you're always in the loop. Optionally, configure additional notification styles for new requests here.
Subscribing to custom views is the best option for more targeted alerts. For example, you might wish to stay aware of issues commonly raised by customers who churn. To track that, create a custom view defined by Customer stage includes Churned, and ordering the issues by customer revenue. Click the bell icon to be alerted when a new issue is added to the view, or configure notifications to a Slack channel for greater visibility.
FAQ
Customer Requests is available on all currently offered plans: (Free, Basic, Business, and Enterprise.) You'll only be able to create requests from integrations available on your plan.
Create requests | Free | Business | Enterprise |
---|---|---|---|
Manually | ✔ | ✔ | ✔ |
By email | ✔ | ✔ | ✔ |
From Slack | ✔ | ✔ | ✔ |
From Asks | ✔ | ✔ | |
From Intercom, Zendesk, and Front | ✔ | ✔ | |
From Salesforce Service Cloud | Coming soon |
The following actions are available through our GraphQL API:
- Create/Edit/Delete customers
- Create/Edit/Delete customer request
- Create/Edit/Delete customer tiers
- Create/Edit/Delete customer statuses
- Query and filter customers
- Query and filter requests by issue/projects/priority/customer
Linear will prevent duplicate customers from being created in most cases. If you notice a duplicate instance, go to the customer page that you want to merge and select the Merge with option from the dropdown menu.
In Settings > Customer requests, exclude specific email addresses or domains to prevent them from being associated with a customer or creating a customer request.
For example, add a domain to Exclude from becoming customer requests to prevent messages like bot emails from being made into requests.
Use Exclude from customer associations to prevent your own company from displaying as a customer. Internally, we've excluded linear.app
here to prevent Linear
from displaying as a customer when we create issues via integrations.