Popular Topics

We’re looking for a way to mass import our knowledge base articles from Zoho Desk into Intercom. What’s the best way to accomplish this? 

Hello everyone, I encountered a strange issue while testing user flows for a mobile video editor, similar to the capcut apk tools I've been using. sometimes it takes a long time for the Intercom widget to appear when the app loads larger media files, or it appears after everything else has finished loading.Has anyone else observed that Intercom behaves strangely when handling large files or a lot of ui changes? Is there a better way to queue events to ensure smooth operation, or do you think this is just a performance hiccup? I'd be interested in learning how others have dealt with it.

We’re Intercom customers and we need to build a variation of the checklist on our own page, not inside the Messenger widget. I assumed the most obvious solution would be to consume an API that returns these checklists, similar to how it works with articles. Do we have anything like that? I couldn’t find it in the documentation.This is very important for us!

We are experiencing an issue with the Intercom Android Mobile SDK. The issue is that the in-app message notifications appear underneath the navigation bar at the bottom of the screen, as opposed to sitting directly above the navigation icons.Our app currently uses the SDK version 17.1.1 – however we have been able to reproduce the issue even on the latest version of the SDK (17.3.0). The release notes for 17.2.0 indicate the issue was resolved.  Upon further investigation, it appears the issue stems from the fact our app still uses AppCompatActivity as our base Activity, instead of ComponentActivity which is what the sample app uses. I tested this theory but switching the ComponentActivity to an AppCompatActivity in the sample app and the bug was surfaced there as well. As it would not be trivial for us to switch our base Activity to ComponentActivity, I'm wondering if there are any further solutions currently being worked on for the next release of the Intercom SDK that would resolve

Hello!Has anyone run into this error when using the Intercom Expo plugin (@intercom/intercom-react-native@9.1.1) with an app.config.ts setup?PluginError: Package "@intercom/intercom-react-native" does not contain a valid config plugin.Learn more: https://docs.expo.dev/guides/config-plugins/#creating-a-pluginUnexpected token 'typeof'SyntaxError: Unexpected token 'typeof' at compileSourceTextModule (node:internal/modules/esm/utils:344:16) at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:105:18) at ModuleLoader.#translate (node:internal/modules/esm/loader:534:12)Not sure if this is an issue with the way the plugin is authored or how Expo expects config plugins to behave in a .ts setup.Would appreciate any insight or workarounds others may have found!

Hello there!I’m looking for a to conduct quality assurance on the back-office ticket submission process and track the responsible parties for each ticket. Is there a way to generate a report that captures that info? Currently, we have a boolean attribute that we can toggle, however, we can’t filter through it by the person who submitted it. Any help is greatly appreciated! 

Hi!We are not using Fin anywhere in our product and are not currently interested in implementing it. It’s never been integrated into a workflow and I have never manually turned it on. From our customer’s help chat perspective, they are seeing the following header on the chatbox: It happens when the agent they are speaking to goes idle or if the user clicks on a conversation that was previously closed. Why does this show up? I need to remove this. Our product’s customers have no idea what “Fin” is. I also don’t know what “The team can also help” means.Any help would be so appreciated! Thanks

We’re unable to safely download the Intercom iOS SDK to build with our application using Swift Package Manager. Adding the Intercom Package to our project on a clean SPM cache returns the following error:checksum of downloaded artifact of binary target 'Intercom' (83f26a63832df968d0279ecdd03d8e5039ebf9bb91a9e0b1783cf184101c5a82) does not match checksum specified by the manifest (b87d95eabe645523f417b9051c20151ca7720c93116b163435c2ce1e87aa65ac)fatalError There is a ‘patch’ raised by someone on a fork of the project, but as this is not an official fix by Intercom we do not consider this a safe approach to include your SDKThis looks very similar to an issue on your forum that was raised (and fixed) last year:  This is urgent for us as Intercom provides a critical piece of functionality that our customers rely on to report issues and get customer support.Please can this be fixed as quickly as possible as we are blocked from releasing new version of our app without this.

👋 Hi everyone! Karla here from the Technical Support Engineering team. Today, we’re diving into how to use Custom Actions and Custom Objects to reference People data — the kind of data that sticks with your users across multiple conversations. We’ll walk through setting up a Prescription Tracker workflow — a simple example that shows how to store and display data for each user inside Intercom Messenger. Let’s start with the why. Imagine you’re tracking prescriptions for your customers. If a user chats today about Tylenol, you’d want that stored on their profile. Then, if they return next week about Ibuprofen, that data should build on top of their record — not replace it. That’s what People data does: it acts like a long-term memory for your users. Each conversation can reference one item (the chat about Tylenol, for example), but the People record holds the full history of every prescription that’s ever been added for that user. Let’s start by checking out what my test API returns wh

GET https://js.intercomcdn.com/vendor-modern.1ffdfa4a.js net::ERR_SSL_PROTOCOL_ERROR GET https://js.intercomcdn.com/frame-modern.f3182eef.js net::ERR_SSL_PROTOCOL_ERRORPlease let us know if you need more details

Hi, We are looking to make our Help Center articles mostly limited to just users. We have SSO setup with Entra/Azure and that works fine for access to the backend. Is there a way to leverage Microsoft for access to the Help Center articles so only users that are part of that group can access the articles as well?Thank you!  

Hi Intercom Team,After updating our app to Intercom iOS SDK 19.3.2, several developers on our team have encountered issues where Swift methods (e.g. loginUser(with:), logout(), etc.) are no longer properly inferred or recognized by the compiler.Details Integration: Swift Package Manager (official intercom-ios-sp repo) Project Type: Pure Swift (no Objective-C bridging) Issue:  Xcode only exposes the Objective-C versions of the APIs (e.g. loginUserWithUserAttributes:success:failure:). Error Messages: “Cannot infer type of function call” “No exact matches in call to function 'loginUser'” Troubleshooting Tried Cleared DerivedData and SPM caches Removed and re-added the Intercom package Could you please confirm: The officially supported Xcode versions for SDK 19.3.0? Whether there’s a known issue or upcoming patch related to this Swift interface mismatch when using SPM?

When updating to io.intercom.android:intercom-sdk version 17.2.0If R8/Proguard is enabled the following error occurs on the build:Missing class lombok.Generated (referenced from: io.ably.lib.network.HttpBody io.ably.lib.network.HttpResponse$HttpResponseBuilder.body and 94 other contexts) This does not happen on version 17.1.1  It looks like maybe something changed in the build but didn’t include a rule in it’s consumer-rules.pro?  gemini says: -dontwarn lombok.** may fix it?

I’m working on an email reply automation tool using the Intercom REST API. I’m trying to retrieve the email history — the quoted text that appears collapsed behind the three dots (“…”) when a customer replies to an outbound email we’ve sent them. Three dots for expanding email historyFrom inspecting the network traffic, I can see that this data is retrieved via a private Ember API endpoint:curl 'https://app.intercom.com/ember/inbox/email_history?metadata_id=XXXXXXXXX&app_id=yyyyyyy Is there an equivalent method in the public REST API to access this email history or quoted content?I’ve already tried GET /conversations/{conversation_id}, but the response only includes the conversation parts - it doesn’t contain the quoted email thread (the hidden “three dots” section) in either the parts or metadata.To clarify, customers are replying directly to our outbound emails (sent via our own system, not through Intercom). When we fetch the resulting conversations through the API, we can see t

We are experiencing a critical issue with Intercom integration in our web application.After a user logs in without a full page reload, the Intercom widget appears and lists existing conversations. However:- Existing conversations cannot be opened- Creating a new message often fails- Network tab shows intermittent 403 Forbidden errors with the message: “App suspended”- - Specifically on requests to: POST /messenger/web/conversations/:idIf the user reloads the page after login, everything works as expected:- Conversations open normally- New messages are sent successfullyContext:- We are using the react-use-intercom package for frontend integration.- The app performs a soft reboot after login (without reloading the browser tab). Call shutdown and boot with intercomUserJwt then- When I had this issue it was always because the app_id passed was 'undefined'We are unsure whether this issue originates from the `react-use-intercom` package or from Intercom itself.If you have any suggestions on

Release Date: 04-11-2025 🐛 Bug Fixes Fixed an issue where tapping the close button on an article in a conversation would not dismiss the article. Fixed an issue where tapping on a link in an article would not open the link. Fixed an issue where carousels were not dismissing correctly. Fixed an issue where reactions to articles were not being handled correctly.

Can I please have a code sample on how to implement dark mode (or switch themes) for Android. E.g. something likeimport io.intercom.android.sdk.ui.theme.ThemeMode;Intercom.client().setThemeMode(ThemeMode.DARK);I noted that Dark Mode was enabled on Android SDK v17.0.0

We are having issues when using presentContent for presenting an article, the close button does not close the modal, though it can be closed with a drag down.any workaround?

When using `Intercom.presentContent(.article(id: articleId))` with the current version of the iOS SDK (19.3.0), the app presents an empty view for a second or two and then crashes after outputting the following.*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[IntercomSDKPrivate.ArticleHostingController setContentDelegate:]: unrecognized selector sent to instance 0x12aeec000'*** First throw call stack:(0x1863e28c8 0x1833597c4 0x18647e838 0x18cfb1484 0x18635f4f8 0x1863673a0 0x10915b2f4 0x18645dd64 0x10913e12c 0x10787c63c 0x1078962d0 0x1078b74c0 0x10788c778 0x10788c6b4 0x186384520 0x186336d14 0x186335c44 0x225726498 0x18bcb0ddc 0x18bc55b0c 0x18bd91860 0x10bad5448 0x10bad53bc 0x10bad7308 0x1833aee28)Exception received: NSInvalidArgumentException - -[IntercomSDKPrivate.ArticleHostingController setContentDelegate:]: unrecognized selector sent to instance 0x12aeec000 

Im trying to install the Messenger app in Salesforce Community. I found this old article but it seems incomplete.  Im wondering if I could get help with this integration.  I Edit the Head Markup in the Salesforce Community with the pre-filled script.Then in a lightning component I tried to Instantiate the Intercom instance:import { LightningElement, api } from 'lwc';export default class IntercomApp extends LightningElement { connectedCallback() { try { window.intercomSettings = { api_base: 'https://api-iam.intercom.io', app_id: 'my-app-id-here' }; } catch (error) { console.error(error); } }}I get this warning:frame-modern.812d2c17.js:1 [Intercom] The App ID in your code snippet has not been set. Set it to your App ID found in settings to complete installation: https://app.intercom.com/a/apps/_/settings/web With this message below:[Intercom] Launcher is disabled in settings or current page does not ma

Hello, We are currently using Intercom in our Expo React Native app for customer service messaging. We have previously been using Expo SDK 53 and React Native 0.79.5 with the react native intercom package 9.0.3 and all has been working well.However upgrading Intercom to 9.1.0 or higher is causing some very weird issues for us.Our app streams HLS video where the HLS playlist contains 10s chunks of video which is presented to the user as one long continuous clip. When scrubbing forward in the clip further than what’s been buffered the stream will obviously need to buffer. Our player is using the expo-video package, but we’ve tried with other packages as well such as react-native-video. Now to the issue; Intercom 9.1.0 and higher causes the app to crash when scrubbing forward quickly in the video stream, this problem is only present there and when downgrading Intercom to 9.0.3 it’s working fine again and I can scrub and pause/forward/rewind with no problem and the app is not crashing. I c

When I pull down an example line in the body via API I get something like this:\n<p class=\"no-margin\"></p>\n<p class=\"no-margin\"><b>Can I add in other activities?</b></p>\n<p class=\"no-margin\">Not at this time. If this is a feature you would like, please send us a message.</p>When I push that back up, it adds a new line to below the bolded text. This is also happening above lists as well, but only when it’s below a <p> class.The output looks like this:<b>Can I add in other activities?<b/>Not at this time. If this is a feature you would like, please send us a message.Where the intended output should be<b>Can I add in other activities?</b>Not at this time. If this is a feature you would like, please send us a message.Is this a bug? Is there a way around this?

We are getting a great number of crashes on the Android version 14.1.0.This seems to happen to the conversation_list RecyclerView.You can find the stack trace bellow:java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first. at android.view.ViewGroup.addViewInner(ViewGroup.java:4471) at android.view.ViewGroup.addView(ViewGroup.java:4312) at android.view.ViewGroup.addView(ViewGroup.java:4252) at android.view.ViewGroup.addView(ViewGroup.java:4225) at androidx.compose.ui.viewinterop.AndroidViewHolder.setView$ui_release(AndroidViewHolder.android.kt:97) at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:332) at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:312) at androidx.compose.ui.viewinterop.AndroidView_androidKt$createAndroidViewNodeFactory$1.invoke(AndroidView.android.kt:247) at androidx.compose.ui.viewinterop.

We’re creating the intercom user account from the backend when a new user signs up in our systems. We set up the account with the email ID, name, and mobile number, but not the user ID. [We wanted to keep the email as the single source of truth.]When the user logs in to our mobile app (iOS and Android), we use the same email ID to log in to the intercom using the identified user login option (without a user ID).However, instead of identifying the existing account and logging in, it creates a new account again. Earlier, we faced similar issues with duplicate accounts because a few intercom accounts from the mobile app had logged in with the user ID and email. That created new accounts in the intercom. We resolved this by permanently deleting those accounts and now only using the email ID to log in. But even with this change, the mobile SDK is unable to identify the user and instead creates a new duplicate account again. Could you help me understand the issue better and suggest the right

Bug Report: Android crash due to setNeedsStatusBarAppearanceUpdate in @intercom/intercom-react-nativePackage: @intercom/intercom-react-nativeVersion: 9.2.0React Native: (e.g. 0.81.0)Platform: AndroidReact Native CLIDescription  The Android build crashes on startup due to a null reference to the property setNeedsStatusBarAppearanceUpdate in IntercomModule. Additional Notes Crash reproducible in RN 0.81.0  Occurs on both emulators and physical Android devices. Works fine on iOS. Cleaning android/build or reinstalling pods does not resolve it. Everything worked as expected when I had intercom version 8.8.0