Share product ideas and upvotes with our product team
Fin over Email and Chat provides both internal and external knowledge sources, as well as showing the guidance when used throughout a chat. Fin over voice is a little more free, and we don’t have a way to view of guidance was used, or if knowledge material was used. It would be great to internally see in the transcripts, or even summarized in a call summary section when, where, and what guidance and knowledge sources were used through the phone call.
Hello Team, Can you include a guidance counter or indicator or notifier somewhere in Guidance page for visibility?Since the guidance is only limited at 100 total (if you can increase it to 150 limit, that would be awesome), we are trying our best to edit (Voice, Chat and Email) and it’s nice to know that we are nearly reaching the limit.That counter, number indicator or reminder seems a greet addition.
We chose Intercom largely because it allowed us to centralize customer communication in one place, especially through WhatsApp.For us, the value was not just sending outbound messages. The real value was being able to send a message through WhatsApp, have the customer reply in the same thread, and continue the conversation naturally inside the Intercom inbox without forcing the customer into a fragmented experience. That continuity is extremely important to our workflow and to the customer experience.With the recent changes around marketing-classified WhatsApp templates, a big part of that value has been reduced.I understand that some of the underlying limitations may come from Meta. However, from the customer side, what this feels like is that Intercom has passed the operational impact of those limitations directly onto paying customers without providing a truly workable alternative.What makes this even more frustrating is that Intercom’s WhatsApp setup is intentionally closed: the number is managed exclusively inside Intercom, so customers cannot easily adopt a hybrid setup using the same number while preserving inbox continuity. That leaves businesses like ours stuck with an all-or-nothing choice: stay in Intercom and lose important WhatsApp capabilities, or leave Intercom and lose the continuity and inbox experience we originally paid for.This is especially difficult to accept because Intercom is a premium platform. Many of us adopted it specifically for centralized communication, continuity across channels, and AI support inside the inbox. When a change like this significantly reduces flexibility in such an important channel, it becomes much harder to justify the cost.My suggestion is not simply to complain, but to ask Intercom to offer a better path forward. For example: allow more flexibility for customers who still want to use WhatsApp marketing templates at their own risk, provide a more open architecture that preserves inbox continuity, or offer a better hybrid option for teams that depend heavily on WhatsApp. At minimum, I believe changes with this level of operational impact should come with more transparency and stronger alternatives for paying customers.Right now, this feels like customers are carrying the cost of a platform decision they did not choose.
I noticed that conversations in Fin do not auto-close when Fin hands the case off to Salesforce team (FinResolutionState = routed_to_team).We use mail-to-case mostly. When a case comes in in Salesforce and is assigned to the Fin user Fin picks it up. But when it hands over based on procedures, escalation rules, or other logic it does not automatically close the copy of the conversation in Fin. Those remain open what seems indefinitely and require manual closing. This is not really workable in a Fin for Salesforce flow.Please provide the option to automatically close a conversation in Fin when it hands over to Salesforce team (human agents)
I have a new episode of Support Stack live!In Ep. 12, I’m joined by Gabriela Passeri (Knowledge Manager at AutoDS) to unpack how her team rebuilt 235 help articles into 50 AI-ready guides for Intercom’s Fin and hit extremely high early accuracy.We get into: Writing for AI vs writing for humans Why vague language breaks Fin Merging fragmented articles into complete topic hubs Using Claude Projects to enforce consistency If you’re turning on Fin or struggling with resolution rates, this one is foundational.Watch it on YouTube
Hello Team, Can you make this play button, play section on Fin Voice stationary (FIN RECORDING). It’s too difficulty to push that play and stop button while reviewing a long transcript. That play/stop section must be stationary (or can be pinned) so that it doesn’t move when I scroll down and up when reviewing the transcription.
Currently when Fin is replying to an incoming email it does not include the sender’s original message content. We want the option to include the senders original message content included with Fin’s reply. Example: A sr. executive is cc’d on an email to Support and when Fin responds, the executive thinks Fin emailed them directly without context. As Fin is automatically replying to everyone included on the original email thread, they already received the info in the first message from the sender so there is no risk. Along with this not every user will have their emails setup as threaded messages, so it’s possible the first message can get lost causing confusion.
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.
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.
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.
We kindly ask you to add Kazakh and Uzbek languages to the existing list.
Requesting the ability to create a content showcase like an announcement without having to use an image. We are using this to announce registration for a learning workshop, and an image is not needed. But I cannot use the announcement feature because it requires an image. Right now, my only workaround is to use a job listing option to make this work without an image. It works, but not ideal.
It would be SUPER helpful if the Intercom badge/icon in the bottom right could be moved. It’s currently blocking content on certain pages on our SaaS Cloud platform, and it’s not feasible to go through and find and adjust this display everywhere. If the icon could be manually moved (within a certain bounds) it would make many comments and complaints we receive go away.
Add logs for failed procedures in real conversations. Currently if a procedure fails in real time in a case, there is no available information to understand why it has failed. There are many components in a procedure and this is essential to troubleshooting
Problem/Use Case:As a company operating in Germany and the EU, we are legally required to include an "Impressum" (legal disclosure) in ALL business emails, including transactional emails like ticket notifications.Currently, Intercom allows customization of email footers for marketing emails and some other templates, but ticket notification emails cannot be customized. This creates a significant compliance gap, as German law (§5 TMG) and EU regulations require legal information in all business communications, regardless of whether they are marketing or transactional emails.Current Limitation:Ticket email templates are standardized and cannot be modified No option to add company legal information (Impressum) to ticket notification footers This affects all ticket-related emails sent from Intercom to customersRequested Feature:Add the ability to customize the footer of ticket notification emails to include:Company legal information (Impressum) Customizable footer text fields Support for multi-brand configurations with different legal footers per brandWhy This Matters:Legal Compliance: German §5 TMG and similar EU regulations mandate legal disclosures in all business emails Risk Mitigation: Operating without proper legal disclosures can result in costly warnings ("Abmahnungen") and fines Professional Communication: Customers expect proper legal information in all business correspondence Competitive Disadvantage: Other support platforms (Zendesk, Freshdesk) offer this functionalitySuggested Implementation:Similar to the existing functionality for other email templates, add a customizable footer section in: Settings > Workspace > Brands > [Brand Name] > Ticket Email FooterThis should include:Rich text editor for legal information Variable support for dynamic content Preview functionality Per-brand configuration for multi-brand workspacesImpact:This feature would enable EU-based companies to use Intercom's ticket system in full legal compliance and remove a significant barrier for adoption in European markets.
Hi!We have several brands within Intercom and want to make Copilot smarter and more brand-specific. Here are two ideas we'd like to explore:1. Brand-specific filters for CopilotWe'd like to set up filters in Copilot so we can select which brand or teammates should have access to specific internal articles.Goal: Questions and answers vary by brand, so agents should only see content relevant to the brand they support.2. Brand-based past conversation filteringWe need a way to filter each teammate's past conversations by brand so Copilot can pull the right context when providing answers.Goal: Each teammate supports a specific brand and should only access past conversations related to that brand for more accurate assistance.These improvements would help ensure agents get the right information for their specific brand without clutter or confusion.Thanks!
To ensure proper moderation, we rely on a specific tagging structure. We need to configure Fin to automatically apply the relevant tag to the conversation immediately before the chat is resolved/closed.
Fin already allows users to upload images and then analyze those images, which begs the question: Why can’t Fin cite/share images on its own when talking with users?To be clear, I’m not talking about genAI images -- I’m referring to images we’ve already uploaded to Help Center articles alongside written instructions. Our users are visual learners, so the ability to share images (and ideally even videos) during a chat conversation would go a long way here.I’ve noticed Intercom’s version of Fin already includes this functionality, but it isn’t available to Intercom clients. Is this functionality already in the works? If not, can we please prioritize it?An example of how Intercom’s version of Fin currently uses it:
Hi Team,Coming from tools like n8n, the Intercom workflow canvas feels very "stiff". I get that the grid keeps things aligned, but it actually makes organizing complex shops harder than it needs to be.The Problem: Right now, you can’t manually group nodes or add much whitespace. This forces everything into long horizontal chains that are hard to read at a glance. To keep my screen clean, I’m forced to make dozens of Reusable Workflows just to avoid a messy canvas.The Solution: We need a "middle ground". Keep the snap-to-grid so things stay professional, but let us move nodes further apart or group them vertically.Why this helps:Faster QA: You can physically separate "Sales" paths from "Payment" paths to see how the logic flows.Easier Training: It’s easier to spot where a Handover is failing if the nodes aren't all bunched together.Better Organization: Solo managers can organize their "brainstorming" nodes away from their "live" nodes.If we can organize our logic visually, we can build and Deploy better automations without the headache of a cramped screen.Thank you!
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.