Share product ideas and upvotes with our product team
Currently, the “Continue on WhatsApp” action always routes the customer to a single WhatsApp number configured in Settings → Channels → WhatsApp → Switch from Messenger to WhatsApp (one number per workspace).This creates a limitation for companies operating in multiple countries with different WhatsApp numbers per region. There is no way to direct customers to their corresponding local number, which negatively impacts both customer experience and operational efficiency.Problem:If a business uses different WhatsApp numbers per country, all customers are still redirected to the same number, regardless of their location or attributes. This can lead to:Customers contacting the wrong regional team Delays in response times Fragmented conversations and routing issuesSuggested improvement:Allow agents or automation rules to select which WhatsApp number is used when triggering “Continue on WhatsApp”.For example:Route based on customer attributes (e.g., country, language, region) Allow rules in workflows to define the destination number Allow agents to manually choose the WhatsApp number when using the “Use Continue on WhatsApp” action in conversationsThis last point would already be a significant improvement, as it would give support teams immediate control to route customers to the correct local number during live conversations.This would enable businesses to:Maintain local communication channels Improve response times and routing accuracy Preserve a better customer experience across regions
We have multiple teams on Intercom and each team utilizes slightly different “Away” statuses. It would be helpful to be able to customize which teams a given “Away” status is displayed for so that teams aren’t having to scroll through all options to find those specific to their team.
We have adopted FIN voice but when FIN is unable to handle the query it needs to be escalated to a human agent. It would be helpful if we can build an ‘AI Summary step into the workflows like we can with live-chat. This will streamline calls and prevent clients from having to repeat themselves.
Hi there, I’d like to request support for custom hold music in Intercom’s phone workflows. It would greatly improve the customer experience if we could upload an MP3 or audio file that plays while the caller is waiting, similar to traditional hold music. Ideally, agents should still be able to answer the call at any time, even while the recording is playing. This would bring Intercom’s call experience closer to an enterprise-grade system and help us maintain a professional, branded phone experience. Thanks!
Currently, you can bulk edit the fin audience, tags, and status. However, it would also be ideal to be able to select all articles in a collection and bulk edit the help center audience. Doing this manually is extremely time-consuming if a collection has more than 10 articles. We ran into this issue when adopting a new product: we want certain users to see specific articles in our help center. This goes beyond Fin. Luckily, our colleague found a way to set up an automation script, but that shouldn’t have to be the case.
Would be great to have custom colour options available on the Help Center when editing articles, e.g. font colors to highlight particular sections in the text or custom colors for the call outs etc.
This is really a 2 fold questionIs it possible to allow users to subscribe to collections and receive notification when new articles are added? How are other companies disseminating patch notes to customers who want to “subscribe” and receive notifications when patch notes are released?
In episode 13 of Support Stack, Thomas Hils (Head of Support @ Wingspan) shows how he’s rebuilt QA using Claude Cowork + Intercom, without adding another tool.It’s a really practical look at: why QA gets harder as Fin improves where AI falls down without structure how to actually make AI useful for QA Watch here:
I want to be able to use the API to search for conversations with a certain CX score within a particular date range. Can you please add CX score to Accepted-Fields? https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations/searchconversations#section/Accepted-Fields
A report that allows us to analyze how agents are assigned and moved across different inboxes during their shifts (e.g., chat, email, snooze, tickets, etc.). This will provide greater visibility into workload distribution and support more effective operational planning.
A report that shows the amount of time (hours) an agent spends operating at maximum capacity during each shift. This will help us better assess headcount requirements and improve schedule distribution across the operation.
Where it checks their most recent outbound and only sends if they haven't gotten an outbound within x number of days, ie.. within the last 2 or 3 days We have separate outbounds and workflows and it’s too hard to coordinate rules so users don’t get spammed
After learning in a Fin chat that functionality doesn’t exist, I asked it to submit a feature request, and was directed here. Customers shouldn’t have to take this extra step when you can automate it.
We should be able to select button colors for posts as we do for banners. I don’t want to use the color I have defined in brand settings.
We currently have 20 ticket attributes visible, some of which are not commonly used, or not used across all teams working the same ticket types. It would be great if users had the ability to customize the ‘Ticket attributes’ view to pin or hide, and re-order specific attributes. If they could re-order the view it would also be very helpful, but just being able to hide certain attributes would make it much easier for the team to focus on key ticket attribute fields.
Allow users to export their own tickets from the ticket portal, and allow this to be restricted to own tickets only vs company-wide tickets.Ticket attributes should include dates, requester, title, state.
We would love to use the newsfeed to make it easier to send short updates to our customers rather than having to post these in articles. However, we post all updates in four languages (potentially more in the future). We don't have an easy way to make these news items multi-language; we have to make an extra news item for each language.We would really appreciate an option to easily create multilingual news items, to save time and make it easier for our customers to switch languages.
ProblemIntercom currently applies a global setting for file delivery (either all attachments or all links).This creates issues:Compliance constraints: Some B2B partners (e.g. German Netzbetreiber) cannot open links → require PDF attachments Manual workarounds: Agents must download and resend files via other tools Different team needs: Some teams need attachments (PDFs) Others prefer links (videos/images) No way to automatically handle large files (>20MB)Proposed SolutionHybrid logic (size-based): ≤20MB → send as attachment 20MB → send as link Team/inbox-level settings: Configure file delivery per team (not globally) (Optional) Per-message toggle for agentsImpactReduces manual work Supports compliance requirements Improves speed and flexibility across teamsWould love to see this supported 🙌
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.