Share product ideas and upvotes with our product team
ProblemWhen handling calls across multiple brands, agents cannot easily see which brand/number the customer is calling. This can lead to mistakes such as greeting the caller with the wrong brand name, creating confusion or a rough start to the conversation.Proposed Solution Allow editing of the incoming call pop-up, or At minimum, display the name of the phone number/brand instead of just the raw number. Optional enhancement: include a brand logo alongside the number name for clearer multi-brand handling. BenefitThis would reduce mistakes in customer greetings, improve clarity for agents, and support smoother conversations—especially in multi-brand environments.Quick sketch of the idea:
Request for the ability for reports to refresh with updated user/company data rather than using snapshots from conversation creation time.If I add users to a company today, I can’t filter for previous months/years data as the users weren’t in the company at the time which is a poor experience.
Hello,We would like to suggest adding a reporting metric that would allow excluding conversations that were reassigned from one agent to another from SLA calculations — or introducing a new metric that measures the actual first response more accurately.Currently, we use the metric “Teammate assignment to first response.” However, there is a challenge:If Agent 1 communicates with a customer and then reassigns the conversation to Agent 2, the system calculates the first response time for both teammates. As a result, the same conversation (same ID) is effectively counted twice in SLA reporting. Additionally, the first response SLA is recalculated after reassignment, which distorts the reporting data.The metric “First response time” unfortunately does not meet our analytical needs.What we need is a metric that calculates the true first response after the initial teammate assignment — something like:“First Teammate Assignment to First Response (initial only)”This would ensure that the first response is counted only once per conversation and would prevent duplicated SLA calculations when chats are transferred between agents.A similar approach is implemented in Salesforce, where the first response is calculated as the actual first reply from an agent, regardless of further reassignments. Implementing something similar would significantly improve SLA accuracy and reporting transparency.Thank you for considering this idea!
Sure, this is more than one idea but… You’ve listed colors as having been implemented but they haven’t (not custom colors for call-out blocks, not font colors). Need a way to share draft articles - infuriating for getting product managers to approve updates before they’re published.Need a way to schedule publication of articles - without this, going in manually going in to publish articles on release day.These are all basic help center features - c’mon :)
Currently, we have to do If Company A has ‘Company Tag A’ , then tag Person with ‘Company Tag A’ and tag Conversation with ‘Company Tag A’ If Company B has ‘Company Tag B’ , then tag Person with ‘Company Tag B’ and tag Conversation with ‘Company Tag B’ If Company C has ‘Company Tag C’ , then tag Person with ‘Company Tag C’ and tag Conversation with ‘Company Tag C’Etc etc etc, and with over 50 clients, that requires an immense amount of work. Plus, the need to go back in every time we have a new client and it’s becoming incredibly messy. Ideally, just setting up one step in a WorkflowIf Company [X] has ‘Company Tag [X]’ , then tag Person with ‘Company Tag [X]’ and tag Conversation with ‘Company Tag [X]’
I would like the option to be able to customise the colour of the search bar to lead to better contrasting between the search bar and hero image to be more aligned with accessibility guidlines.
We’re looking for a feature for our internal team only, where an AI summary or rollup is available when a user reaches out. The rollup will be based on all previous conversations, pressing matters previously discussed, how often the user reaches out, CX scores, NPS scores, tags applied etc. The idea is to have one central place for all information on the user, so every time a team member makes contact with the user (or visa versa), we can have a glace at the summary and adjust the support accordingly. This should provide context for improving the quality of support.
This creates a frustrating user experience - the user gets an email that the conversation has been updated but they cannot see the entire thread within the email. Here is a direct quote from an impacted customer:Good morning - This new chat system makes emails almost worthless because we often can’t tell which issue your answer is associated with. I would imagine you already know this but below is a good example if you do not.Proposed improvement #1: When a user is notified by email of an update to a conversation that they did not see in the messenger widget AND the company settings have conversation history enabled, send the entire history of the conversation. See article below.https://www.intercom.com/help/en/articles/3527623-sending-email-notifications-without-conversation-content-or-historySpecifically, this callout:Important: If the email notification is sent because of user/lead inactivity from a conversation started from the Messenger, then it will only include the messages they haven't seen, not the full conversation history.I am not sure what the business rule / reason for this is. If the config has been set to include the enable conversation history, all of the history should be sent. Proposed Improvement #2: An alternative option might be to include a deep link to the conversation. If the user clicks the link, they are taken to a detailed view of the conversation directly.
We need the ability to mark a ticket after we click it as “unread” so it shines brighter and we know that it still needs to be worked.
When a reader clicks on a photo in a Help Center article, the image loads as a new tab. We’d prefer to keep the reader in the article itself, so if Intercom could support an enlarged overlay within the same article, that would be wonderful. This maintains a streamlined and seamless experience for the reader without having to switch or remove extra tabs.
Can we get a Notes module that compiles all notes that we can filter, sort, and organize? It’s difficult and time consuming to track notes by going to each conversation or ticket to try and find a note that was left previously.
Hello,We would like to suggest improving the accuracy of SLA metrics by removing automatic rounding of time values.Currently, response time values are automatically rounded (for example, 9.6 seconds → 10 seconds). This affects the precision of the data and may distort the actual response time and SLA results.For more accurate analytics and fair SLA calculations, it would be helpful to either: avoid rounding values altogether, or allow displaying time with decimal precision (e.g., 9.6 seconds instead of 10 seconds). This enhancement would improve reporting accuracy and provide more reliable performance analysis.Thank you for considering this suggestion!
Hello,We would like to suggest adding the ability to create shortcuts (or quick-access buttons) for launching specific reusable workflows directly from the conversation view.Currently, to trigger a reusable workflow, an agent needs to open the reusable workflow menu and search for the required one using keywords. While this process does not take much time, it could be significantly faster and more efficient if agents could create dedicated shortcuts for the most frequently used workflows.For example, our Support team regularly uses reusable workflows for: Closing conversations Applying internal regulations “Please wait” messages Sending apologies Granting individual promo using Data connectors Having customizable buttons in the bottom panel of the chat that instantly trigger selected reusable workflows would noticeably speed up daily operations and reduce manual steps.It would also be very helpful to have a dedicated greeting button, so agents do not need to type the same welcome message manually each time.Overall, this enhancement would improve efficiency, reduce repetitive actions, and optimize agent workflows.Thank you for considering this idea!
As I have been using Intercom for writing Articles, I find some of the basic formatting options missing. For example, Underline option. Shouldn’t this be a must-have feature rather than good-to-have to support the rich formatting options that every editor provides!
We would like to suggest adding Excel (.xlsx) as an export format for reports, in addition to the existing CSV option.Currently, reports can only be exported in CSV format. While CSV is useful, it often requires additional formatting before analysts can comfortably work with the data in Excel. Providing a direct .xlsx export would allow teams to immediately build pivot tables, create charts, and analyze data without extra conversion steps.Adding Excel as a native export format would simplify workflows, save time, and improve the overall reporting experience.Thank you for considering this idea!
The current workflow to pass data into a Salesforce case is clunky and not intuitive. Having to pass data between attributes via data connectors and potentially creating duplicate attributes across objects (person and conversation) is not a great experience. Additionally, the mapping between Attribute Name and Salesforce Field Label is brittle because Salesforce Field Labels are not unique. A deterministic and explicit mapping of any data point in Fin would be the best implementation. See attached image as mock up of what this should look like.
We would like to suggest adding the ability to enable or disable notification sounds for specific conversations.Our teams handle a high volume of chats, and there are situations when a client may send multiple frequent messages within a single conversation (for example, spamming or sending many short follow-ups in a row). In such cases, constant sound notifications from that one chat can be very distracting and affect productivity.It would be extremely helpful to have the option to mute notifications for a specific conversation while keeping it open and active. The main idea is to allow users to mute individual conversations instead of disabling sound for all chats or browser tab.This feature would help teams stay focused while still ensuring that new incoming chats are not missed.
We have been recently testing the Inbox AI Auto translate and encountered success only in Spanish, Testing against German, French, Bulgarian have all brought unusable results. Sentence and paragraph structure are poor, formality is not always correct, translation is very literal which results in the output translation making little sense thus unfortunately unusable. Are there plans to improve the translation for Inbox AI, if so any timelines on this?
In some cases user might have been contacted proactively by our team already and in case same user is opening a new conversation thread with Fin, Fin can’t see or advise the user that we already contacted them about this issue. It’d be helpful if Fin could see all open and recently closed conversation threads with the specific user.
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.