Loading post…
IntercomTutorial
The right way to respond to feature requests - The Intercom Blog
Summary
Customer support teams frequently encounter feature requests that reveal gaps between a product and user goals, and responding effectively requires a rigorous framework. The post categorizes these requests into three types: unresolved problems with existing features, improvements to existing features, and brand new feature requests. For each type, it recommends a tailored response: educate customers on workarounds for problems without promising specific fix dates, suggest alternative existing functionality for improvements, and honestly decline new requests while acknowledging the gap and offering third-party solutions like Zapier or YouCanBookMe, sharing context about limited engineering resources. Prioritization should also consider customer lifecycle, high-value users, implementation difficulty, and feedback volume to balance satisfaction with engineering resources and long-term strategy. Closing the loop by tagging conversations in Intercom and sharing monthly customer voice reports with product managers ensures feedback drives roadmap decisions and builds long-term customer success.
Context
A framework for handling feature requests in customer support, categorizing them into three types and providing tailored response strategies, prioritization criteria, and methods for closing the feedback loop with product teams.
Approach / What changed
Categorize feature requests into unresolved problems, improvements, and brand new requests. For each, respond with education, workarounds, or honest decline with third-party suggestions. Prioritize based on customer lifecycle, high-value users, difficulty, and feedback volume. Tag conversations and share monthly reports with product managers.
Takeaways
Feature requests fall into three categories: unresolved problems with existing features, improvements to existing features, and brand new feature requests, each requiring a different response strategy.
For brand new feature requests not on the roadmap, be honest, explain the context, and suggest third-party solutions or integrations instead of making empty promises.
Prioritize feature requests by considering customer lifecycle, high-value users, implementation difficulty, and volume of feedback to balance customer satisfaction with engineering resources.
FAQ
How should I respond to a feature request not on the roadmap?
Be honest and acknowledge the gap, explain the context of limited resources, and suggest a viable workaround or third-party integration like Zapier or YouCanBookMe.
What factors should I use to prioritize feature requests?
Consider customer lifecycle (especially new users at risk of churning), high-value users, difficulty of implementation, and the volume of feedback for each request.
How do I handle a customer reporting an unresolved problem with an existing feature?
Use it as a jumping-off point to understand their goal, educate them on workarounds, and avoid committing to a specific fix date; over-deliver rather than promise.
Source and freshness
- Source
- intercom.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.