Tracking Feature Requests in Intercom

If you are using Intercom as your support tool or to communicate with prospects you’re almost certainly getting messages that include valuable customer feedback and product feature requests.

Those messages are pure gold.

They can help you build a better product, be more customer focused and be seen as more responsive to your customers. You definitely don’t want to lose that valuable feedback. You want a well managed process that turns that feedback into results for customers.

Qualities of a Good Intercom Feature Request Tracking Process

What does a good Intercom feature request tracking system look like? A good system has four main attributes.

Low Friction

If you want to make sure that every feature request that lands in your Intercom inbox actually gets collected then the process better be easy. Ideally you don’t want your support reps to leave Intercom to track requests because that adds friction. If you ask people to jump through a bunch of hoops to collect feedback they are going to be less likely to do it.

Highlights Trends

If you dump every feature request in a generic “feedback bucket” it’s going to be painful to use. No one wants to read through a thousand uncategorized feature requests.

Instead you want a system that organizes feature requests into logical buckets, groups related feature requests together and makes it easy to spot trends.

Supports Segmentation

Not all feature requests are created equal and you want your process to capture that.

One of the pluses of Intercom is that it makes it easy to send user and company properties to Intercom.

For example, you can send properties like monthly spend (MRR) or what plan the company is paying for to Intercom and then tie that information back to the feature requests they have submitted.

Imagine you have two feature requests: A and B. If 100 people have asked for feature A and 50 people have asked for feature B you might be tempted to think feature A is more important.

But what if I told you that all 100 people who asked for feature A were on your free plan and all 50 people that asked for feature B were on your enterprise plan.

Would you still think feature A is more important?

That's why having a feature request tracking system that can segment feature requests is important.

Closes the Loop

You’ve collected a bunch of feature requests from customers. You’ve used those requests as evidence to make a product change. The feature has actually been added.

Yay you! 🥳

But if the customers that asked for the feature aren’t aware that it’s been added, or if you haven’t told them that their feature request was heard and influenced product direction then you’ve missed out on a big opportunity. Customers love feeling heard.

By individually messaging the customers that provided feedback after you’ve shipped the feature you make them feel important and increase their affinity to your product and company.

It’s a simple thing but it goes a long way to reducing churn. Intercom makes it easy to message users and you want your feedback process to tie into that.

Three Different Options for Setting up an Intercom Feature Request Tracking System

There are three main options for setting up an Intercom feature request tracking system:

  1. Use Intercom tagging and reports.

  2. Use a general purpose tool like Google Sheets or Trello.

  3. Use a purpose built feedback management system with a deep Intercom integration like Savio.

Option 1: Using Intercom Tagging and Reports

With this approach you tag all feature requests as they come in with a set of tags you maintain in Intercom e.g. “Feature Request: A”, “Feature Request: B” etc. Then you use Inbox search and export to CSV process to work with the data.


  • No additional tools.

  • Low friction for support reps. Just tag conversations.


  • Hard to see trends. You have to either build a search for each tag and walk the list of conversations manually or export all of your conversations to a csv and build your own analysis.

  • Hard to segment feature requests based on user and company properties like plan and MRR.

  • Hard to close the loop with customers after you ship a requested feature.

  • Poor centralization. Feature requests that come in via other channels like email, Slack, Salesforce etc. need to be handled with a different process.

You can workaround the difficulties in spotting trends to some extent by:

  1. Exporting all of your messages to CSV using: Inbox / Reports / Export.

  2. Building your own pivot table to analyze feature requests trends. Be aware that the export doesn’t include company or user attributes so you won’t be able to segment feature requests by plan, MRR or other attributes that might be important to you. The export also doesn’t include the message content. This means you won’t be able to use the export to dig deeper into what people really want. For that you’ll have to go back to the Inbox and walk each message individually.

You can workaround the difficulties in closing the loop by:

  1. Exporting your message per above.

  2. Filtering the messages to only include the ones that have the tag you want.

  3. Copying and paste all of the email addresses back to Intercom or your email tool to send feature requesters messages.

Option 2: Use a General Purpose Tools

With this approach you use a general purpose tool like Google Sheets, Air Table or Trello. As feedback comes in you manually paste it into the tool.


  • Don’t need to learn a new tool.

  • With careful maintenance you can group related feature requests and highlight trends.

  • Can be used to centralize feature requests from multiple channels not just Intercom.


  • High friction. You need to leave Intercom and paste a bunch of info into another tool.

  • Hard to segment feature requests based on user and company properties.

  • Hard to close the loop. Have to manually email each user by copy and pasting their email address back to Intercom.

Option 3: Use a Purpose Built Tool Like Savio

With a purpose built tool like Savio you get a smooth, integrated process designed to make it easy to track feature requests from Intercom as well as many other channels like email, Slack and Salesforce.


  • Low friction. Just tag a message and it gets added to your Feedback Vault.

  • Easy to highlight trends and see at a glance what feature requests are most important.

  • Easy to segment feature requests based on different user and company properties like monthly spend and plan.

  • Built in workflow for closing the loop after feature requests are shipped.

  • Unified system for all feedback not just feedback from Intercom.

  • Many additional features designed to give you a high quality feature request tracking system.


  • You need to learn a new tool.

  • You have to pay for an additional tool.

How to Choose an Option

If you are only getting a handful of pieces feature requests a month, requests primarily come via Intercom and you don’t care about segmentation then consider using Intercom + tags + CSV export. It’s low friction and it’s better to actually capture feature requests then not capture them.

If your feedback is multi-channel, low volume and you’re price conscious consider a free general purpose tool like Google Sheets or Trello but only if you are confident that team members are really going to jump through the hoops required to capture the feedback. There is no point in starting the effort if it’s not actually going to get used and this approach takes more discipline on the part of the submitters.

If you get a moderate amount of feedback, receive feedback from different channels, or care about segmentation then it’s worth investing in a purpose built tool.

By having a strong process around feature requests you’ll be able to grow revenue, reduce customer acquisition costs, and increase retention. Your customers will appreciate your more thoughtful use of their feedback and the product improvements that come from it.

Last Updated: 2023-04-14

Kareem Mayan

Kareem is a co-founder at Savio. He's been prioritizing customer feedback professionally since 2001. He likes tea and tea snacks, and dislikes refraining from eating lots of tea snacks.

Want more articles like this?

Product Leaders from Slack, Zapier, and Appcues read our newsletter to delight customers, lower churn, and grow revenue.

Prioritize high-value Feature Requests

Centralize customer feedback from HubSpot, Intercom, and Slack.

Prioritize high-value features sorted by churned revenue or MRR.

Close the loop for Sales and CS by automating status updates from JIRA.

Learn more


Use HubSpot CRM? Collect and Prioritize Feature Requests

Get a central hub of customer feedback sorted by HubSpot attributes like churn or MRR.