Share product ideas and upvotes with our product team
I’m looking to trigger certain external workflows when certain articles are updated in our intercom instance. Example workflows include (but is not limited to) customer and internal newsletters. This would be a pretty cool feature to ensure eyeballs are kept on high-value articles whenever they change/are updated, especially as more and more disparate teams are collaborating to ensure these articles are up-to-date.
As the product owner for our intercom installation I would like to hide the inbox from the left panel for teammates that don't handle tickets.For instance our marketing department writes articles, send outbound messages and does automations.They don't need to see the button to the inbox and should not be able to be assigned to a ticket.
Since Intercom allows for multiple contacts (users) to have the same email address, using a combination of attributes and/or fallback logic is a better way to identify a particular user compared to email alone. Intercom's Zapier action Find user provides a number of options which would allow you to return a single user as a result, but the Add note action does not. Because the Add note action only allows email as an input, it errors anytime Intercom returns multiple users with the same email. And because it only allows email as an input, there is no way to get around this — and this makes this action unusable in all cases where an email address belongs to multiple users. Feature request summary: Bring Intercom's Add note Zapier action to parity with Intercom's Find user Zapier action by allowing multiple attribute inputs for finding users and/or fallback logic when multiple users are identified.
Currently, Intercom’s article editor only supports anchor (jump) links for headings H1 to H4 using the “Copy anchor link” feature. I am requesting a built-in way to create a jump link for <p> tags or other non-heading elements—manual anchor tags like <a href="#my-section"> . I would like to create direct jump links to normal <p> tags or regular texts within the same article which are not currently supported in the current editor workflow.
My company relies on the Intercom as a tool for communication with customers, we have encountered some challenges when it comes to serving our Georgian-speaking customers effectively.One of the main issues we face is that Intercom currently does not support the Georgian language and it causes some difficulties while in communication. We have started to use a Language Override in workflows. However, we find that we are unable to fully address all cases.Also currently, Intercom does not allow us to publish a separate Help Center in the Georgian language alongside the English one.In light of these challenges, we have been actively researching other companies from Georgia that utilize Intercom and have found that many of them using Intercom.We kindly request that Intercom consider adding support for the Georgian language as an official language option.
Translate CSAT feedback into default workspace language. Right now, we’re translating the conversation but then when a user leaves feedback in their native language, I still need to use a third-party tool to translate the feedback to understand it.
I would like to be able to upload my own recording for the outbound call message that notifies customers that the call is being recorded.
I'd like to submit a feature request on FIN AI Agent Suggestions. It would be great if it could be possible to sort the list. A use case would be the ability to sort suggestions based on number of conversations used to generate the suggestion so we can begin or focus on optimization efforts that would have the most impact.
There are several ideas related to this topic where people are struggling with pausing workflows and setting them live again during the holidays. What we do at our company is we duplicate our normal workflow and add a message saying “Hello! We're currently closed, but feel free to ask your question. You will receive an answer through e-mail as soon as we're open again.” We then publish it scheduled. Another user commented that they do something similar:https://community.intercom.com/ideas/would%2Dlove%2Dthe%2Dability%2Dto%2Dschedule%2Da%2Dspecial%2Dnotice%2Dfor%2Dthe%2Dholidays%2Dinstead%2Dof%2Dhaving%2Dto%2Dturn%2Dit%2Don%2Dand%2Doff%2Dmanually%2Din%2Dreal%2Dtime%2D3487?postid=26377#post26377 The problem is that after the holidays are over, the workflow is “paused” and you can't schedule it again for the new upcoming holidays. It would be great if this became a feature so you don't have to duplicate it again. Thanks in advance!
When users ask for a recovery code they receive this email from Intercom: “Hello (name), Your teammate Marijke has generated a new recovery code for you. This code can only be used once. Your recovery code is (code)You can use this to regain access to your account by entering it in the recovery code field. Once in you should set up 2FA on another device or download your recovery codes so you don't get locked out again: https://www.intercom.com/help/en/articles/181-protect-your-account-with-2fa-google-sign-on-or-saml-sso#enable-2fa-on-your-intercom-account- If you did not request this recovery code, please contact Marijke or Intercom customer support at team@intercom.io.” If you click the link you get directed to a generic article, regardless what your function is (admin or user). A lot of our users do not understand what they have to do to set up 2FA again. It would be better if an anchor link was used so you get to the relevant part, which is:“How to Migrate authenticator app to a new deviceTo migrate your authenticator app to a new device to be used for 2FA with Intercom, follow these steps:1. Log into your Intercom account on your computer.2. Go to your Preferences page by clicking here.3. Toggle off "Enable 2FA".4. After disabling 2FA, toggle it back on to set it up with your new phone.5. Scan the QR code displayed on your computer screen using the authenticator app on your new phone.” It would also help if the title was “How to reset 2FA or migrate authenticator app to a new device” or something like that. Thanks in advance!
I would like to propose a solution to an issue that my team has come across when trying to create tags within the Intercom Knowledge module. Currently, it is not possible to use the down arrow + Enter key to select and assign existing tags when searching for existing tags using the search bar. This shortcut is present on many softwares, and this would be a huge QOL improvement for us as we are working with multiple articles a day. The Intercom team’s help would be greatly appreciated regarding this matter!
IntercomRootActivity shown to be leaking with the Android Studio memory profiler. Steps to repro:Launch your app in debug, or attach debugger. Launch Intercom with a call Intercom.client().present(IntercomSpace.Home) Close Intercom completely. Go to Profiler->Memory then Capture heap dump. Android Studio should report IntercomRootActivity as leaking. Alternatively, if you’re using LeakCanary, it will show over UI because it is detecting this leak.
Why does the Intercom workflow trigger for “opens a new conversation in the messenger” require a reply button on mobile?Our goal is simple: we want to automatically send an introductory message as soon as a user opens a conversation on mobile, without forcing them to tap an unnecessary button first. This extra step creates friction and isn’t user-friendly.Unfortunately, switching to the “Customer sends their first message” trigger isn’t viable either. Many users won’t know they’re supposed to send a message at all unless they’re guided, so waiting for their input first defeats the purpose.Disabling the error message would solve this problem immediately.
Hi Intercom Team, In this documentation https://www.intercom.com/help/en/articles/7872967-auto-close-incomplete-workflows-conversations it says that we can customize a message when the chat auto close due to abandoned workflows.But the option is nowhere to be found.After going back and forth with your team, they confirmed that the custom message is only available when the workflow use FinAI, and regular workflow doesn’t have this capabilities.This is completely misleading and the auto-close is not helpful and even create bad customer experience.Please fix this and add the proper feature as promised in the documentation.Thank you.
Currently when an email comes through, the subject line isn’t completely visible and you have to click on the message to view it. Some clients who are not technologically savvy can write their full emails in their subject lines. 🙄 We would like to be able to see the full subject line without having to go find it/click to view. This would ensure that no important information is missed.
Hello, Often times I am utilizing a report drill in and I want to open every conversation (case) for review. Can you please add a bulk open option?Currently, I have to click each one individually. It also will pull me into each new tab as I open it so I have to go back and forth opening each one.I’d imagine this being a multi-check box select option with a “select all” option as well but open to your expertise.Thank you for your consideration.
We are using a lot the tickets to handle the follow up of our clients (tons of steps). Backend is playing with ticket states which enable different workflow. Currently we have a single massive workflow to handle everything because we cannot split it into several reusable workflows. Worst, we have to manually duplicate it for different events that triggers the workflows. Here is the list: Ticket is created Ticket state is updated Customer has been unresponsiveIt means we have to maintain 3 times the same behavior. Of course, this leads to tons of possible human mistakes. This idea might be linked to this one but more detailed with explanations of our workflows.
When writing help articles, there are often pieces of information that shouldn’t be publicly visible or are only relevant in very specific scenarios. A common example is notes about known bugs that haven’t yet been prioritized for resolution.Currently, I handle this by creating internal snippets and adding clarifying context where possible. However, it would be extremely helpful if we could tie specific snippets directly to articles, without making them publicly visible. This would: Allow us to maintain a single source of truth, even for edge cases or temporary issues Enable Fin to use these internal notes when assisting users, leading to more accurate and context-aware responses Reduce the need for support agents to rely on memory or scattered internal documentation This kind of backend tagging or linking could make our support content more flexible and powerful.
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.