Popular Topics

We want to configure the layout of Apps in the Details panel for team inboxes. At the moment each team member can update their personal view, but we want to set up a standard layout for our team. I haven’t found a solution yet in the documentation. Is this possible at the moment or will this need to be a wishlist item?

We are utilising the 6.0.2 version of the capacitor-community/intercom package, which is using a 12.x version of the Intercom Android SDK internally.What seems to be happening is that when the plugin registers it is making an initial call to Intercom (probably for the reasons outlined in this thread: Our JS implementation code does not do anything until the user logs in. At which point we call `setUserHash` and `registerIdentifiedUser` respectively. We then have a button that launches the intercom bubble (displayMessenger).On a fresh install an Android 15 this works fine. We can login, click the button and intercom launches. On Android 16 it doesn’t. If you exit the app and restart it works fine from that point onwards.When monitoring the logs on the Android 16 device, with a release build, we get this error immediately upon app launch, before the user has a chance to interact (or even grant permissions for things like push notifications):Failed to register or update user: {"type":"err

Hi everyone, I’m a WFM employee assigned to a new client who’s using Intercom, and it’s my first time to use it. I am looking into building a payroll report, currently they pay the employees just based on how long they are logged in which I can easily find the report in intercom (Adherence Report), however, they wanted to change it and reference it with their schedules. The only way to do it is to use the Login/Logout report of each employee which shows what exact time an employee logged in/out. I can’t seem to find the report in intercom. Is there anyone here who happen to find that report and if you can share where in intercom can I get it?

Hi,It appears that the Intercom CDN links synced to Zendesk via the ticket integration have a short expiration period of under an hour. After expiration it is not possible to view the images in Zendesk directly.Is there a setting in Intercom to extend the expiration or is it possible to remove the expiration?Thanks!

This is specifically for the followup camera request (“<app> does not have access to your camera”) after declining the first camera request. From Apple:Guideline 5.1.1 - Legal - Privacy - Data Collection and StorageThe app encourages or directs users to allow the app to access the camera. Specifically, the app directs the user to grant permission in the following way(s):- A custom message asks users to reconsider their decision after they deny the permission request.Permission requests give users control of their personal information. It is important to respect their decision about how their data is used.Next StepsTo resolve this issue, please revise the permission request process in the app to not ask the user to reconsider denying permission.

Hello,It seems that the @intercom/intercom-react-native is not compatible with Expo SDK 53. it fails to build with the following error:> 1 | #import <IntercomModule.h> | ^ no macro named 'import' 2 | import Expo 3 | import FirebaseCore 4 | import ReactAre there any plans to support it?

Is there a way to automatically trigger a Slack notification whenever a new lead is captured in Intercom? I want my team to get instant alerts in a specific Slack channel whenever a lead submits a form or starts a conversation (Read More). Are there any built-in integrations or recommended workflows to achieve this?

 Intercom SDK version: 16.0.3 Xcode: 15.0 UIGraphicsBeginImageContext() failed to allocate CGBitampContext: size={0, 0}, scale=3.000000, bitmapInfo=0x2002. Use UIGraphicsImageRenderer to avoid this assert.0CoreFoundation __exceptionPreprocess 1libobjc.A.dylib objc_exception_throw 2Foundation -[NSMutableDictionary(NSMutableDictionary) initWithContentsOfFile:] 3UIKitCore _UIGraphicsBeginImageContextWithOptions-[Ullmage(ICM|mageUtils) icm_resizelmageToSize:]_51-[ICMReactionsViewController displayOption:inView:]_block_invoke_2

I need to measure the duration it takes for specific contacts to reply after one of our teammates sends them a message. Intercom's standard reports focus on our team's response time, but we need the reverse perspective – the customer's reply time to our messages. This is crucial for identifying unresponsive contacts who may need their details updated. Is there a built-in report, feature, or a recommended method within Intercom to easily achieve this specific type of response time tracking and potentially flag contacts based on their responsiveness?

Hello Team,We recently updated to the Intercom iOS SDK 17.0.1 and started getting a crash in the SDK with the following stacktrace.  Crashed: nexus.reachability0  libobjc.A.dylib                0x4e30 lookUpImpOrForward + 881  libobjc.A.dylib                0x34c4 _objc_msgSend_uncached + 682  Intercom                       0x50cf4 -[IntercomSDK_IntercomNexusSocket isConnected] + 201563  Intercom                       0x50ef8 -[IntercomSDK_IntercomNexusSocket reconnect] + 206724  Intercom                       0x4db48 -[IntercomSDK_IntercomNexusConnection reconnectSockets] + 74405  Network                        0x83844c __nw_path_necp_update_evaluator_block_invoke + 3166  libdispatch.dylib              0x213c _dispatch_call_block_and_release + 327  libdispatch.dylib              0x3dd4 _dispatch_client_callout + 208  libdispatch.dylib              0xb400 _dispatch_lane_serial_drain + 7489  libdispatch.dylib              0xbf30 _dispatch_lane_invoke + 38010 libdispatch.dylib          

Hi, we’re running into an issue with ANRs on our application stemming from the initialize call on the Intercom SDK.We are currently using 15.1.4 of the Android SDK with the following code used for initialization:Intercom.initialize( application, apiKey, appId)The following is the stacktrace we’re seeing in Firebase for a number of our users: io.intercom.android.sdk.Injector.getMetricTracker (Injector.java:255)io.intercom.android.sdk.Injector.getOverlayPresenter (Injector.java:279)io.intercom.android.sdk.Injector.getResetManager (Injector.java:333)io.intercom.android.sdk.Injector.getLifecycleTracker (Injector.java:311)io.intercom.android.sdk.Injector.initWithAppCredentials (Injector.java:135)io.intercom.android.sdk.Intercom$Companion.create (Intercom.kt:1092)io.intercom.android.sdk.Intercom$Companion.initialize (Intercom.kt:1005)com.<redacted>.android.util.IntercomUtil.initialize (IntercomUtil.kt:38)  When looking at the releases, we’re currently 2 patch versions behind b

Hello ,while init intercom sdk in App.kt which is app launch class ANR is produced please find the error belowmain (runnable):tid=1 systid=8183 at io.intercom.android.sdk.identity.AppConfig.<init>(AppConfig.java:125) at io.intercom.android.sdk.Injector.initWithAppCredentials(Injector.java:104) at io.intercom.android.sdk.RealIntercom.create(RealIntercom.java:80) at io.intercom.android.sdk.Intercom.initialize(Intercom.java:73) at yourpakagename.com.manager.IntercomManager.configure(IntercomManager.java:24) at yourpakagename.com.App.onCreate(App.kt:95) at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1277) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6771) at android.app.ActivityThread.-$$Nest$mhandleBindApplication(unavailable) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2129) at android.os.Handler.dispatchMessage(Handler.java:106) at

Hi, we’re running into an issue with ANRs on our application stemming from the initialize call on the Intercom SDK.We are currently using 15.1.4 of the Android SDK with the following code used for initialization:Intercom.initialize(this, INTERCOM_API_KEY, INTERCOM_APP_ID);I have updated the SDK to 15.5.1 but we haven’t had time to collect data,  I am wondering if this will suffice, I didn’t see anything the latest or previous release notes that would indicate so. Below is the exception from firebase : main (runnable):tid=1 systid=3084        at io.intercom.android.sdk.errorreporting.ExceptionParser.<clinit>(ExceptionParser.java:11)       at io.intercom.android.sdk.errorreporting.ErrorReporter.create(ErrorReporter.java:18)       at io.intercom.android.sdk.Injector.getErrorReporter(Injector.java:319)       at io.intercom.android.sdk.Injector.getLifecycleTracker(Injector.java:310)       at io.intercom.android.sdk.Injector.initWithAppCredentials(Injector.java:135)       at io.interco

Hi everybody, we are integrating Intercom with two of our custom built applications. In these two applications we have built the standard integration with Intercom. When I sent a banner or chat from Intercom to these applications, they only appear within these applications when I do a refresh. Of course this is not the behaviour that we want: we want our users to directly see the banner/chat in the applications. Both applications a web based cloud native. It seems that the push mechanisme does not work. What are we doing wrong?

As of @intercom/intercom-react-native v8.2.0 the back button after presenting content using Intercom.presentContent(IntercomContent.helpCenterCollectionsWithIds([id]))is broken on Android devices.Screenshot attached. Any help appreciated.  

My team has run into a roadblock in setting up single sign on for our platform. We use OpenID, and it’s not configurable natively in Intercom. I’ve found some articles stating that some third party partners offer a ‘go between’ workaround for this, but I’d love to hear from the community if anyone has successfully set this up and what the experience was like with the third party they chose.

Hi Intercom team,We're encountering a crash in our production app related to the Intercom SDK when processing push notifications. The error occurs in TaskStackBuilder.getPendingIntent() with the following stack trace:  Fatal Exception: java.lang.IllegalStateException: No intents added to TaskStackBuilder; cannot getPendingIntent at androidx.core.app.TaskStackBuilder.getPendingIntent(TaskStackBuilder.java:333) at androidx.core.app.TaskStackBuilder.getPendingIntent(TaskStackBuilder.java:313) at io.intercom.android.sdk.m5.push.ConversationDeepLinkRouterKt.buildBasePendingIntent(ConversationDeepLinkRouter.kt:85) at io.intercom.android.sdk.m5.push.ConversationDeepLinkRouterKt.buildIntentForDeepLinkScreen(ConversationDeepLinkRouter.kt:42) at io.intercom.android.sdk.m5.push.ui.DeepLinkStylePushUIKt.buildDeepLinkNotification(DeepLinkStylePushUI.kt:44) at io.intercom.android.sdk.m5.push.IntercomNotificationHandler$processDeepLinkPushNotification$1.in

Release Date: 16-05-2025 🐛 Bug Fixes Fixes a bug that could cause a crash when dismissing multiple in app notifications. Fixes a bug that could cause a crash when trying to close a note using the x button.

Hi! I have the “Prevent users from opening multiple conversations” option enabled in Intercom settings, but when calling Intercom.presentMessageComposer(); from my React Native app, it always creates a new conversation instead of navigating to the existing one.Is this the expected behavior, a known issue, or am I missing something in the implementation?What’s the best way to handle this scenario?Thanks!

Hi team, just wanted to check if Intercom have any plans to integrate with the 2 following chinese social media apps 1) XiaoHongShu and 2) BiliBili3) Tiktok XiaoHongShu (XHS) is kind of like the chinese version of Instagram

We plan purchase Circle. IO for our course and community platform. We need to make sure that Intercom integrates with it before we finalize the purchase, though. Circle said it should integrate just fine, but we want to test it first. They asked me for an Intercom code snippet. Intercom bot directed me where I can find this. I shared it with Circle and they were unsuccessful with getting the snippet to work. Is there anyone at Intercom that can help me outside of the bot? Or anyone else use Circle and have had success integrating intercom?

My context:API version: 2.12API call: search and update contact404 Curl request at 2025-03-31 09:50:33 { "headers": { "content-length": "74", "user-agent": "GuzzleHttp/7", "host": "api.intercom.io", "authorization": "********", "accept": "application/json", "content-type": "application/json" }, "body": "{\"query\":{\"field\":\"external_id\",\"operator\":\"=\",\"value\":\"vegastars_78859\"}}", "url": "https://api.intercom.io/contacts/search", "method": "POST"}Here is the response at 2025-03-31 09:50:33:I have double-checked that the value exists in Intercom. However, the weird thing is that when my server calls the API, it returns an error response. Then, when the request is retried by the queue, it succeeds.I want to make sure that are these response such as 404 and 502, 504 coming from your side ?{ "body": "<html><head><title>404 Not Found</title></head><body><center><h1>404 Not Found</h1></center><

I would like to export the Intercom ID of all users - and the only documentation I can find is to do this via API. I am using Postman for this but I was hoping to find a way to get it as a CSV or something easier to navigate. Can anyone point me in the right direction to get this data?

Release Date: 11-04-2025 🚀 Enhancements We've added a new API to enable setting JWTs in the Messenger. This should be called before any user login. To learn more go here. Resolved some differences between the registration of unidentified and identified users of iOS and Android. Both platforms now have matching implementations.

Hi there,Here’s the situation, we’ve rebuild an old application and are almost ready to a launch. We used Intercom on the old application to trigger emails and in-app messages to users, as well has handle support. What is the best way to migrate our Intercom install to the new app? Should we start a new app entirely and export our old data? Or can we just install the Intercom code in the new app, connect it to segment, and build off what we already had?Cheers