Popular Topics

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.

I am facing problems while trying to create an account on intercom, the error 403 forbidden appears, it shows that my workspace is suspended, but I have respected all the policies.

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.

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  

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

Hey! I’m facing an issue with intercom-sdk version 17.2.0.The in-app message doesn’t display any message text when it’s a new message in an existing conversation. I’ve attached a Layout Inspector screenshot for more details.Compose version in the app: composeBom = "2025.09.01"  At the same time, if you start a new conversation from the Intercom web interface, the very first message is visible in the app — but from the second message onward, it disappears again. 

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?

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?

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

We’re presenting Intercom articles with Intercom.presentContent(content) . Everything was working well in version 8.8.0 but after bumping to 9.x, the close button at the top article header is broken in iOS and doesn’t respond to taps. The only way to close the article is to drag the overlay down (which is something that might not be obvious for every user). It is working correctly on Android.

Hello,I’ve been planning to make a customer portal and wanted to make it a PWA. I would like to be able to use Intercom push notifications on the PWA but from all the documentation I can find it seems like push notifications are only possible using the mobile SDK.I was wondering if there is a way to have push notifications without using the mobile SDK.

Hey friends, unsurprisingly enough - after reaching out to our clients for some feedback, Fin is their favorite education tool that we have - which we love! That being said, I’m trying to get MORE source documentation into Fin to reference and suggest - specifically, our University Courses (hosted in Northpass/Gainsight) - what’s the best way to go about this, so that it indexes correctly and really does become more helpful!? 

Hi, I’ve been having a helluva time trying to get JWT verification working with `@intercom/intercom-react-native`.For context, we have JWT working with our website, and the API secret is enabled for all platforms. We’re reusing the same endpoint we use for web to get the JWT for mobile.Our mobile app is built with:expo: @53.0.23 @intercom/intercom-react-native: 9.1.2 react-native: 0.79.5I have been testing the app in development mode, with `expo run:ios`.So far, I’ve been able to get Intercom working if JWT is not enforced. But once I activate “Enforce Messenger Security” in the Security Settings, Intercom views start returning “Something’s gone wrong” with a reload button. Here’s our JWT code:// Verified that `intercomToken` is valid, in Intercom’s online JWT decoder// // Token payload looks like:// {// "user_id": 3, // << Does this need to be a string?// "email": "person@place.com",// "name": "John Smith",// "exp": 1759892398// }await Intercom.setUserJwt(intercomToken

Hello support!When fetching a conversation using GET conversations/{id} or POST /conversations/search, the statistics fields are all null. I’m using version 2.10 but tried with 2.14 as well and it doesn’t work either. This is the object I receive  "statistics": {      "type": "conversation_statistics",      "time_to_assignment": null,      "time_to_admin_reply": null,      "time_to_first_close": null,      "time_to_last_close": null,      "median_time_to_reply": null,      "first_contact_reply_at": null,      "first_assignment_at": null,      "first_admin_reply_at": null,      "first_close_at": null,      "last_assignment_at": null,      "last_assignment_admin_reply_at": null,      "last_contact_reply_at": null,      "last_admin_reply_at": null,      "last_close_at": null,      "last_closed_by_id": null,      "count_reopens": 0,      "count_assignments": 0,      "count_conversation_parts": 7    }  My close is to know when was last time a conversation was closed and intended to use stat

SDK version 19.2.0 has broken the close button on our carousels, and it's still broken on 19.2.1It would be good if we could update our SDK version for Intercom because Intercom have also fixed UI issues on iOS 26 (new iOS version) :(

There are multiple ways of sending a ticket form to a conversation as described here:https://www.intercom.com/help/en/articles/8300310-ticket-form-optionsIs there a way to send a ticket form to a conversation through the REST API?TIA

Looking at the implementation of intercom for IOS, the creator seems to leave the API key in the front end. Does this mean that this API key is fine if exposed to the end user? I don’t seem to see another way to obscure it, as keeping the key on the backend doesn’t seem like an option if I want to use intercom’s package.import Intercomlet INTERCOM_APP_ID = "<#YOUR APP ID#>"let INTERCOM_API_KEY = "<#YOUR API KEY#>"class SceneDelegate: UIResponder, UIWindowSceneDelegate { 

I’m returning to Intercom after a long break, and I could use some advice from folks who’ve set up recent workflows.It looks like every customer interaction starts as a Conversation. And if it takes longer to resolve or needs extra structure, it can be turned into a Ticket. That all makes sense.But I’m trying to set things up in a way that keeps reporting clean and consistent.My goals:I want to capture the same core metadata for every interaction (things like feature area, source, etc.) I don’t want to double-count anything when pulling metrics I want to avoid having agents fill in fields twice, or inconsistently across conversations and ticketsMy questions:Do you only use tickets for escalations, or convert everything? Can you safely report on Conversations only, and still get reliable counts and resolution metrics? Are you adding custom fields to Conversations for universal stuff, and using ticket-only fields for more complex cases?Trying to figure out how to avoid having my metrics

We are trying to use official @intercom/messenger-js-sdk with our react app.https://www.npmjs.com/package/@intercom/messenger-js-sdkWe are calling Intercom instance in our App component Intercom({ app_id: ..., });and then updating user info when user data is available using following functions:import { boot, shutdown, update } from "@intercom/messenger-js-sdk"; when there is no user data we are calling boot with only id,boot({    "app_id": "...",})and if there is user data, we are passing required properties to boot functionboot({    "app_id": "...",    "user_id": "...",    "name": "...",    "email": "...@......",    "created_at": ....,}) It seems that when calling with boot({ "app_id": "..."}), user data is not cleared and in chat we continue to receive messages as if user is still logged in.Once boot() is called with user data, can it be rebooted with no data (for example, in scenario if user is logged out from our app and we want new chat instance without user data)? Also, if t

I’m trying to integrate Intercom push notifications into my React Native app built with Expo (using a custom dev client). I’m using @intercom/intercom-react-native (latest version) and JWT authentication.I can successfully:Generate a valid JWT (confirmed via jwt.io) with user_id and email. Log in the user in Intercom with matching userId and email. Verify that Intercom.isUserLoggedIn() returns true. Fetch the logged-in user attributes from Intercom, which match the JWT payload.Here’s the code I’m using to set up push notifications: export const setupIntercomPushNotifications = async (): Promise<boolean> => {  try {    const { status: existingStatus } = await Notifications.getPermissionsAsync();    let finalStatus = existingStatus;    if (existingStatus !== "granted") {      const { status } = await Notifications.requestPermissionsAsync();      finalStatus = status;    }    if (finalStatus !== "granted") {      console.log("❌ Push notification permissions not granted");      re