Popular Topics

The v2.13 REST API introduces support for creating, updating, and reading custom object instances. But, the documentation does not say anything about updating references – either on those instances themselves, or references to custom objects as custom attributes on people.Without the ability to associate custom objects with contacts or conversations, the API doesn’t seem very useful.I’ve tried to pass contact IDs and external IDs, and objects with an “id” key with no success, both as arrays and as simple attributes. Based on how the contacts/{id}/companies endpoint works, I’d probably expect the following to work:POST /custom_object_instancesContent-Type: application/json{"external_id": "123", "custom_attributes": {"Owner":{"id":"6602eae0ca854b5e2a01f503"}}And if the attribute support multiple people, it should support an array. Supporting objects, instead of just the ID, would allow you to support identifying references with both Intercom’s ID and external ID, so that’d be nice.I’ll n

Hi!  I’m the CEO of a high ticket, low volume equipment manufacturing company.  We use Hubspot for our sales CRM and customer support.  The allure was to have all of our data in one place, which also likely reduces costs.  But in practice, creating “automations” manually to facilitate ticket management is absurdly and unnecessarily complex compared to any support-first product like Intercom.  I’m also curious as to AI / chatbot features between Hubspot and Intercom.We receive about 50 tickets per month but many of those are simple requests that could surely be answered by an AI bot, which would allow our staff to focus on the truly urgent.The urgent, priority 911, requests typically require a video call on Zoom or Whatsapp to visually inspect the customer’s equipment, diagnose, and address.My current belief is that our needs are so basic and our requests so minimal, that Intercom would be overkill and not worth the additional cost and integration complexity, but I’m making this post to

Hi,Recently I have been noticing that we have been receiving an error_code of “not_found” when making a POST request to the /contacts endpoint (creating a contact).This is surprising as I am not sure how this is possible when creating a contact (as opposed to updating one).If it helps, an example request id for this 000bkte0pcsrns5hpus0, hopefully I am not just off-base but I was looking to understand how this might happen? I am not sure what this error code could mean when trying to create a contact.

All of sudden today our native Android crash started crashing whenever a user tried to access Intercom. This was the crash:java.lang.ClassNotFoundException - org.msgpack.core.buffer.MessageBufferUThe crash only happened with builds obfuscated by ProGuard. The crash still happened even after adding the keep rules according to the documentation:-keep class io.intercom.android.** { *; }-keep class com.intercom.** { *; } We solved the crash by adding the following to our proguard-rules.pro file: -keep class org.msgpack.** { *; }I have a couple of questions:Why did the crash start happening all of a sudden? Why is it not mentioned in the documentation that we need to keep org.msgpack classes unobfuscated? How can we be sure to prevent similar crashes from happening ever again? Thank you

 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-Crashlytics handler (IntercomSDK_sentrycrashcm_signal_getAPI). This w

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 sensitive Data Connector calls)?

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 any endpoint provided by intercom to ingest them? or any other possible way?

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.DestroyActivityItem.execute(DestroyActivityItem.java:47) at android.app.serv

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.DispatchedTask.run(DispatchedTask.kt:100) at kotlinx.coroutines.internal.LimitedDispatcher$Worker.r

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_package_code=access-community&search=turfWould love to get all your feedback and thoughts on possible improvements!!! Thanks a million 😁  

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. 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)kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask (CoroutineScheduler.kt:820)kotlinx.coroutines.

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. 

We are using @intercom/intercom-react-native v9.4.0 with Expo.When we send mobile push notifications, we can track:    •    How many users received the push    •    Which users opened it (tap on the push)  However, we also use POST messages, and inside those POST we include deeplinks to redirect users to specific screens in the app.Here’s the issue:    •    We can track how many users opened the POST message    •    But we cannot track link interactions inside the POST    •    The “Clicked” metric is always empty, even when users tap the deeplinkIs there any workaround or recommended approach to track when users tap deeplinks or links inside POST messages?