YOUR INFORMATION

Understand work in context

You are an engineer on the iOS team and your PM just assigned a high-priority issue to you. Customer Requests gives you all the context to understand what you need to build.

1.The issue description is a little vague, so you scroll down to the Customer Requests section to get more context.

2.Reading through the full customer feedback is really helpful because it comes directly from the user and describes real use cases and pain points.

3.With this context, you go ahead and build the feature. Sales and support automatically get notified once the issue gets marked as done.

Build stronger relationships

You are a customer success manager and your largest enterprise client just shared an important feature request in your shared Slack channel.

1.With the Linear Asks integration, you file a new customer request directly from Slack.

2.The product team reviews every ask that comes into their Triage inbox, so you have full confidence that the product team will see it.

3.Once the feature request has shipped, you and your customer will automatically get notified in the original Slack thread.

Make better product decisions

You are the Head of Product and planning your roadmap for the upcoming quarter. Instead of relying on just your intuition, you can now leverage Customer Requests to make a more informed decision about what your team should work on.

1.You create a custom project view that narrows down your backlog to a list of feature ideas that have been requested by your most important customers

2.You notice a project on the list that has been marked as important by top customers and has significant revenue impact.

3.You open the project to see the customer requests in full context: The missing feature is a really painful problem for these users, enough that one of the accounts is considering churning. You confidently prioritize the project and add to your Q2 roadmap.