Share product ideas and upvotes with our product team
Allow ends users (our customers’ customers) to search the pervious conversation via keywords in messenger. So any conversations that contain such keywords would show up. One of the customers’ end user requested so that they can easily search and refer to previous conversation when talking to the support agent.
Present state - Selecting to edit an article forces all collapsible sections to expand Request - Instead keep collapsible sections collapsed once you select editThis helps the amount of scroll needed when I am editing, saving, and publishing.
It would be incredibly useful if Intercom Webhook topics included events for article creation and editing. This would allow my team to automatically trigger tasks in our project management system (e.g., via Zapier) instead of manually tracking every content update. Right now, the lack of these event types in Intercom prevents us from automating what could otherwise be a simple and efficient workflow.
We currently use outbound messaging to greet all new users and guide them to available support channels (Help Center, chat). However, the message can only be sent from a teammate, even though Fin can handle replies if the user responds, which they often do.For the sake of transparency and a better user experience, it would be great if we could set Fin as the sender. This way, users know they’re interacting with an AI from the start, rather than expecting a human response. At the moment, the only alternative is to explicitly state in the message that our bot will be responding, which can come across as a bit tacky.
The current ticket report is ok but has limitations related to tracker tickets. 1 tracker ticket is linked to multiple conversations. It would be great to see in the reports how many conversations have been linked to tracker tickets over a given period. This gives a more accurate impact of the issues related to tracker tickets. For example, if there were 5 tracker tickets last month, there can be a big difference in impact if only a handful of conversations were linked to the tracker, versus if 20 or 30 conversations were linked to each ticket. It would be good to be able to see this in the reports. Alternatively, having a way to automatically tag a conversation when it is linked to a ticket would help generating custom reports for this.
Hello everyone, I’d like to request the ability to hide the names of Back-office ticket types that are shared with customers. These names are currently internal and, from a legal standpoint, could be used as evidence against the institution. Since we currently have around 200 Back-office ticket types, it would be unfeasible in the short term to rename or rewrite them, and doing so could also cause confusion and errors among the customer service agents who create these tickets. Thanks!
Conversations that only have a communication from the customer without reply from the customer, are not considered actual conversations and do not appear in reports. A conversation is considered a conversation when at least 1 communication from a teammate AND a communication from a customer exists. Only then will the conversation appear in reports. (According to Intercom Support)But in our environment we often proactively send conversations to customers, for example informing them we have seen an issue in our monitoring systems and have already solved the issue. It is mandatory that these conversations appear in the customer reports as it shows that we are proactive and solve issues for customers before they even notice them.
When manually adding a new Lead in Intercom, the form currently only includes fields for Name and Email.However, for many teams — especially those using phone or WhatsApp as primary communication channels — the Phone Number is just as essential.It would be very helpful to have a Phone Number field available as well — even if it’s optional.Key benefits: Improve efficiency: Teams can capture all relevant contact details upfront, avoiding extra steps or edits later. Enhance data consistency: Ensures that phone-based communication channels (like WhatsApp integrations or call workflows) have accurate data from the start. Support real-world workflows: Many sales and support teams engage leads via phone or messaging apps before email, making this field highly practical. This small improvement would significantly streamline lead management for teams that rely on multi-channel communication, while maintaining flexibility for others who don’t use phone contact information.
Currently Inbox Views are working solely on conversation attributes and conversation data attributes. It would be so much more effective if we can filter buy company/user data as well... Why?(a) we need to work really hard to push user/company data into the conversation data, it makes everything much less flexible.(b) it makes data sticky. If I edit company data (manually or by api after user/company product behavior) , the conversation data attribute doesn't change.I assume the initial setup was do to resource management, but I think you can afford some more resources on it, no?
Overview: I propose adding an "Undo Send" feature to the Intercom chat tool, similar to the feature available in Gmail, where users can recall or undo messages for a short window of time after sending them. This would greatly enhance user experience and reduce potential errors in communication.Problem Statement: In real-time communication, users sometimes send messages prematurely or with errors (such as typos, wrong information, or unintended content). Currently, once a message is sent in Intercom, there is no way to retract it. This can lead to confusion, miscommunication, or embarrassment, especially in customer service environments where accuracy and clarity are paramount.Solution Proposal: Introduce an "Undo Send" functionality that provides users a brief window (e.g., 5-30 seconds, configurable in settings) to recall or unsend a message after clicking "Send." During this window, the message remains in a pending state and can be canceled or edited by the user.Key Features:Undo Timer: A customizable time window (default to 5 seconds, adjustable up to 30 seconds) during which the user can undo the sent message. Visual Feedback: Display a temporary notification (such as a snackbar or toast message) after sending, showing an "Undo" button. Message Pending State: While the timer is active, the message will not be visible to the recipient, giving the sender time to review or cancel the message. Setting Customization: Allow users to toggle this feature on/off or adjust the time window for undoing messages. Application Scope: This feature should be available for all chat types (automated, manual, or customer-initiated conversations).Benefits:Reduces errors in communication by allowing users to fix mistakes before the recipient sees them. Provides peace of mind to users who may hesitate before sending important messages. Enhances customer satisfaction by ensuring more polished and accurate communication.Conclusion: The "Undo Send" feature would significantly improve the user experience within the Intercom chat tool by providing a safety net for users. This is especially valuable in customer support environments where clear and error-free communication is essential.
I would like to have a tab in the Testing section for Fin Voice that is similar to the one we have now for Fin Chat/Email. Including the Evaluate Answer feature would speed up the time it takes to manage changes to guidance by showing us exactly what content is being used to craft replies. I want to be able to batch test questions from customers that come through over phone calls as there are differences in what customers ask over the phone, and differences in how they respond to Fin from the moment the call starts. It would also help track how the changes made in voice guidance affect how Fin responds over key topics as Fin responds differently over voice.
Hi, I was wondering if it’s possible to ad a pop-up like a post for the news item. When we use the post to tell the customer ; there is something new- the information is at 2 places at the same time (in the news AND in the conversation). So by suggesting a pop-up like a post , it would helps your team to reach more customer.
In the chat layout, when switching from my inbox to the team inbox and vice versa, it automatically opens up the first ticket in the inbox. This is not only visually a lot, but will also lead to teammates thinking that someone else is looking into that ticket when in reality, there just isn’t a way to close out of the view/not be viewing a ticket. Can there be a way to turn this off?
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.