Share product ideas and upvotes with our product team
Currently, when using the messanger sdk I don’t know if a user has started a conversation. I would like to react to that event but currently it is not easily achievable.I have to poll the Intercom API for all the conversation created events and then filter for that particular userIt would be much much easier for me to just react to a callback from the intercom messanger sdk that a conversation has started and then perform business logic that I want to have. Please consider addign this callback to the messangeer sdk.Similar callback exists in the mobile SDK according to FIN AI and it is called IntercomDidStartNewConversationNotification. I’m not sure how to use it since I am now developing this on a mobile application.
I would like a reporting metric to be able to view the number of customers that have opened more than 1 conversation or ticket within the filtered period.Basically any user id where the count of conversation ids is greater than 1, within filtered parameters.Alongside a count of distinct conversations and distinct users within the filtered period, this will give our team a much better idea of how well issues are being resolved the first time, if the same issues are constantly coming back up, and if the same customers are consistently opening new conversations.
Given we need to reference knowledge base articles from external systems (ex: in banners, in release emails, etc. )Once I’m done editing my article and publishing I want an easy way to get the URL link to that article directly from the editor. I think that was present previously but got removed. pls add it back.
It would be helpful to be able to customize more options for the Phone channel, such as:Edit the default delay after phone menu options are shared before they are repeated (20s is too long and leads to more abandoned calls when they don’t pay attention the first time around) Edit the speed of the AI voice (the voice is a bit too fast and leads to customers missing the phone menu options that are stated) (nice to have) More options for the hold/wait musicThese customizable options will help our customers navigate the phone menus easier, and reduce abandoned calls or calls that get routed to the wrong team.
I think it would be a great improvement to have the ability for the AI to be able to respond to conversations before routing them to a team member, either providing more context as to why the routing is taking place. This would be great for some guidance changes that would allow for responses before closure etc.
At present when taking the ‘Overview’ report as an example, phone calls are automatically grouped under “Closed With No Reply” in reporting. Whilst this classification makes sense for missed calls, it doesn’t accurately reflect answered calls, which are genuine customer interactions handled by teammates.Why this matters: Customer engagement is underrepresented. An answered phone call is a meaningful teammate interaction, even if no written message follows. Grouping these with “no reply” means reporting doesn’t reflect reality. Managerial insights are skewed. Team responsiveness and workload data appear distorted, making it harder to track performance, allocate resources, or demonstrate value. Consistency across channels. With Fin Voice resolutions expected to be categorised correctly, teammate calls risk being unfairly bundled into “no reply”, creating inconsistencies in reporting. Proposed solution: Keep missed calls grouped as “Closed With No Reply.” Reclassify answered calls as “Teammate replied,” since these are direct agent engagements. Ensure consistency so that both agent calls and Fin Voice resolutions are reflected properly in analytics. Impact: Reporting would become more accurate and trustworthy. Managers would gain visibility into the true volume of customer conversations handled by agents. Support performance could be measured consistently across chat, calls, and AI voice interactions. This small distinction would have a significant impact on reporting clarity, helping teams to better understand and optimise the customer experience.
We tested the Slack integration and it workes fine.I´d suggest 2 things:To make it possible to create a ticket directly from these threads. When setting status to resolved in a ticket (since this wont be possible in a conversation I guess), create a trigger that reacts on the initial Slack conversation with an emoji, eg checkmark ✅ for solved. This would make it easier to see if a thread in Slack already is solved.
The new dataset export page promises, “ It’s faster, more flexible, and supports everything the old version did—and more.” This isn’t true when fields that we were able to add to reports are missing. In the legacy dataset export tool, I was able to add a column that showed up in the export as “Participated (email)” that would list the email addresses of everyone included in the conversation.I’ve attached a copy of a recent dataset export file. Column J has the field that is no longer available.This field is essential to my weekly reporting and analysis on my client conversations. Please add this field to the new dataset export tool ASAP.Thank you,Kieran
We increasingly use AI tools that generate documentation in markdown. The current Articles editor doesn’t support markdown or auto-convert it, which makes updating to Intercom’s own formatting tedious and error-prone.Why it matters:Faster authoring: paste markdown or docs without manual reformatting Fewer formatting mistakes: consistent headings, lists, code blocksWhat would help:Native markdown rendering in the editor, or “Paste as markdown” auto-conversion, or Import/Upload a .md file with mapping to Intercom blocksMarkdown is a basic documentation standard—supporting it would streamline knowledge base workflows for many teams.
There is zero reason to gender callers in the voicemail summary, but beyond that, it’s also incorrect a lot of the time. Example: we had a customer named Aaron call in but the summary said Erin and referred to the call as “she” throughout the summary. It would be better to say “The caller… they.”
Our team does not provide omnichannel support—our agents are only available via phone during specific hours of the day. We would like to track the number of hours each agent's channel availability was set to "Phone" on any given day. This will help us measure whether an agent was available to take calls for the full duration of their scheduled phone shift.
Part of the rationale around the CX score is to replace the need of CSAT scoring. I don’t send CSAT requests out as often as I used to, but I still like to offer the option. However, when chatting with Intercom’s iteration of Fin, I’m asked to leave a CSAT score every time, which seems like overkill on its own, but it also makes the bot frustrating to use, which makes me use it less and less.
Currently, we have 2 distinct types of calls that come in. These calls are routed using a workflow to a specific inbox. If teammates had the ability to be available or unavailable for a specific inbox, it would be a huge benefit to ensure our team is working as efficiently as possible.
I have a SaaS app where each client can customize its domain. For instance, the base domain is app.myname.com, but a client has the domain app.customer_name.pt, When accessing the ticket portal through the base domain, everything works flawlessly. However, when a client with a customized domain tries to access the ticket portal, the cookies aren't transferred, due to the different domains. Is there any way the ticket portal link can accept the JWT that authenticates the user, allowing the ticket portal to create the necessary cookies?
When it comes to setting up the Details tab, we have to direct all team members to update each individual item the way we want it in terms of pinning attributes and apps. We know for each team what we want this to look like across the board and it would be nice if we could bake out a template and link it to the team so that if they are on the team or specific product we could assign them the Details sidebar format that has all the things we need ready to go.Currently we have to tell them every individual thing to pin and add and how to organize it.
When creating a new macro, you can select which team or teams the macro applies to. We often need to select a multitude of these. Every time you select one, it takes you back to the top of the list and you have to scroll back down to the select the next one and this continues for each one thereafter. Even if you type in the key word, that will take you there for the first selection and then it resets for your next selection. It would be nice if I could type in “Dash” which is a key word in all of my team inboxes and I could bulk select all the Dash ones without it resetting everytime.Thank you, this would save us so much time!
When Users/Leads reply to messages in WhatsApp, it would be great to see to which ones they do that. It is a crucial feature that is missing, and because of that miscommunication happens a lot.
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.