Share product ideas and upvotes with our product team
The current red exclamation mark warning system triggers consistently on legitimate emails due to routing configurations, reducing its effectiveness as a security indicator. When warnings appear universally across all conversations from certain domains or forwarding setups, they lose their ability to highlight genuinely suspicious activity.The system currently applies blanket risk assessments without distinguishing between legitimate routing patterns and actual security concerns. This creates "warning fatigue" where users become desensitized to alerts, potentially missing real threats.Proposed improvement: Enhance the warning algorithm to better differentiate between legitimate email configurations and actual security risks, reducing false positives while maintaining protection against bad actors.
We offer a platform for collecting and reporting ESG data. Sometimes, we get questions from users reporting data that we need to check with users collecting data (i.e. our customers). Instead of forwarding the email and creating a separate conversation, it’d be very neat if one could forward an email and create a side conversation out of it. That way, we would have related threads in one single place.
Customers would like to completely hide chat bubble so it isn’t a distraction to their work. Additionally, they would like to be able to totally clear out/delete a announcement messages.
The ability to utilize the Automated Workflow features in Intercom for the Phone Channel. Using the “Convert to ticket” button in phone interaction does not allow that interaction to be recognized in ticket workflows. (Intercom internal team indicated this was a feature request - submitting here) Business case why this would help - keeping the transcript and recording with the ticket will improve the service experience and also not require the team to create duplicate tickets separate from a phone interaction.
Ahoy everyone!It’d be great to have the option to view CC’d addresses in an email thread instead of only having the “To” field visible. Our crew deals with time-sensitive conversations which require confirmation that a user’s response to our outreach includes all participants, but some major email platforms will automatically migrate participants other than the sender to the “CC” field regardless of initial positioning. As an example, a reply sent from Gmail will only allow one address in the “To” field, while a reply sent from Yahoo respects user input and allows multiple addresses in the “To” field. Our crew currently has to check the raw email data for every conversation and compare it against the participants listed in the right-hand sidebar of the threaded conversation due to these inconsistencies, which results in increased handling time and more potential for error. Adding the CC field into Intercom’s email display would be huge help!
We are having a hard time having Fin AI Agent being able to read and answer questions based on multi-column tables. It seems like this would be a pretty easy thing for an AI to manage understanding.
When searching a term within the Help Center, I would like the possibility for that word to stay in the search bar even when I access a suggested article. It gives me more context of what I’ve been looking for and would also be relevant for search history.
When using the search bar within the Help Center functionality, I would like to be able to see my search history below the search bar when entering a new query. That would make it possible for em to see what I searched before and go back to previous content.
Hello,With the introduction of the FIN support for webhooks (https://community.intercom.com/ideas/add-fin-replies-to-conversation-webhooks-7784), businesses can use workflows to speed up the work.When FIN/Workflow replies with a comment which includes quick reply buttons, the two “conversation.admin.replied” webhooks are sent. One with the conversation part with type `conversation_part` and the second with part_type: `quick_reply`. Here is how the message with quick reply buttons looks in Intercom:The FIN message with two quick reply buttons sent by reusable workflow Unfortunately, The webhook with part_type: `quick_reply` does not include information about the buttons:Webhook payload for part_type: `quick_reply` As many 3rd-party chat platforms have support for quick reply buttons (including Telegram), it’d be nice to include the information about buttons to the quick_reply webhooks.In the Intercom documentation, there is a parameter `reply_options`. Perhaps, there is an issue in the code that prevents having `reply_options` in the webhook:REST API docs https://developers.intercom.com/docs/references/rest-api/api.intercom.io/models/admin_reply_ticket_request Also, to have a complete set of tools to incorporate quick reply, it is essential to have an endpoint that allows “click” on a quick action. For example, an additional parameter in the reply endpoint:curl example
It would be really nice if there were an option to mute notifications temporarily that was a lot more accessible on the main page, rather than digging through the settings. I suggest having the option in status like how Slack does because it is a lot easier to remember since Intercom already displays it so well when you are on away mode or away and reassigning. Where as currently muting notifications through the settings, you won’t remember they were muted until you missed a few conversations and your boss is mad at you! lol.An example of where our team would find this extremely useful is for the teammates who only cover support when support agents are out of office, but use Intercom daily for internal purposes. It would be nice for them to set their selves as a custom away status like “Not Covering Support” and that status be set to mute all notifications- or custom notifications. Then when they are covering, they just easily make themselves active!
Bonjour, ma demande/ suggestion est d’ajouter un attribut pour les rapports : Ticket Back office. Pour notre équipe, il serait pertinent d’avoir cette données, car ceci nous permettrait d’améliorer nos processus internes. Merci
When our customers report P1 tickets (production down), an escalation should be done internally.Typically these tickets are escalated to the management team via email or SMS.It would be good to be able to send emails from within a workflow to inform management teams.
We would like a singular point within the knowledge base on intercom, where all of our information/data/knowledge/processes are kept in one place. This would include; public articles, snippets, guidance, workflows and tasks, query types/tags all broken down for the information, by customer issues and enquiries.We would like to, for example, have this listed by the query type, where any information lives related to the topic as well as how we would handle it and how Fin/our workflows would handle it. We want this to be in one place so that we can spot duplicates and gaps and have information updated on a master document without having to duplicate the work or update multiple sources.
Currently, in the Intercom Contacts page, I need to select and delete inactive users one by one. This process is very time-consuming and inefficient for our operations.For a more user-friendly experience, it would be extremely helpful to have the option to select and delete multiple users at once directly in the same page. This feature would significantly reduce manual work, save time, and streamline contact management for teams handling large user lists.
When selecting multiple tags to filter from in Intercom Reports, every time you select one tag, the list automatically scrolls back up to the top. This is incredibly annoying as I then have to scroll BACK down over and over again, wasting time. This seems almost like a UX error due to how frustrating an experience it is.
It would be great if we could trigger a reusable workflow via the API.This initially came from a desire to change a ticket status via a macro, which also is not currently possible (I’ve upvoted that on the product wishlist!). I thought a workaround could be setting up a data connector and using that to connect to Intercom’s API and triggering the workflow that way, however it’s not possible to trigger a reusable workflow via the API so that won’t work either.This would be a helpful feature for those of us that use some external automation tools (n8n, Zapier etc.) externally to Intercom so that we can build the workflow in Intercom and trigger it from the external tool, rather than having to build the entire trigger and workflow in the external tool.
Implementing conditional logic for messenger ticket-types: The "Refund" ticket type is restricted to users with the "Owners" user type. The "Feature Request" ticket type remains available to all users. Enhancing ticketing system customizability: New rules to be configured, such as limiting customers to raising only one "Refund" ticket, and up to 3 “Feature requests” ticket. Enabling in-workflow ticket attribute management: Ticket attributes cannot be modified directly within the Workflow Builder, we’re using custom API calls for each change.
At FundedNext, we rely heavily on Intercom to power our Help Center and FAQs. Many of our articles are long and detailed, which is necessary for compliance and clarity. However, modern clients often don’t enjoy reading through large blocks of text, and as a result, some skip important information. This not only reduces the effectiveness of our knowledge base but also increases repeat queries to our support team.Why We Need TTS in IntercomWe strongly believe a Text-to-Speech (TTS) button on Intercom Articles would significantly improve the client experience. With one click, clients could listen to an FAQ or policy being read aloud in a clear, natural voice — instead of having to read it.Benefits: Accessibility – Makes our Help Center more inclusive for users with visual impairments or reading difficulties. Convenience – Traders can listen while multitasking (commuting, trading, or during daily tasks). Engagement – Clients are more likely to consume full content when listening instead of skimming. Support Efficiency – Fewer repetitive queries, since clients will fully understand rules and processes. Competitive Edge – Platforms like Babypips already offer this; Intercom adding it would show innovation and user-first design. Why This Matters to FundedNext Improves customer satisfaction (CSAT/NPS) by making FAQs easier to digest. Reduces support workload by ensuring clients get the full picture without missing details. Strengthens our brand image, since clients will see FundedNext (and Intercom) as forward-thinking and accessible. Alternative Option: Integration with FundeeAt FundedNext, we already have Fundee, our in-house AI voice assistant. If a native TTS feature is not possible in the short term, we’d love for Intercom to allow integration of external assistants like Fundee directly into the Help Center. That way, users could either: Click a TTS button to listen to FAQs, or Interact with Fundee for voice-based answers and follow-up questions. Fundee Call to ActionWe request Intercom to: Add a native Text-to-Speech button for Articles/FAQs, OR Provide integration options for AI assistants like Fundee to connect with the Help Center. This would greatly improve accessibility, client satisfaction, and overall efficiency for FundedNext — and for many other Intercom clients with similar needs.
It would be great if you could push a survey to all Intercom users, allowing them to vote on the most requested features, rather than leaving them buried in the community forum. I see many essential feature requests that most users would consider must-haves, yet they’ve been overlooked for months or even years.Please have a dedicated team review these ideas and launch a survey with a simple yes/no voting option to gauge how essential each request is. This approach would help you run faster experiments, set clearer priorities, and respond more effectively to customer needs.Don’t let valuable ideas sit untouched for years, it slows progress and leaves you behind competitors. Many users don’t even realize this community exists, and we ourselves only just discovered it after being loyal customers for many years. You need to act faster. Empower users to shape Intercom’s future.
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.