Unanswered questions

Hi! I am curious to learn more about how Fin ingests long form content that is not necessarily written in a way to support it (i.e Content chunking, formatted for Ai readiness). Looking to learn if Fin has the ability to ingest something like an owners manual and able to answer any questions related to it without creating a specific support article on a topic related to the owners manual. 

We’d like the ability automatically assign a team inbox when a teammate initiates an outbound conversation, ideally based on the From email address used.For example, a conversation sent from billing@company.com should automatically belong to the Billing inbox from the moment it is sent, regardless of whether the customer replies.Currently, teammates must remember to select an inbox manually. If they miss that step, outbound conversations can sit without a team inbox, creating gaps in visibility, ownership, and follow-up.Requested behavior: Allow admins to map each outbound From address to a default team inbox. Apply the assignment when the initial message is sent, without waiting for a customer reply. Preserve an inbox explicitly selected by the teammate. Provide a fallback team inbox for outbound conversations without a matching address rule. The core requirement is that every teammate-initiated outbound conversation has an assigned team inbox immediately, so none are left witho

Few of our identified users on iOS see “Something went wrong” when user opens the Messenger.  Calling Intercom.logout() and then logging the user in again fixes it. We cannot reproduce it on demand, and no error reaches our app.EnvironmentIntercom iOS SDK via SPM - 19.5.7. Some affected builds were on 19.7.2. iOS version: > iOS 15 Identity verification: enabled. We call Intercom.setUserHash after loginUser(with:). Setup: setApiKey at launch, loginUser(with: ICMUserAttributes) with userId, email and company after sign-in, then Intercom.present() from a Settings → “Chat with us” row.ExpectedIntercom.present() shows the Messenger for a logged-in user.ActualThe Messenger opens with a “Something went wrong” error screen.ObservationsLogging out of our app (which calls Intercom.logout()) and logging back in fixes it loginUser’s completion handler returned no error that we could observe.Lifecycle, in the order our code runs itAt launch and after sign-in, we call Intercom.setApiKey(_:forAppI

Hello everyone, I have been running into an issue integrating the Messenger widget on our site, where the chat launcher randomly fails to appear for visitors. The script is embedded in the header, but in several modern browsers, the boot sequence appears to stall before establishing the connection.We have reviewed our domain settings and CORS headers, yet the intermittent connection drops continue to occur during high-traffic periods. For more details on our client-side setup and console logs, please let me know what specific environment information would help diagnose this.

We've recently been experiencing an issue with the Data Export API.The export jobs are submitted successfully, but when polling their status, the API returns in_progress a few times before eventually returning the following error:{ "errors": [ { "code": "service_unavailable", "message": "Sorry, the API service is temporarily unavailable" } ]}The transition from in_progress to this error often happens within just a few minutes.An example export job ID is 8ejdlg23rdolf8l2.This has been happening consistently with recent export request.

Hello everyone, I have been working on integrating the Intercom Web Messenger into our web platform, but we are experiencing unexpected behavior during dynamic page transitions. Specifically, the chat launcher periodically fails to mount or becomes unresponsive after navigating between client-side routes, forcing users to perform a full page refresh before the widget becomes functional again.We first detected these intermittent display glitches while troubleshooting identity verification and event logging on the website, where custom user attributes appear to delay script execution. Has anyone faced similar timing or lifecycle issues with the JavaScript SDK in single-page environments, and what is the best practice for cleanly updating or re-booting the Messenger instance across route changes?

The search bar on the modern Help Center template only runs once a query has at least 3 characters. Intercom confirmed this limit is fixed, not configurable, and the same for every language.A 3-character minimum works for English, where 1–2 letter inputs rarely carry meaning. In Korean, Japanese, and Chinese, a single character carries much more meaning, and many of the most common support search terms are exactly 2 characters:- Korean: 플랜 (plan), 가격 (price), 결제 (payment), 환불 (refund), 계정 (account)- Japanese: 料金 (fee), 解約 (cancellation), 請求 (billing)- Chinese: 价格 (price), 退款 (refund), 账户 (account)Today these queries return nothing. Customers assume the article doesn't exist, then contact support or give up. Adding a particle (e.g., 플랜이) makes search work, but customers have no way of knowing this.Requested change (any of these would solve it):1. Lower the minimum to 1–2 characters for CJK queries2. Apply the minimum per Help Center language3. Make the minimum length configurable in Hel

The search bar on the modern Help Center template doesn't return results for queries under 3 characters. For example, searching "플랜" (plan) or "가격" (price) returns no results, while "플랜이" or "가격은" (the same root word with a particle attached) works fine.This minimum length may work reasonably for English, where 2-letter inputs are often low-signal, but it's overly restrictive for Korean, where 2-character words are frequently complete, high-value search terms. A language-aware minimum, or a lower threshold for CJK queries, would better serve non-English Help Centers.Could you let us know if this minimum length is configurable, or if there are plans to make it language-aware?

Optically - the word “Sent” is too similar to “Seen” and harder to quickly distinguish when navigating through conversations. It’s also not very descript - does Sent mean delivered??Instead of “Sent” some other suggestions…-Sending-In transit-In route-Pending delivery-Delivered

Hello,  We are starting out with intercom and struggling to verify outbound messaging, I used auto configuration and everything got updated in Cloudflare, but I am still seeing Warning on Outbound Messaging, here is what I am seeing https://ibb.co/s94ZrnSq (Not sure why I cannot upload image here)I can manually configure it in cloudflare, but I don’t know what are TXT record values, is there anyway to see those values so I can manually change in cloudflare?ThanksKets  

These quickly clog up tickets and also cannot be removed. This should be a very thin line with text “Message delivery failed” with a button to expand into further details. Multitple failed messages should be compacted into the the same block.  

We recently integrated the Intercom Messenger JavaScript snippet onto our website to handle setup queries and live troubleshooting for users downloading our custom launcher builds. However, we have noticed inconsistent behavior where the chat bubble delays the initial page load on low-spec mobile browsers and occasionally fails to initialize altogether inside embedded webviews.Alongside the load delay, we are seeing related tracking glitches where custom user attributes and visitor session tags drop completely before reaching our team inbox. We also ran into strict Content Security Policy warnings in our console regarding some dynamic assets requested during the boot phase, which seems to disrupt the overall launcher guide display.Has anyone encountered similar performance and CSP conflicts when deploying the Intercom Messenger across a gaming utility website? I would love to know if there are recommended asynchronous initialization patterns or lightweight configuration workarounds tha

We're currently experiencing compatibility issues when using Intercom alongside other push notification platforms, and we'd like to understand whether FID support is on your roadmap.If a migration is planned, could you share an estimated timeline?Thanks!

Hey Everyone!We have data of conversation, conversation parts, contact, and company to our datawarehouse, extracted using Intercom API.Now, we are trying to replicate one table that our client has built in the Intercom Reports which basically shows the conversation with bug tag across the companies. It’s a really basic table, containing the following columns:Conversation ID Company ID (from Company Standard Attribute) Company Name (from Company Standard Attribute) Conversation Tag Some more additional fieldsNow, we are able to create the most of the fields from the API data. However, we are facing the issue for the Company ID and Company Name.For example, in Intercom report table, a single conversation has 8 companies (as comma separated string) in the Company ID and Company Name. While in datawarehouse we have around ~52 companies.For the datawarehouse logic, we are using contact as the a bridge to map the conversation data with company. In datawarehouse the flow is Conversation → Con

When an agent starts a new outbound email (Inbox → + → Conversation → Email), the ID field in the sidebar shows “—” until the email is sent. Our agents need the reference number while writing the email, to log it in our back office. Today they have to send first and then go back to copy it.The only way to get an ID before sending is to create a Customer ticket first, which is much slower than a simple email.Request: give a new outbound email its conversation ID as soon as it’s started, and show it in the sidebar before sending, the way Freshdesk shows a ticket number from the start.

Why is there no option in workflow builder to Expand all paths, similar to Minimize all paths option?There is only Expand all paths in view, but we have to scroll horizontally and click on it several times to expand all the steps and have a complete overview.

Hi everyone, I'm running into an issue while configuring the Intercom Messenger widget to trigger based on dynamic session states. We recently added the standard JavaScript snippet across our website to offer quick help for users encountering setup or download issues, but the chat bubble frequently fails to load for visitors using specialized Chromium-based desktop wrappers.Alongside the initialization hiccup, user attributes like operating system and client build numbers are either delayed or drop out completely before reaching the conversation inbox. Has anyone experienced similar script conflicts or timing issues when running Intercom on a dynamic web application, and is there a recommended way to delay the boot script or adjust Content Security Policies to ensure stable tracking?

Hello everyone,I’m glad to be part of the Intercom Community. As a new member, I look forward to learning from other users, sharing ideas, and participating in discussions about customer communication, support experiences, and customer engagement.I believe that exchanging knowledge and real-world experiences can help us understand different challenges and find better solutions. I’ll make sure to follow the community guidelines, respect other members’ perspectives, and keep my contributions helpful and relevant.I’m excited to connect with fellow members, learn how they use Intercom in their daily work, and discover new ways to improve customer interactions.Thank you, and I look forward to learning and contributing to the community!

Hey everyone 👋 I'm an indie founder building ChatShield, a tool that helps support teams identify potentially risky conversations across their workspace not just AI chatbot replies, but human-agent conversations too. For example, an agent might accidentally promise an unauthorized refund, make an incorrect pricing commitment, or share information they shouldn't. I'm trying to understand how Intercom teams currently catch these issues. A few questions: - Do you manually review conversations, use internal QA, or have another process?- Are mistakes by human agents as much of a concern as AI-generated replies?- Would automated flagging of conversations for human review be useful to your team? I'd genuinely appreciate hearing how you're handling this today. I'm also looking for a few Intercom teams willing to test ChatShield and give honest feedback. Product: https://chatshield.cloud/ Thanks!

TextSpeed WhatsApp Business API helps businesses connect with customers through automated, secure and scalable WhatsApp communication. Use the API for notifications, customer support, promotional campaigns, order updates, authentication and chatbot conversations while creating personalized customer experiences at scale.

Product Design Services | OEM Engineering Partner | DFM & Hardware Engineering - DEM Manufacturing: An engineering extension of your team. Get U.S.-based product design services with custom electronics, hardware engineering, and DFM built in, moving you from concept to production faster.

It would be wonderful to have a Intercom native feature where you could set up a alert threshhold feature on a chart that informs dedicated stakeholders if the volume was hit (without requiring periodic review). Examples might be: - If CX score hits X% - If conversation volume exceeds X conversations - Etc. We have a lot of busy stakeholders managing multiple different tasks, and things can fall below the radar. But this way you could draw peoples attention, without them having to cut out time daily to review dashboards to check performance across different releases.

Hello,We use Intercom for customer support for our SaaS product and would like to be able to display the exact time under each message (for example, “3:50 PM” or “8:31 AM”), instead of the elapsed time (“16 hours ago,” “2 days ago”).We know that the date and time are visible when you hover over a message, but having to hover over every message makes it less convenient to review conversations, especially when trying to understand the time intervals between two replies.Would it be possible to add a setting that lets us choose between the current relative display and a permanent display of the exact date and time?Is this option already on your roadmap?Thank you!Wendy

hi,I was wonderig if there were plans to allow us to use the Free Salesforce Integrations licenses for integration between Salesforce and Fin.Thanks

Description:We run several brands in one workspace, with chat, email, overnight Fin coverage and multiple languages. These are the gaps we keep hitting, roughly in order of impact:Brands and what customers seeA customer-facing name per brand, separate from the internal brand name. Brand names must be unique, so ours include internal suffixes. That internal name then shows in the Messenger header, in the “[Teammate] from [Brand]” sender line of chat replies sent by email, and in the email footer. Setting a display name on the sending address doesn’t change it. Editable footer and wording on conversation notification emails without building a full custom template for every brand. Brand detection for BCC’d emails. Customers often email many companies at once and put our address in BCC. These arrive with the default brand, and workflows can’t set the brand automatically.Fin AI AgentControl over the transition line when a procedure starts (“Let me look into that for you…”). It’s sent before