Share product ideas and upvotes with our product team
Can we make the inbox search, so it also searches on customer data such as email-addresses. Many times I have to search for emails based on their company mailaddress, but the Intercom inbox is just not finding these emails through a simple keyword search. Gmail does a better job at this though.
WhatsApp Business API, does not allow to send audio messages to users via API, so that explains why it is not implemented atm. However, there is a workaround used by many other Customer Support platforms to handle this, that I would love to get adapted by Intercom as well:In the chat, there is next to Gif, photo, files etc. a voice message option that starts a recording in browser and allows the agent to record a voice message. This voice recording is then sent to the customer as a file, not a classic voice message. This is a workaround but totally works and allows us to adapt voice messages (which is a very common communication style with Gen-Z) to our customer communication. CheersPhilipp
Hello Intercom Team,I’d like to suggest a feature that I believe could really improve workflows in Intercom: the ability to edit internal notes.Right now, if a mistake is made in a note, the only way to correct it is by adding another note or deleting the original one, which often leads to clutter. Having the option to edit notes would help keep conversations cleaner and more organized.To balance flexibility with accountability, you could also provide a setting to either: Allow edits without tracking versions, or Enable version history so teams can see changes if needed. This would reduce unnecessary clutter while still preserving context where required.I believe this enhancement would make internal collaboration smoother and save teams time.Thanks for considering this request!Regards,Syed H
This idea is to create a version history for workflows.When working on workflows, it would be great to have a version history. This is useful when the need comes to revert changes. Also, a version history helps tracking changes made overtime.When testing workflows and making constant changes for testing purpose, having to manually redo-undo isn’t optimal. Being able to restore/revert to a previous version of a workflow would be much easier.
Hi, another suggestion we would like to add: Version History in WorkflowsWe would like to request a feature that provides version history within flows. When working in workflows, it is easy to lose track of previous configurations. Often, we need to test changes live to ensure they work as intended, and in many cases, it is helpful to review how things were set up before. Currently, we create multiple duplicates of workflows because we hesitate to delete them, thinking we might need them again later. This leads to clutter and makes it difficult to maintain an overview. With version history, we could reduce the number of duplicates and keep our workspace more organized.
Hi Intercom team! We would love to see a feature that would allow us to easily submit our specific holiday hours and closures by the individual holiday. It would be awesome to pull up a calendar view and be able to select the date of the holiday and simply mark if the hours are different from BAU or select if that specific holiday is open or closed based on the business. Thank you for considering these ideas from the community.
Instead of sending a new internal note on a ticket, it would be great to thread messages, similar to what you do in Slack - This is possible in Freshdesk, would love to see this on Intercom!
For specific filters in Monitor- we would like to have a "match" option. As in - we are trying to identify different users with the same company ID and we want this to be dynamic. Meaning- if we have different users from the same company ID from many different company ID's we want to make a flag for a trend so they can be pushed to an agent ASAP an not stuck in a conversation with FIN. (As Monitors grows to monitor teammate conversations as well, this would be super helpful for making sure agents are working together and can identify trends/bugs quickly)Context - if multiple users reach out about a bug from the same company, we want to have an opportunity to have shared communications with the users that includes them all in the communication/troubleshooting process. As opposed to the individuals not knowing that the other reached out about the same thing. This will decrease duplicate work done by our customers at the company who reach out to us, as well as our technical team having to interact with individual users separately creating duplicate work.Goal is to have one agent work with multiple users reporting similar/same issues to improve user experience.
Summary:Provide the ability to control Fin agent access to articles by default (either individually or a folder level default), and/or support for configuring this setting via API while creating/updating articles.Problem:Currently, all published articles default to having Fin access enabled. While we intentionally publish some articles as unlisted (accessible only via direct link), Fin can still surface these articles and information within to users.Our team frequently manages articles via API and is not always working directly in Intercom. As a result, we cannot reliably disable Fin access without manually logging in and updating each article.Why this matters:Unlisted articles are meant to be restricted to users with direct links Fin surfacing these articles can expose context-specific or limited-use information This can lead to: Customer confusion Incorrect guidance being shared Increased support friction Current limitations:No way to set Fin availability defaults for articles No API support to enable/disable Fin access No ability to control this at the folder level Fin audience settings exist at an individual article level, but are not configurable via APIProposed Solution Ideas:Allow setting a default Fin availability state (e.g., OFF by default) Add API support to control Fin access per article Enable folder-level settings to manage Fin access at scale Ensure unlisted articles can be excluded from Fin by defaultImpact:This would give teams better control over what Fin can surface, prevent unintended information exposure, and reduce manual workflows when managing content programmatically.
Hi,The users are suggesting organizing the messager based on the ticket’s status. For closed conversations, they would like the messages to be archived or moved elsewhere, making the chatbox more user-friendly.
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.
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.