Popular Topics

The 19.3.0 release introduced a bug where opening articles could sometimes crash, reported here. That was fixed in 19.3.1, but at the same time or possibly earlier, it seems another issue was introduced and the articles now aren’t loading at all.When calling Intercom.presentContent(.article(id: “123456”)), while the app no longer crashes, I’m instead stuck on a blank screen that can’t be dismissed.The close button on that page also does not do anything. I believe this bug was introduced with version 19.2.0. It has already been reported multiple times, but seemingly with little response, here and here.

We are seeing quite a few crashes for the latest Intercom SDK. Older SDKs do not crash.  OS Version: iOS 26.0.1 (23A355)Report Version: 104Exception Type: EXC_BREAKPOINT (SIGTRAP)Exception Codes: 0 at 0x00000001077393e8Crashed Thread: 0Application Specific Information:Exception 6, Code 1, Subcode 4419982312Thread 0 Crashed:0   Intercom                        0x1077393e8         ListBlockView.configure1   Intercom                        0x107738d40         ListBlockView.init2   Intercom                        0x10773f1c0         closure in BlockViewFactory.getViewsForBlocks3   Intercom                        0x10773efc4         BlockViewFactory.getViewsForBlocks4   Intercom                        0x1077432cc         BlockPartView.addBlocks5   Intercom                        0x107744a3c         BlockPartView.configureLayout6   Intercom                        0x10774ec1c         PartViewFactory.getView7   Intercom                        0x107754034         ConversationCellViewFactory.getV

Hello, We need to calculate total duration for which conversations are snoozed for analytical purposes. I went through the community forum and found this In the above topic, it’s mentioned that their isn't a direct method provided for generating a report specifically for snooze time in conversations.Although we have found out that we can derive snooze durations and it would be helpful if we can get a review from the Intercom community over this method, or if we can get some other attributes or methods (provided by the Intercom API) through which we can calculate snooze durations, this would be extremely useful for us.We are aiming to derive the snooze duration based on the following:Calculate snooze time by tracking conversation state transitions through conversation parts, which provide the most granular state information for each conversation. Each conversation_part has a status field that captures the conversation state (open, closed, or snoozed) and a created_at field which tracks

Hi!I’m new to Intercom and Workflows. I’m a French speaker, so apologies if some of the wording isn’t perfect.We use Intercom to communicate with professionals using our AI tool for healthcare.To improve efficiency, we created a Workflow that automatically generates tickets depending on the issue type.I looked into the “Auto-close incomplete Workflow conversations” option, but it doesn’t work in our case, since most of our Workflows end with a ticket.I also considered using the “When the customer doesn’t respond” trigger, but that doesn’t help either—because it’s the bot (not a human) interacting with the user.And most importantly: I don’t want conversations to close automatically when the Workflow ends, because our goal is to continue helping the client if they still need support.Fin suggested I try using tags inside the Workflow to trigger auto-close only in specific cases.So I was thinking: what if I add a tag like “not_finished” while the Workflow is still in progress, and then swi

Hello everyone.I'm experiencing an MQRC 2035 (Authorization) error when integrating Intercom with our messaging queue system. The setup involves deploying an application with MQ Client Connection Properties, specifying all necessary details.While trying to resolve the issue, I reached out to RabbitMQ support to ensure our configurations were correct. Despite Intercom running as the root user and the queue manager using default mqm users, the connection still fails. The error message indicates a failure to connect to the queue manager on the specified hostname and port.Has anyone encountered this issue while integrating Intercom with a messaging queue? What steps did you take to resolve it?Any insights or suggestions would be greatly appreciated.

Looking for an experienced consultant to help build and optimize Intercom chatbot solutions for customer support automation and lead generation. Need expertise in conversational AI design and Intercom platform integration.Requirements:Experience with Intercom's Resolution Bot and Custom Actions for automated customer interactions Knowledge of conversation flows, intent recognition, and fallback scenarios for complex customer queries Understanding of Intercom's Messenger integration, help desk workflows, and CRM data synchronization Ability to design multilingual chatbots with personalization and user segmentation Familiarity with Intercom's API for custom integrations and third-party tool connectionsRemote work preferred. Please share relevant Intercom chatbot implementation experience and approach to conversational AI optimization.

Hey, im currently creating an Chatbot Workflow. My maingoal is to split the current workflow in 2 parts. I want to do this to clean it up a bit.The Workflow asks the User if hes a Customer or a driver and this is where i want to split it. Id like to have one workflow for customers and one for Drivers.Any Ideas on how to implement this?You can see the current Workflow on the attached picture. 

We were able to go on Phone queue but whenever we receive calls , agents cant be heard. All headset and sound setup were working fine. tried basic t/s but issue persists.

Since the upgrade to 9.*.* of version for React Native Intercom (https://github.com/intercom/intercom-react-native), we can no longer build and compile our Expo React Native app for iOS.Somehow the Intercom upgrade introduces a failure where C++ files are not correctly mapped during compiling. This is only when combined with other packages (in our case UserCentrics for RN).It is important to highlight that although other third party apps are involved, Intercom’s upgrade breaks the building process. Compiling fails with: 13 | 14 | #ifndef __cplusplus> 15 | #error This file must be compiled as Obj-C++. If you are importing it, you must change your file extension to .mm. | ^ This file must be compiled as Obj-C++. If you are importing it, you must change your file extension to .mm. 16 | #endif 17 | 18 | // Avoid multiple includes of IntercomReactNativeSpec symbolsand 'optional' file not found'tuple' file not found'utility' file not foundI’ve added a minimal reproducible

I have discoverd instances in conversation_parts where the conversation_part.status is in a snooze state even if the part_type is a comment type. How is this possible, because according to this article (https://www.intercom.com/help/en/articles/6564538-snooze-a-conversation) “If you send a reply message in a 'snoozed' conversation that's assigned to you, it will not automatically 'unsnooze'/reopen the conversation.”“If someone else sends a reply, adds a note, or updates an attribute in a 'snoozed' conversation assigned to you, it will be automatically 'unsnoozed'/reopened.” So How come a conversation remain in an snoozed state even after there is a comment from either admin or customer?A comment part type is defined as: Standard reply from customer or admin to a conversation (defined at: https://developers.intercom.com/docs/references/1.4/rest-api/conversations/conversation-part-model#conversation-part-types)  These are the part-types appearing with snoozed state1    comment2    conver

Hi all! Support team leaders, I’d love to know -What metric from reporting in Intercom do you use to inform a goal for your team monthly?Number of tickets closed? Number of tickets assigned? Number of replies sent? Or something else? I’m trying to zone in on how many tickets my support team members are handling individually each week.  Thanks!

Hi, We are using Intercom's API in Europe and have been experiencing an outage in one of the endpoints since October 25th.It fails with error 504 IntercomException: API service is temporarily unavailable.The status page does not show any incidents https://www.intercomstatus.com/Do you experience any API outages?Thanks!

Fatal Exception: java.net.MalformedURLException: unknown protocol: content at java.net.URL.<init>(URL.java:608) at java.net.URL.<init>(URL.java:498) at java.net.URL.<init>(URL.java:447) 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:33) at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:101) at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:113) at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:89) at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:589) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:823) at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:720) at kotlinx.coroutines.scheduling

Release Date: 28-10-2025 🐛 Bug Fixes Fixed a crash that could happen when opening articles from a conversation.

Fatal Exception: java.lang.NoSuchMethodError: No virtual method close()V in class Landroid/media/MediaMetadataRetriever; or its super classes (declaration of 'android.media.MediaMetadataRetriever' appears in /system/framework/framework.jar) at io.intercom.android.sdk.m5.conversation.utils.URIExtensionsKt.getVideoData(URIExtensions.kt:146) at io.intercom.android.sdk.m5.conversation.utils.URIExtensionsKt.getMediaData(URIExtensions.kt:51) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreen$lambda$29(ConversationScreen.kt:286) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.$r8$lambda$l4hfoRjJBkYl_jEYY6YWj7rurp4() at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$$ExternalSyntheticLambda2.invoke(D8$$SyntheticClass) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$35.invoke$lambda$3$lambda$0(ConversationScreen.kt:572) at io.intercom.and

We are longtime users of Intercom’s API.  The majority of our requests to Intercom’s API succeed.  Here are examples of two payloads that consistently fail.{  "event_name": "new-feature-receive_this_response",  "created_at": 1761447241,  "user_id": "x12x227f8x4067cx7a5dx97x"} {  "event_name": "experiments-show_experiment",  "created_at": 1761447325,  "user_id": "x12x227f8x4067cx7a5dx97x",  "metadata": {    "label": "experiment_questions"  }} When they fail, Intercom’s API just returns a 422 with no additional details about the problem. Reading through the docs, I can’t figure out what is wrong with these.  They both have event_name and created_at, the two required fields.  One has metadata, and one does not, but metadata is listed as optional, anyway.  I tried adjusting the event_names — replacing underscores with hyphens, truncating them &c., even trying a random string of 10 ascii chars, but these requests always still fail.  I got a coding agent to read through the docs, and it

I’m having an issue with the workflow in our ticket queue when closing a ticket. Normally when a ticket is closed the next ticket in the queue is automatically selected. For the last couple of days this has not been happening. For the most part it is reverting to the most recent ticket received in the queue, but sometimes it jumps to a random ticket somewehere else in the queue. I seem to be the only member of our team experiencing this so I think I have inadvertantly changed a setting somewhere but cannot find anything about this in the Settings or the Help section.

When a contact replies through the email channel to a closed ticket, there is no webhook received even though the ticket reopens. Is this a feature or a bug?

https://developers.intercom.com/docs/references/rest-api/api.intercom.io/contacts/createcontacthttps://developers.intercom.com/docs/references/rest-api/api.intercom.io/contacts/updatecontact I am unable to figure out why this is happening and on the API documentation says it should be able to update the value.

Hello All, When I search something about a customer I found this URL which have release notes of the a known vendor in our country.https://intercom.help/c-c-s/tr/ 

Hi Intercom Community,We are a returning customer (we was using Intercom for many years until end of 2024 with US data hosting) and want to come back but with EU hosting to make it complaint. I’m hoping to get some help moving the process forward as we seem to be stuck.Our goal is simple: we want to pay for and activate the Intercom Advanced plan with EU data residency. Another words: 😅 To make it as easy as possible, here are all the details: Plan: We need 3 seats on the Advanced plan. Hosting: Data residency in the European Union is a mandatory requirement for us. Commitment: We are ready to pay immediately. We understand an annual commitment is required, and that's perfectly fine. We can even pay for 2 years upfront if it helps accelerate the activation. Context: We were long-time Intercom users who churned in late 2024. We've decided to come back and are fully aware of the product and its capabilities (including the limitations of the EU hosting add-ons). Urgency: We are f

Hello, I am trying to integrate a third-party app into our workspace, and the oauth screen displays the following:  I have full admin on the workspace - and ive tried signing in and out again.

Hi Intercom Support, I'm building a Slack bot to pull metrics from Intercom. I need to access the Fin AI Resolution Rate and conversation stats that appear in the Reports dashboard. Questions:1. Is there an API endpoint that provides the same metrics shown in Reports (AI resolution rate, conversation counts)?2. How can I identify which conversations were resolved by Fin AI via the API?3. Should I use the Data Export API or Conversations Search API for accurate reporting data? Current Issue:Metrics I calculate from the Conversations API don't match the dashboard. For example, my calculation shows 84% AI resolution but the dashboard shows 62%. (same issue happens with other stats as well) What do you think the best way is to programmatically access these report metrics? Thanks(The goal is to build an AI agent—a Slack bot app that connects with Intercom. When I ask in Slack, it responds correctly with proper reporting and provides AI insights - Reporting SHOULD BE ACCURATE.)

Hi,As part of our integration into intercom - we would like to know when a contact gets blocked so we can start ignoring that contact for tasks like updating user attributes etc when they change on our side.I had a look at the available webhooks, but it wasn’t obvious which (if any) webhooks would fire when a contact was blocked and which field would let us know that they were blocked.Is there any webhook that would assist us with this?

Hello Intercom Community,I'm encountering a persistent issue with retrieving and listening for unread conversation counts in my React Native application using the Intercom SDK. Neither Intercom.getUnreadConversationCount() nor the IntercomUnreadConversationCountDidChangeNotification event listener seems to be working as expected.Goal: My objective is to display the current unread message count from Intercom within my app's UI (outside of the Intercom messenger itself).Expected Behavior: When new messages arrive in Intercom conversations, the IntercomUnreadConversationCountDidChangeNotification listener should fire with the updated count. Intercom.getUnreadConversationCount() should return the correct number of unread conversations at the time of the call. Actual Behavior: Intercom.getUnreadConversationCount() consistently returns 0 (or null/undefined, please specify) even when there are clearly unread messages visible when I manually open the Intercom messenger. The Intercom.addEve