Popular Topics

 Issue DescriptionWe're experiencing signal handler conflicts between Firebase Crashlytics and Intercom SDK in our app. During app initialization, we see multiple warnings in the console:[Crashlytics] The signal SIGABRT has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGBUS has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGFPE has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGILL has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGSEGV has a non-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This will interfere with reporting.[Crashlytics] The signal SIGSYS has a non-Cra

We are experiencing an issue where conversations started via the JavaScript Messenger are not being associated with the company object provided during initialization. While the session ping correctly identifies the active_company_id, the resulting Conversation object via the REST API doesn’t returns companies at all.Steps to Reproduce: Initialize the Intercom Messenger using the window.intercomSettings snippet. Provide a valid user_id, user_hash (Identity Verification), and a company object (including a valid company_id). The Messenger boots successfully; identity_verified is true. Start a brand new conversation as the user. Fetch that specific conversation via the REST API (GET /conversations/{id}).

Hello, according to FIN there is no way to merge conversation besides using the UI. Can you confirm if this is true? Merging conversations via api is a crucial part of our workflow. 

We're experiencing an issue with iOS SDK where AI agent responses are not immediately visible in the chat interface. When a user sends a question and the agent responds right away, the message doesn't appear on screen unless the user navigates back to the dashboard and returns to the chat. This same issue previously occurred in the Android SDK but was resolved with a version update. I attached a video of it. We are using 19.4.1 swift package version.

  SDK Version: Intercom iOS SDK 19.4.1  Platform: iOS 26.1 Integration: Flutter (via intercom_flutter wrapper) Description:  The close button (X) on surveys does not respond to touch events on iOS. Users cannot dismiss surveys by tapping the close button and must complete the survey to proceed. Swiping down to dismiss still works.  Steps to Reproduce:  1. Initialize Intercom with valid credentials  2. Trigger an Intercom Survey (programmatically via presentContent:surveyWithId: or via auto-targeting)  3. Attempt to tap the close button (X) on the survey modal  4. Observe that the tap is ignored and the survey remains open  Expected Behavior:  The survey should close immediately when the close button is tapped.  Actual Behavior:  The close button does not respond to touch events. No c

Hi Intercom Support/Community,We want Fin to trigger an OTP verification flow whenever a customer asks for personal information, before Fin is allowed to call our backend and retrieve sensitive data. What we have today (custom SMS OTP via our backend): Data Connector – Generate OTP: calls our backend, and the user receives a code via SMS. Data Connector – Verify OTP: Fin should ask the user for the code, send it to our backend for verification, and then our backend returns a token. After verification, we want Fin to use that token to access backend information via subsequent calls We tried implementing this via Fin Tasks, but it’s not working well for us.Question: What is the most effective/supported way in Intercom to implement this flow end-to-end (SMS OTP + verification + then allow sensitiv

I’m seeing an issue with a “blur” overlay being left on top of the conversation window when Intercom loads after calling [Intercom presentMessageComposer:NULL] or [Intercom presentMessageComposer:@”text”]This only happens when building on XCode and only when running on iOS 26. Any other combination (e.g. XCode 16 on iOS 26 or XCode 26 on an older iOS version) worksFeels like a race condition in the loading logic perhaps? But hard to investigate as it’s closed source.This happens on intercom-ios versions 16.6.2, 19.4.1 and several in betweenDoes anyone have any information or a workaround?  

When retrieving a conversation via the REST API  GET /conversations/{id}, the initial message that starts a side conversation is not included in the response. Only subsequent replies appear as part_type: "side_conversation_reply" or part_type: "side_conversation_started" as a conversation_part under the  conversation_parts section.Observed behavior: The originating message (e.g., "Hi team, please answer clients query below...") sent by an admin to start the side conversation is completely missing. This message doesn’t appears neither in the api response nor in the main conversation thread in the intercom website, but when we click View side conversation in the main conversation thread in intercom, we can view all the side conversations opened in a separate dialog box.We want to ingest all side conversations related to a conversationId, Is

There is a property that the SDK adds to requests to Intercom. It is called anonymous_session . It appears to keep the API calls to Intercom working beyond the JWT expiry. :Why does this keep authentication alive? Is there a way we can disable it to have more control over the amount of time the API is accessible.

Hello, I’ve got a crash using the Android SDK but can’t say more than the device details and the stacktrace, which I report here.Hope you know more and got to fix it.Intercom Android SDK: v17.3.0Device: Samsung Galaxy A13 - Android 14Fatal Exception: java.lang.RuntimeException: Unable to destroy activity {myapppackagename/io.intercom.android.sdk.survey.ui.IntercomSurveyActivity}: java.lang.IllegalArgumentException: Detected multithreaded access to SnapshotStateObserver: previousThreadId=1163), currentThread={id=2, name=main}. Note that observation on multiple threads in layout/draw is not supported. Make sure your measure/layout/draw for each Owner (AndroidComposeView) is executed on the same thread. at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:6149) at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:6181) at android.app.servertransaction.DestroyActivity

We are sending messages using Intercom’s REST API and after completing a task on our platform side, we would like to inform the customer that:“The team will get back to you on this. Our usual reply time is 1 day. You'll get replies here and to email@example.com.” (sent from William’s Admin ID)However, this causes an unintended side-effect with our auto-assignment rules:Because Intercom treats this as a teammate reply, when the auto-assignment occurs (balanced assignment). We auto-assign conversations based on “waiting longest”, so this causes these conversations to be de-prioritised and skipped, and they will only be picked up again if the customer replies.As a workaround, we curr

There is a vulnerability not fixed even in latest Intercom Android SDK 17.4.2:org.msgpack:msgpack-core should be 0.9.11 or greater|    +--- io.intercom.android:intercom-sdk-base:17.4.2|    |    +--- io.ably:ably-android:1.5.0|    |    |    +--- io.ably:network-client-okhttp:1.5.0|    |    |    |    +--- io.ably:network-client-core:1.5.0|    |    |    |    \--- com.squareup.okhttp3:okhttp:4.12.0 (*)|    |    |    +--- org.msgpack:msgpack-core:0.8.11Could you please update io.ably:ably-android to latest 1.6.1 to see if it fixes the vulnerability?Thanks!More Infoorg.msgpack:msgpack-core(Maven)< 0.9.110.9.11SummaryAffected Components:org.msgpack.core.MessageUnpacker.readPayload()org.msgpack.core.MessageUnpacker.unpackValue()org.msgpack.value.ExtensionValue.getData()A denial-of-service vulnerab

Hi Intercom team, we receive several errors after trying to login a user with attributes using react-native sdk.We check if the user is logged in before making a Intercom.loginUserWithUserAttributes call.A short stack-trace for the error we receive: code: 102,domain: io.intercom.ios.error.network,message: Error in loginUserWithUserAttributes,name: Error,NSLocalizedDescription: HTTP Error: 400 bad requestWe send email and userId to the method call, like this: Intercom.loginUserWithUserAttributes({ email, userId }) Could you help us understand why we still get an error, I’ve run a console.log for both email and userId and both seem legit.

Hi, if there’s a need for a Ops, Customer Support Specialist, I’m available and would love to connect.

Hello, I wanted to report a crash that we have in our application.I don’t know when it happens but it seems to be caused when the SDK try to download an attachment and the file isn’t available.Stacktrace: Fatal Exception: java.io.FileNotFoundException: https://xxx-support.intercom-attachments.eu/i/o/file.pdf at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:255) at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:211) at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:30) at io.intercom.android.sdk.ui.preview.ui.PreviewUriKt$loadFilesAsBitmaps$1$1.invokeSuspend(PreviewUri.kt:252) at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34) at kotlinx.coroutines.D

Hi everyone,We’ve noticed some users reporting that parts of our in-app widgets stop responding after they add third-party tools to customize their experience. While discussing this with a teammate, we mentioned hub script as one example people often try when experimenting with UI behavior.Has anyone seen similar conflicts with Intercom widgets, chat triggers, or tracking after users add custom scripts? What’s the best way to isolate whether the issue is coming from Intercom or from external tools?

Hi everyone,My team is trying to refine our reporting, and we’re running into an issue where our "First Response Time" metrics are being skewed.We are trying to measure the speed of our agents picking up a chat specifically after Fin hands it off.However, we often have scenarios where Fin closes a chat without human interaction. Then, a few days later, we might manually check in on that user or follow up on the closed conversation. Currently, the reporting counts those intervening days as "wait time," which makes our response metrics look inaccurate (showing 2+ day response times for chats that were actually closed).Does anyone have a workaround or a specific filter setup that isolates "Active Fin Hand-offs" vs. "Manual Follow-ups on Closed Chats"? We want to see how fast we are responding to immediate needs, without the data being dragged down by our sporadic follow-ups.Thanks in advance!

I already use Intercom and build up 1 help center site, now i want create new community like community site of Intercom for customer ask something about my product. Can i do that?

Hey everyone! Saw some posts on here about a community and forums feature for Intercom so thought this might help some people out.We built this feature as an Intercom partner at Turf. The integration allows you to very easily add community forums directly inside your Intercom Messenger so your users/customers can create community forum posts directly inside the Intercom messenger widget on your website and in your application/product.Essentially allows you to build an entire community that lives inside your Intercom Messenger widget. If it could be of value to some of you, here’s the link to the integration in the Intercom app marketplace (we have an official partner integration live): https://www.intercom.com/app-store/?app_pack

We use Intercom for chat & articles. Will a forum feature (like Interconnected) become available to us to purchase as well? (BTW - I did search, but couldn't find similar topics, so I apologize if this has been asked a gazillion times already). Paul

Hi,I’ve found an issue with the in-app message preview on Android where the actual message content is not visible, I assume because the text color matches the background color.You can see this issue replicated in your expo-example app from https://github.com/intercom/intercom-react-native/tree/main/examples/expo-example in the screenshot below.I can’t find anything obvious on the Native Android app settings that is causing this issue, so perhaps there is a styling issue in the Intercom SDK?Thanks for your help  

Hi there,I've been looking through Intercom documentation, and it seems like there's something called a Custom Channel and an event called "custom channel base event." However, when I dig a little deeper, it seems that’s somehow connected to Fin?Not trying to integrate a conversation with the Fin chatbot; rather, I am looking to use my own pipeline for our users to interact with my customer service team in Inbox.What I'm looking to do is integrate my custom app as a custom channel in Inbox so that our team can interact through our own managed integration via API.Does anyone know:How to access this capability? If this feature is gated? Whether usage of this feature is billable or if it is included in the standard subscription tier?Thank you!

Hi. We have a crash in our app when pushing a survey to some of our users. We are using version 17.1.0 (latest)This is the crash log → io.intercom.android.sdk.survey.SurveyViewModel.buildContentState (SurveyViewModel.kt:215)io.intercom.android.sdk.survey.SurveyViewModel.access$submitSurvey (SurveyViewModel.kt:83)io.intercom.android.sdk.survey.SurveyViewModel.access$buildContentState (SurveyViewModel.kt:83)io.intercom.android.sdk.survey.SurveyViewModel$submitSurvey$1.invokeSuspend (SurveyViewModel.kt:388)kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:34)kotlinx.coroutines.DispatchedTask.run (DispatchedTask.kt:100)kotlinx.coroutines.internal.LimitedDispatcher$Worker.run (LimitedDispatcher.java:124)kotlinx.coroutines.scheduling.TaskImpl.run (Tasks.kt:89)kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely (CoroutineScheduler.java:586)kotli

Could you share your KPIs and what works best for you when using AI support together with human support? I’ve read a lot of articles, but I’m still not sure what works best in practice. I’d love to hear what you’re using! 😍

Hi there! We’ve recently recieved reports from our support team that carousels aren’t displaying within the app. In our android code, we initialize intercom, and then if we are authenticated, we call loginIdentifiedUser after. This logic has been unchagned for a while and had worked for well over a year. Through debugging we have found that adding an artifical delay (9 seconds) between initialize and loginIdentifiedUser results in the carousesl to show again. Without the delay, login completes successfully (the callback returns a success), but the carousels don’t show.Is this expected behavior, or something on our end? Guidance would be greatly appreciated here  We’re using version 17.4.0 of intercom.