Tracking feature requests from Slack

If your company runs on Slack there is a good chance you’re regularly receiving feature requests and customer feedback from internal teams via messages in Slack.

Slack makes an excellent hub for collecting customer feature requests for a number of reasons:

  1. No special tools means less friction and more feedback. Slack is used across teams. If a sales rep talks to a prospect and the prospect makes a feature request it’s easy for the sales rep to shoot a Slack message like, “ACME Corp says they won’t purchase without SAML support” and know that the product team will see it.
  2. Slack is a messaging tool which means not only can you share feedback but it’s easy to have a discussion around that feedback right in Slack. Maybe the product already has that feature or maybe there is a workaround. Maybe the product team needs additional clarification on what the core use case is. All of those conversations can be had right there in Slack and in context with the original feature request.
  3. Slack isn’t just great for submitting feature requests but it’s also a great way to passively hear about what customers care about. You can subscribe to a channel and dip your toe in as you have time to stay on top of what people care about.

Each of the above factors makes Slack a great feedback hub. Unfortunately it’s not without its problems. If you feel like your current Slack-based feedback process lets things fall through the cracks or makes it hard to analyze your feedback you’re not alone.

How Companies Use Slack to Stay on Top of Customer Feedback

The typical Slack feature request tracking process is to create a channel like #feedback and then socialize that channel with all of the various internal teams that want to communicate feature requests to the product team.

For example, when sales or support hear feedback from customers or prospects they shoot a message to the #feedback channel in Slack. The product team monitors the #feedback channel. If clarification is required the discussion happens right there in Slack.

Although this is super convenient for people submitting feature requests to Slack it’s not great for the product team that needs to collate and act on all of that feedback. A few problems quickly become apparent:

  1. There’s no easy way to rollup feature requests and keep track of which ones are most common.
  2. You can’t easily segment feature requests and see which are the most important with different segments e.g. which feature requests are most important with our enterprise customers?
  3. It’s not easy to follow up with customer vs. the internal user that submitted the request. Imagine you implement a particular feature request that has been submitted many times to your #feedback channel in Slack. How will you notify all of the customers who asked for it?

Improving Feature Request Tracking in Slack

Is there a way to keep the simplicity of submitting feedback via Slack while not having the process be hard to manage and having things fall through the cracks?

The key benefit we don’t want to lose in a Slack-based process is the simplicity of having different teams submitting feedback via Slack to a well known #feedback channel.

What we want is to add a layer of management on top of that so that things don’t get lost and so that additional analysis can be done. That’s where Savio’s Slack integration comes in. With Savio’s Slack integration you can:

  1. Send feedback from Slack directly to your centralized Savio Feedback Vault with the click of a button.
  2. Group related feature requests together so you can easily spot trends.
  3. Link feedback to the user and company that provided the feedback.
  4. Segment feedback on key information like plan or MRR so you can see which feature requests are the most important to different segments.

With this extra management layer in place you can have the best of both worlds: a simple process where internal teams can keep using Slack the way they are used to, while you can easily roll that feedback up, pull it together with feedback from other channels like Email and Intercom and segment it to improve you analysis and understanding. With this in place you’ll be in a better position to use feedback to drive future product direction and increase customer happiness.

Start Tracking Feature Requests Today

  • Centralize product feedback from your voting board, Help Scout, Intercom, Zendesk, HubSpot, Slack, or any other tool with Zapier or our Chrome Extension
  • Prioritize feature requests by number of votes or total MRR, or for specific customer segments (like all customers on the "Pro" plan)
  • Share customer verbatims with your product and dev teams
  • Track Feature Request status as your dev team works on them
  • And close the loop with customers

Try Savio Free or learn more about Savio