Share product ideas and upvotes with our product team
It would be extremely helpful if you could add a sentence to every chat reply we send to our customers - the sign off for example Kind regards Customer Service Team It would be useful to have this automatically come up on the reply bar so we don’t have to personally type this or look for the macro we have created for it. Thank you
Please add support for publishing articles in Tamil in the help center. This is critical for better supporting the full scope of users in South Asia/India.
At the moment, it is not possible to merge tickets that originated via email or messenger with tickets created from a phone call.In practice, many of our customers follow up on the same issue across multiple channels. Not being able to consolidate this information into a single ticket makes handling these cases unnecessarily cumbersome and error-prone.We consider this a significant limitation and would strongly appreciate support for merging these tickets across channels.
We use the merging feature HOWEVER we need the ability to be able to merge any ticket. Not just the ones intercom offers to us. Previously, with our other product we were able to pick the ticket number we wanted to merge, it would show us, as intercom has now, and then we would be able to merge it. Intercom. Doesnt seem to recognize two tickets we have that need merging and it doesn't offer. Example: our customer sends us a direct email & we get that same emal from one of our subs. We would merge those. We get a phone call and we already have a ticket regarding this exact call we would want to merge that call with its pre existing ticket.
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
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.
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.