Answered

We are seeing the following crashes on Android only when upgrading to Version 6 of the React Native SDK. iOS works fine: 1-07 12:50:31.668 21555 21555 D AndroidRuntime: Shutting down VM11-07 12:50:31.672 21555 21555 E AndroidRuntime: FATAL EXCEPTION: main11-07 12:50:31.672 21555 21555 E AndroidRuntime: Process: com.neuropeakpro, PID: 2155511-07 12:50:31.672 21555 21555 E AndroidRuntime: java.lang.IllegalStateException: No OnBackPressedDispatcherOwner was provided via LocalOnBackPressedDispatcherOwner11-07 12:50:31.672 21555 21555 E AndroidRuntime: at androidx.activity.compose.BackHandlerKt.BackHandler(BackHandler.kt:97)11-07 12:50:31.672 21555 21555 E AndroidRuntime: at androidx.navigation.compose.NavHostKt.NavHost(NavHost.kt:212)11-07 12:50:31.672 21555 21555 E AndroidRuntime: at androidx.navigation.compose.NavHostKt.NavHost(NavHost.kt:129)11-07 12:50:31.672 21555 21555 E AndroidRuntime: at io.intercom.android.sdk.m5.helpcenter.HelpCenterScreenKt.HelpCenter

Is it possible to receive an NPS score/inbox or team member? Thanks! 

Have a nice day 

I've integrated a Product Tour link into a banner using Intercom. However, I've encountered an issue where clicking on the Product Tour link causes the page to refresh itself before initiating the tour. Ideally, the tour should start seamlessly since the banner appears on the same page where the tour begins. Is there a method to prevent this page from reloading upon clicking the link? Thanks!

I am trying to embed an image URL into an article so we can quickly replace images by just updating the image url in our image repository. How do I do this in Intercom? I tried putting the code <img src=”https://examply.io/image.jpeg”/> into the Insert Code block but this populates no images, as if the code does not work but the code is correct. I followed this article on Intercoms website that states you CAN insert this type of code into a help center article. Any advice is appreciated!

Hi All, Hoping someone can help or provide some direction as how to prevent SPAM bots starting conversations on our Intercom Messenger on our Public Website.We have the Intercom Messenger on our Public facing website (Visitors/Leads) https://freshtrack.comWhen someone starts a conversation they need to provide Name, Email and Contact Number (which they do). However, the conversation is SPAM.  The email and phone number are fake and the message is generally “How do I register?”  or most recently “Where may I find a food bank” or similar.   The phone set to USA number.The volume of these messages is increasing and we want to prevent them as it is causing issues when our marketing automation runs and the emails just bounce back. Sometimes we get replies with exactly the same original conversation message  “How do I register”, “How can I book a appointment” etc. Is there a {I’m, Human} tool for Messenger when it is public facing?  Or dose anyone have any other ideas?Thank you all in advanc

Hello, I wanted to report to you a problem we faced recently.Our application is crashing when it's starting on iOS 13.We are using the Intercom SDK version 16.1.2.We installed this one with Cocoapod.It seems the SDK is referencing one Library that is available for iOS14+UniformTypeIdentifiershttps://developer.apple.com/documentation/uniformtypeidentifiersDid you also experience the same issue?I noticed the SDK should support iOS 13 in the podspec file: https://github.com/intercom/intercom-ios/blob/master/Intercom.podspecCrash log:Termination Description: DYLD, dependent dylib '/System/Library/Frameworks/UniformTypeIdentifiers.framework/UniformTypeIdentifiers' not found for '/private/var/containers/Bundle/Application/33855C68-5037-413A-B790-77EB65129A22/Qonto.app/Frameworks/Intercom.framework/Intercom', tried but didn't find: '/System/Library/Frameworks/UniformTypeIdentifiers.framework/UniformTypeIdentifiers' '/System/Library/Frameworks/UniformTypeIdentifiers.framework/UniformTypeIdenti

We're currently integrating Intercom into our Flutter app.We've set up a workflow that's triggered within a series. The first time around, it works perfectly and the message appears as an in-app notification. However, subsequent triggers result in the message being delivered to the inbox without the in-app notification alert.This inconsistency is affecting our product onboarding, which relies heavily on these workflows. The experience for our users is crucial and currently compromised due to this issue.Has anyone else encountered this? We're looking for an urgent fix or any workarounds that could help us ensure a smooth and consistent onboarding experience through Intercom.Thanks in advance for your help!

Is there a way in the iOS SDK to disable opening a conversations while keeping the ability to send campaigns?Specifically when user taps on campaign we wouldn’t want them to be able to start a conversation from it

Currently, in our android app is configured such that whenever a user clicks on the Intercom button, it initiates a new conversation.This setup, although functional, is not ideal for our users who often return to continue previous discussions. How can we modify this so that clicking the Intercom button opens the most recent conversation with that user instead of starting a new one every time.

Hello We want to hard close conversation the moment it was closed.We don’t want closed conversation to keep on reopening within 24 hours(min we can set)  

Integration with the sdk seems to work but when I navigate to the messaging screens it crashes immediately  java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/compose/ui/platform/LocalSoftwareKeyboardController;                                                                                                        at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreenContent(ConversationScreen.kt:240)                                                                                                        at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt.ConversationScreen(ConversationScreen.kt:119)                                                                                                        at io.intercom.android.sdk.m5.navigation.ConversationDestinationKt$conversationDestination$5.invoke(ConversationDestination.kt:79)                                                                                                      

Hello - in the past week I’ve assisted two customers in whitelisting our domain so their adblocker (uBlock Origin, Total Adblock) would not prevent them from accessing Intercom. I’m guessing that the definitions used to determine if something is an element to block may have changed as this was never an issue before. Is there a way to prevent this? Attaching two examples before and after whitelisting: uBlock OriginTotal Adblock Does this have the potential to impact surveys? Looking forward to the feedback. Thanks, Michael

Hi all.Some of our documentation has been created in other documentation authoring systems. Is there a way of importing documents from a system like Madcap Flare or to import the HTML5 output that has been created by that system? And how about the other way round?Best regardsHolger

Hello Intercom Community,I'm reaching out to seek some guidance on an issue I've encountered while upgrading the Intercom SDK in my React Native project.I'm in the process of upgrading my project to Android SDK 34 as required by the new version of Intercom SDK. However, when I change the `compileSdkVersion` to 34 in my build.gradle file to accommodate this update, I encounter `:app:mergeExtDexDevDebug` errors during the build process.Here is the error log I'm receiving: ERROR:D8: com.android.tools.r8.kotlin.HERROR:D8: com.android.tools.r8.kotlin.HERROR:D8: com.android.tools.r8.kotlin.HERROR:D8: com.android.tools.r8.kotlin.HERROR:D8: com.android.tools.r8.kotlin.HERROR:D8: com.android.tools.r8.kotlin.HERROR:D8: com.android.tools.r8.kotlin.HERROR:D8: com.android.tools.r8.kotlin.HFAILURE: Build failed with an exception.* What went wrong:Execution failed for task ':app:mergeExtDexDevDebug'.> Could not resolve all files for configuration ':app:devDebugRuntimeClasspath'. > Failed to t

Hello,I trying to search by using the “POST /contacts/search” API. If I call the API from either POSTMAN or form the JSON as string, everything works fine. But when I trying to serialize an object to JSON and call the API, I get the error “Query body must contain a query hash”.This is from .NET API.Scenario which worksvar json = JObject.Parse($@"{{    ""query"": {{        ""operator"": ""AND"",        ""value"": [            {{                ""field"": ""email"",                ""operator"": ""="",                ""value"": ""{email}""            }}        ]    }}}}");var jsonStr = json.ToString();var postData = new StringContent(jsonStr, Encoding.UTF8, "application/json");using (HttpResponseMessage response = await httpClient.PostAsync($"/contacts/search", postData)){ … }Scenario which results in the errorvar searchQuery = new IntercomSearchQuery{    Operator = "AND",    Value = new List<IntercomSearchValue>    {        new IntercomSearchValue        {            Field = "email

I can create a tracker ticket and link user raised conversations. Can add a note that I can then copy down to all linked conversations.How could I add a comment on the tracker (parent) that actually creates that same note as an email in all the linked conversations?  

Hey everyone!I’ve been going around the workflow automation settings and so far no joy.I need to have a workflow that begins with an action on a backoffice ticket (such as, ticket closed with a specific status) and I would like this to trigger sending an automated message to the customer. It is entirely possible that the user was not and did not have an ongoing conversation with us, either by chat or by email, so this would need to be the same as creating a new ticket on our end.It seems like it’s not possible to just do this with existing automations, but do you know any valuable workarounds I could use in the meantime?Thank you in advance! ⭐️

Hello Intercom community. We use Slack as our communication hub and have many sales, product, and onboarding team members using Slack. Most of our support team uses Intercom though. What is the best practice for us to take a conversation from Slack and turn it into an Intercom ticket/chat? We want to have our sales/product/onboarding teams create an issue from within Slack and support can work on the issue from within Intercom then follow up and close it. Ideally support would do that in Intercom and updates would be sent to Slack. We found this 3rd party solution, but we'd prefer not to have to spend any more money or install more software: https://clearfeed.ai/pricing#Integrations

Over the last couple of weeks, some of my teams are reporting that the Recent Page Views data is missing from certain leads and visitors These all seem to be from visitors using Chrome... wondering if anyone else has noticed this, and wether its a new update to Chrome that prevents tracking ?

Asking on behalf of the user 👉 “Is it on the Road Map to allow required fields for Tickets Creation in Workflows?”

“Are there reports to compare YOY statistics?”

“Is there a timeline for FIN kicking in with SMS's sooner than email or around the same?”

I'm having a real issue relying on chat notifications for my support team. We have all the settings correct in Intercom and Windows to receive desktop notifications but random times it stops working, and chat will go unanswered for too long. Our team does not keep their inbox on screen all the time due to other tasks they have to perform. Any suggestions on how we can get more reliable and more noticeable notifications that will allow us to keep a first response time within a minute?

Hi, After updating to latest android sdk version (15.6.0), there's a crash when user clicks 'Send us a message' or 'Messages' Button. I attach crash logs below  java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/paging/Pager; at io.intercom.android.sdk.m5.inbox.InboxViewModel.<init>(InboxViewModel.kt:44) at io.intercom.android.sdk.m5.inbox.InboxViewModel.<init>(InboxViewModel.kt:30) at io.intercom.android.sdk.m5.inbox.InboxViewModel$Companion$factory$1.create(InboxViewModel.kt:109) at androi