Share product ideas and upvotes with our product 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 🙌
SummaryWhen an article is created or updated through the REST API / MCP then the `style` attribute on table <td> tags are removed, undoing styling that was applied in the web editor to customize colors or widths. Steps to ReproduceUse the Knowledge web editor to create an article with a table, assign colors the to the column headers and adjust the column widths. Use the REST API / MCP to retrieve the article HTML, note that the retrieved article’s body contains the `style` attribute defining background-color and width on the <td> tags. Use the REST API / MCP to re-save the article as-is. In the web editor refresh the article and note that the table styling was removed. Use the REST API / MCP to retrieve the article HTML, note that the retrieved article’s body no longer contains the `style` attribute on the <td> tags. Expected ResultThe `style` attribute on the <td> tags defining the background-color and column width is preserved. Actual ResultThe `style` attribute on the <td> tags is removed. Example Step 1 Example Step 2<div class="intercom-interblocks-table-container"> <table role="presentation"> <tbody> <tr> <td style="background-color: #d7efdc; width: 320px;"> <p class="no-margin">Header 1</p> </td> <td> <p class="no-margin">Header 2</p> </td> </tr> <tr> <td style="background-color: #e8e8e8; width: 320px;"> <p class="no-margin">Lorem ipsum dolor sit amet</p> </td> <td> <p class="no-margin">Sed ut perspiciatis unde omnis iste natus error</p> </td> </tr> <tr> <td style="width: 320px;"> <p class="no-margin">Ut enim ad minima veniam</p> </td> <td> <p class="no-margin">Consectetur adipiscing elit</p> </td> </tr> </tbody> </table></div> Example Step 4 Example Step 5<div class="intercom-interblocks-table-container"> <table role="presentation"> <tbody> <tr> <td> <p class="no-margin">Header 1</p> </td> <td> <p class="no-margin">Header 2</p> </td> </tr> <tr> <td> <p class="no-margin">Lorem ipsum dolor sit amet</p> </td> <td> <p class="no-margin">Sed ut perspiciatis unde omnis iste natus error</p> </td> </tr> <tr> <td> <p class="no-margin">Ut enim ad minima veniam</p> </td> <td> <p class="no-margin">Consectetur adipiscing elit</p> </td> </tr> </tbody> </table></div>
Customers have asked for the ability to export their support history directly from the widget.
Right now, when a User or Lead is archived in Intercom, all their conversations are archived too. This causes problems because teams often still need access to past conversations for context, audits, support continuity, product investigations, and customer history - even if the user is no longer active.What we’re asking forPlease separate the act of archiving a user/lead from archiving their conversations. Conversations should stay visible and searchable unless an admin chooses otherwise.Why this mattersTeams rely on historical conversations to understand past issues and avoid asking customers to repeat themselves. Product, Engineering, and Compliance often need older conversations for investigations and audits. Archiving conversations affects reporting, SLAs, tagging trends, and Fin AI analytics. Re‑engaging customers becomes harder without visibility of previous interactions.Suggested improvementsAdd a workspace setting that lets admins choose what happens to conversations when a user/lead is archived (e.g., keep them visible, archive only closed chats, or apply a retention period). Provide a simple checkbox option when archiving a user/lead so the teammate can decide what to do with the conversations. Keep conversations discoverable in Search, Reporting, QA/Monitors, and Fin/Copilot analytics even if the user profile is archived. Show a small banner like “This user is archived” without hiding any history.What success looks likeArchiving a user/lead no longer hides or auto‑archives their conversations. Teams can still view, search, and report on those conversations. Open conversations remain open unless a teammate or rule closes them. The workflow is clearer and reduces accidental loss of useful history.
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.