Share product ideas and upvotes with our product team
Bitte ergänzt die Möglichkeit, Knowledge Hub-Inhalte anhand der Artikel-ID zu durchsuchen. Aktuell funktioniert die Suche nur mit Stichwörtern (Titel oder Text) und Filtern, was langsam ist, wenn man die ID bereits hat und direkt zum exakten Artikel springen möchte. Eine einfache Suche nach der ID würde die tägliche Content-Verwaltung deutlich schneller und effizienter machen.
Currently, Fin's content recommendation feature analyzes conversations of any age when suggesting article edits, including conversations that are a year or more old. For fast-moving products where features and functionality change frequently, this leads to outdated and incorrect recommendations.Request:Add a setting to limit the age of conversations that Fin reviews when generating content recommendations. Ideally, this would allow us to restrict recommendations to conversations from the past 6 months (or a custom timeframe).Why this matters:Recommendations based on year-old conversations suggest edits that no longer reflect current product functionality This creates extra work reviewing and dismissing irrelevant suggestions For products with frequent updates, only recent conversations provide actionable insightsExample:I recently received a recommendation to edit a help article based entirely on conversations from approximately one year ago. The suggested changes were completely incorrect because our product has evolved significantly since then.
I can add multiple external links but only one Ticket links inside the Messenger Box.I would like to have the ability to show different tickets depending of the URL.Also cannot create an app that call the ticket form
Bitte ergänzt die Möglichkeit, Knowledge Hub-Inhalte über die Artikel-ID zu durchsuchen. Aktuell funktioniert die Suche nur über Stichwörter (Titel oder Text) und Filter, was langsam ist, wenn man die ID bereits hat und direkt zum exakten Artikel springen möchte. Eine einfache Suche nach der ID würde die tägliche Content-Verwaltung deutlich schneller und effizienter machen.
Currently, when a ticket is in Waiting on customer, any reply from the customer automatically changes the ticket state back to In progress. In many cases the reply doesn’t actually unblock the ticket. For example, a customer might say “Perfect, I’ll send the file tomorrow” or “I’ll book the meeting later today.” Even though the required information hasn’t been provided yet, the ticket still moves to In progress automatically. It would be very helpful to have an option to disable this automatic state change, so the ticket can remain in Waiting on customer until a teammate updates it manually. This would make ticket workflows clearer and prevent tickets from returning to active queues before the needed information is actually received. We use Intercom in our app to onboard customers and guide them through a process with our team, and ticket statuses are an important way for both sides to understand where we are in that process.
When customers send screenshots in Intercom conversations, images can be opened but cannot be zoomed in.This is a major limitation for support teams, especially for: Technical troubleshooting (settings, step-by-step flows, small text) Customers using smaller screens Accessibility (older users or users with visual impairments) In many cases, screenshots contain critical details that are simply unreadable without zoom, which slows down resolution, increases back-and-forth, and creates frustration on both sides.Being able to zoom in/out on images and or being able to put the image in landscape format directly in the conversation would: Improve customer experience Speed up issue resolution Reduce unnecessary follow-up messages Significantly improve accessibility This feels like a basic but essential feature for any support-heavy Intercom setup.Would love to see this added 🙏
It would be ideal to schedule an article to “go live” or be published at a specific time. This is a fairly common feature on other documentation platforms. Use case wise: We have specific times that features are released or courses ares released. If we can schedule the articles, we can ensure they are published as soon as the course or feature is launched.
Currently, articles in the Intercom Knowledge Base can only be saved as drafts and published manually. Automated publishing at a specific future time (e.g. in parallel with a product release) is not possible.Requirement:It should be possible to schedule the publication time of an article or news item in advance. The article should automatically go live as soon as the defined time is reached, without any manual intervention.Target Functionality: Ability to define a future publication date and time when creating or editing an article. The article remains in “scheduled” or “draft” status until that time. Automatic publication at the specified time. Optional: Notification (e.g. via email or within Intercom) when the article has been successfully published automatically. Rationale / Benefits: Facilitates preparation for releases and time-based communication activities. Reduces manual effort and the risk of delayed publications. Supports consistent publishing processes, especially in larger teams or during international rollouts.
Conversation data as Bulk export through the Intercom workspace UI
We would like the banner impression data to be exposed through the Intercom API or the Intercom MCP. We implemented banners as a node code solution and now we are unable to attribute the impression/views without this data.
It would be fantastic to be able to remove, or at least hide from public view, the numeric ID attached to each help center article.For instance, instead of having: https://support.organizationname.com/en/articles/14463812-name-of-articleit would be: https://support.organizationname.com/en/articles/name-of-articleThe numeric ID, to me and others in my organization, makes the URL of an article look less straightforward.
It is increasingly common for websites to not just have a sticky chat bubble, but to embed fin on a specific location on a web page.Features: Insert Fin by URL targeting on a page Ability to adjust prompt based on attributes or URL Some customization around UXExamples Include: Amazon Product Pages “ask a question” SimpliSafe “ask about this product Walmart/Target are testing out similar features Expedia
When our service receives the contact.merged webhook, we update records related to the previous lead user.In the current version (2.14), the webhook does not include the previous lead ID.You can find a more detailed description here:
We calculate our CSAT based on average 1-5 scale, not as a percentage of positive ratings, and I would want this to be an option inside Intercom without the need to exporting data every x amount of time. For example, if an agent receives four 5-stars and one 1-star, I want the csat calculation to be = (4*5 + 1) / 5 = 4.2.
It would be extremely helpful to our team if we could use Teammate Availability as a condition in our Messenger and Phone workflows. This would allow us to route conversations to a different option if, say, zero teammates are set to Active.We are a small team, so it sometimes happens that no one is available to take chats or calls during office hours. To prevent customers from having to wait unnecessarily for someone to respond when no one’s available, we have to manually pause our standard workflow and activate an “away” workflow if no one is Active. This takes time and a lot of steps for multiple personnel. Other phone/chat products we’ve used have had the ability to route messages based on agent availability, which simplifies things enormously.Note: for Phone workflows, Talking should be included in the list of Teammate Availability choices, since that is distinct from Away. We need to be able to send callers to VM if no one is Active but send them to the queue if at least 1 teammate is Talking.
It would be great to have the ability to resize images in macros and the reply box.
In Inbox views, some columns can’t be sorted right now, even though the table is configurable and columns can be rearranged or hidden. It would be really helpful if clicking any column header would sort that column (ascending, descending, and/or alphabetically), so we can organize conversations by Assignee, Company, Team, and any other column we add. We want to sort by Assignee, Company, Team, and any other column we add, so teammates can scan and find the right person or company faster.
I have some customer that would like the option to make the chat window full screen for some conversation.
It would be great to allow users to have multiple tickets open at the same time, but restrict them to only one active chat conversation. This way, users can have several ongoing support requests tracked as tickets, whilst still being able to reach the team via chat — but not spam multiple simultaneous chats. The challenge is that Intercom's native "prevent multiple conversations" setting treats tickets and conversations as the same object, so having any open ticket blocks users from starting a chat entirely.It would be amazing for the restriction to apply only to chat-type conversations, leaving tickets unaffected.
For VIP/Ent customer email emergencies, the key is to avoid relying on the “inactive customer follow-up” timer, since email follow-ups are only configurable in hours (1 hour to 7 days). [1] [2]Request: to have more flexibility with the follow up timer and use minutes instead of hours.Use case: we want to add Fin also to handle Ent emails and if there's an emergency we can't wait 1 hour for Fin to escalate/hand off to our inbox.
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.