Share product ideas and upvotes with our product team
Some clients have super long signature with images, disclamers and long text. This creates a lot of unnecessary content within the Intecom conversation. I would love a feature that automatically identifies signatures and remove them from the conversation (or at least make them invisible)
Ultimately, I understand the current reporting feature isn't supported but I am being asked by leadership to pull a report of the different Conversation Types we handle and log via the Intercom Chat. It seems that unfortunately only the channel of each conversation is supported via reports.I’d love to see a report where I can quickly see the different conversation types by number. This helps our team understand the amount of questions per topic.
The IssueFin automatically sends the "Did that help?" prompt after every response. When customers say "Yes," the conversation closes immediately. This breaks workflows where Fin provides an explanation but still needs to collect data or perform a handover.Example: Customer: "I want to change my email." Fin: Explains the requirements and asks: "Please provide your new email. Did that help?" Customer: Clicks "Yes" (out of politeness). Result: Fin closes the ticket before the customer can provide the email. This leads to negative CSAT and duplicate tickets. Requested Improvements Toggle Auto-Reply: Ability to disable the "Did that help?" prompt for specific Procedures or Intents. Logic-Aware Closing: Fin should recognize if he just asked the user for information; in these cases, the success prompt should be suppressed. Custom Follow-ups: Allow the "Yes" button to trigger a specific next step in some cases (not for all conversations) instead of an immediate close. Business ImpactReducing "premature closures" will significantly improve CSAT and prevent customers from feeling "shut out" by the bot, while maintaining the efficiency of Fin’s pre-qualifying explanations. Previous Workaround (Inefficient)To prevent this, we previously marked these intents as direct handovers. However, this meant agents had to handle the basic explanations themselves. We want to keep Fin’s efficiency in explaining the process (which works in 90% of cases) without him prematurely "killing" the conversation via the success prompt.
Some customers are entering their inquiry in the “name” field by mistake, leading to names that are whole sentences. This is causing issues when the name is pushed to external systems that limit the length of name fields. Can a feature be added to allow a custom length limit for the name field?
Currently, notification settings are global and apply across all inboxes and activity types. This creates noise for teams who only work in a specific inbox at a time (e.g. live chat and later emails after hours), as they receive notifications for all inboxes and for teammate actions like assignments, closures, and internal updates.It would be valuable to:Configure notifications per inbox Separate customer activity (messages/replies) from teammate activity (assignments, status changes, etc.)This would help teams stay focused on real-time customer conversations without unnecessary internal noise.
Hi! We would like the Special Notice we post to remain visible in the chat window at all times, even after the user has started writing messages. At the moment, it disappears after the user sends their first message, which is unfortunate as not everyone notices it. This is particularly evident on days when we have a one-hour closure in the middle of the day.
It would be very helpful to be able to manage the snippets via the intercom API for a variety of maintenance tasks and for changes in operations to review and purge outdated snippets as well or to transform that content into guidance or procedures etc where needed. List snippets using the Developer API
This is the text that appears if you configure Intercom so that some articles are public and some are behind a login. If the user isn’t logged in and clicks a link in a public article to an article that is gated/not public, this is the message they see. The only customizable text is the word at the end (and the URL it points to). I would prefer to be able to customize the whole sentence so we can tailor our message to our audience. However, if it must remain static, the terrible punctuation should at least be improved. Proposed updated text:"This article is only available to logged-in users. [Sign in to continue] or send us a message if you need help."Where “Sign in to continue” text is fully customizable, as is the URL it links to. Thank you very much!
Whenever I create articles in Google docs (because we can leave comments and collaborate cross departmentally) I have to go through the same song and dance each time of removing the mess of text Intercom adds in place of a “ or a ‘. This makes writing any kind of article a nightmare, especially a multilingual one.Please ensure your composers respect pasting as plain text.
Today, Inbox search lets you filter to Open, Snoozed, or Closed, but there’s no way to filter for everything that’s not Closed (Open + Snoozed) in one view. This would help teams quickly see all active conversations without having to switch between Open and Snoozed.
Add a ‘backlinks’ view for Help Center articles so we can quickly see which other articles link to a specific article. This would make it much easier to audit content relationships and avoid broken links when updating articles.
Right now, CTA buttons in in-app messages (popups) have fixed styling with rounded corners and no option to customize their appearance.It would be really valuable to allow basic button styling controls such as:Corner radius (e.g. sharp vs rounded edges) Padding / size More flexibility in visual appearanceThis is especially important for maintaining brand consistency across channels, since email templates already support more advanced button styling.At the moment, the lack of control in popups creates inconsistencies in UI/UX and limits design flexibility.
There’s already a feature to assign visibility conditionally on the team inbox where the customer is assigned for Custom Conversation Attributes. Can you expand that to Standard Attributes plus the People and Company objects?
When a Banner is active in Intercom, teams should have the option to make its content available to Fin as a knowledge source. When the Banner is paused or deleted, that content should be automatically removed from Fin's knowledge base without any manual steps.The problemBanners are commonly used to communicate important product changes, outages, or announcements. In practice, many customers dismiss or skim banners without fully absorbing the information. This generates avoidable support volume — customers contact support asking questions the banner already answered.Fin has no visibility into active banner content today, so it cannot answer these questions accurately or consistently, even when the information is current and relevant.There are existing workarounds — such as creating a snippet or article with the same content — but these require manual cleanup after the banner is removed. Without that cleanup, outdated information remains in Fin's knowledge base, which creates a different problem.The proposed behaviourWhen creating or editing a Banner, an option is available to include the banner content in Fin's knowledge base. When that option is enabled and the banner is published, the content is automatically added as a contextual source for Fin. Fin can reference that content when responding to related customer questions while the banner is active. When the banner is paused or deleted, the content is automatically removed from Fin's knowledge base — no manual cleanup required.This closes a gap between what customers are told through banners and what Fin can actually answer. It reduces support volume during product change windows, improves the accuracy of Fin's responses, and removes a manual process that teams would otherwise need to manage themselves.
When using a macro in a Slack side conversation, macro variables (such as company name or custom attributes like Company ID) do not populate. The same macro works correctly in the main Intercom conversation, but the Slack side conversation thread leaves those fields blank.Because Slack side conversations are synced with the main Intercom conversation, it would be more consistent if macros could automatically pull the same conversation data (user attributes, company attributes, etc.) when applied in the Slack thread.This would improve teammate efficiency and reduce manual data entry when responding from Slack.
I've found this question I had a few times on this platform and I can't wrap my head around the fact that this is not possible. I think this is very basic Support platform functionality. The answer from Intercom is; Use the REST API. This is not a workable answer for many people, so I suggest just adding a “+ Create new company” button in the Contacts section: Thanks for your consideration :)
Addition of domain field for companies with automatic email domain identification.When someone writes in from a domain that is clearly associated with a company, it would be helpful if the system automatically detected this. This would not only be helpful for reporting purposes but also for workflows where certain content is specific to a segmented audience. As an example, if Big Health’s domains are sleepio.com, trydaylight.com and bighealth.com, allow the team to specify those associated domains in company details and when someone writes in from teammate.name@sleepio.com, automatically assign the company “Big Health”. This would allow Fin to point to guidance specific to the “Big Health” audience in knowledge base and in workflows
Animated GIF launchers for iOS and Android let users quickly discover, preview, and insert GIFs directly from the app. This makes conversations more expressive, fun, and engaging while keeping the experience fast and seamless across mobile platforms.
Currently, conversation datasets/reports measure handling time from the start of the conversation until closure. This includes time that occurs after a ticket is created, which makes it difficult to measure the true chat handling time for our frontline support.It would be helpful to have a new metric that measures chat handling time only until ticket submission, excluding any time spent after the ticket is created.This would allow teams to:Measure the actual time spent handling the chat conversation. Compare chat handling performance without ticket processing time. Build clearer SLAs and reporting for chat vs ticket workflows.
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.