Popular Topics

Two issues specific to android:Issue building with expo 55, any version greater than 9.6.3 fails the prebuild step with:- Creating native directory (./android)✔ Created native directory- Updating package.json✔ Updated package.json | no changes- Running prebuild✖ Prebuild failedTypeError: [android.manifest]: withAndroidManifestBaseMod: f.action?.some is not a functionTypeError: [android.manifest]: withAndroidManifestBaseMod: f.action?.some is not a function at /home/expo/workingdir/build/node_modules/@intercom/intercom-react-native/lib/commonjs/expo-plugins/withAndroidPushNotifications.js:96:149 at Array.some (<anonymous>) at /home/expo/workingdir/build/node_modules/@intercom/intercom-react-native/lib/commonjs/expo-plugins/withAndroidPushNotifications.js:96:129 at Array.some (<anonymous>) at /home/expo/workingdir/build/node_modules/@intercom/intercom-react-native/lib/commonjs/expo-plugins/withAndroidPushNotifications.js:96:58 at action (/home/expo/workingdi

Hi everyone,We are experiencing inconsistent behavior with contacts created through our WhatsApp channel and wanted to check if anyone else has seen something similar.When users start a conversation via WhatsApp, some contacts are created with the phone field populated, while others are created without the phone number.However, in the Intercom UI we consistently see the "WhatsApp number" field populated, even when the phone field is null in the Contact API response.Because of this, we are unable to retrieve the user's phone number via the API.Example Contact API response{ "type": "contact", "id": "69b8334c390fea79a974100c", "external_id": "whatsapp:xpto", "phone": null, "name": "Teste"}Conversation payload{ "type": "conversation", "source": { "type": "whatsapp", "author": { "type": "lead", "id": "69b8334c390fea79a974xxxc", "name": "Teste" } }}In the Intercom UI the WhatsApp number is visible, but it does not seem to be exposed through either the Contact

Hello!Hoping someone can help with this issue we’ve been facing when trying to integrate Fin in Slack. We’re using Fin in Slack for internal team use only (not customer-facing). The goal is for Fin to respond to teammates in designated Slack channels without ever involving our human Support team.However, we’re experiencing an issue where Fin keeps automatically routing the conversation to our human support teams despite the workflow being set up so that only Fin should be responding in these conversations. When the conversation ID is checked in the workflow troubleshooter no workflow is triggered. More details below:We have 3 Slack channels configured to trigger Intercom conversations (these channels can only be accessed by our internal teams)Channel settings: Trigger on keyword and a specific emoji Only these 3 channels trigger conversations Workflow setup: Channel = Slack Audience = All users (only internal teams have access to the slack channels in question which is why we did n

Release Date: 23-03-2026 🐛 Bug Fixes Fixed an issue where the composer attachment menu could render as plain text instead of a proper menu. Fixed an issue where the typing indicator may not appear when admin details are unavailable. Fixed an issue where the help center search bar placeholder could appear in English regardless of the workspace locale. Fixed an issue where device tokens could be mistakenly deleted impacting push notification delivery. Fixed an issue where workflows would sometimes not match for a user.

We’re looking for insight from companies that manage multiple subscriptions per customer in Stripe.In our case, each account has three separate subscriptions: Base plan Email plan Teams plan Each of these also has multiple plan levels, and every customer technically has all three subscriptions (either free or paid).Right now, the Stripe integration appears to pull only one random subscription, which makes it difficult to reliably identify a customer’s actual plan levels across all products.How are you configuring your Stripe integration to correctly identify all subscription plans for a customer, rather than just one? Are you using specific metadata, workarounds, or a particular integration setup to handle this?For context, we are looking to use Procedures to perform account actions inside Stripe, but need to be able to accurately make changes to all plans.

Hi,We are currently experiencing an issue with the Intercom Android SDK (version 15.9.1) in our application while developing a new feature with event.When a user clicks on the refill button, we send an event to Intercom as per your documentation: https://developers.intercom.com/installing-intercom/android/using-intercom#submit-an-event.As a result, a small popup window appears at the bottom of the screen. However, this popup window does not disappear automatically after the user reads the message and returns to the previous screen. Instead, it remains persistent until the app is killed and reopened.This behavior differs from the iOS SDK, where the popup window disappears automatically once the message is read, and the user returns to the previous screen.The user can manually remove the popup by sliding it. Is the persistent popup designed to be removed only manually by the user, or is there a way to make it disappear automatically after the message is read? We have implemented the feat

  Few devices it  displays fine <img width="512" height="1044" alt="Image" src="https://github.com/user-attachments/assets/88b18472-d6a3-4b46-a0c8-43201b08c538" /> but most of the devices, intercom message getting overlapped  <img width="467" height="960" alt="Image" src="https://github.com/user-attachments/assets/5b3019fd-dbbd-4fff-afd8-eeae2bda9034" />  <img width="512" height="705" alt="Image" src="https://github.com/user-attachments/assets/83a8a7f9-d6ee-41c9-ac8b-c1d6e1fecbe6" />  <img width="330" height="330" alt="Image" src="https://github.com/user-attachments/assets/4e82f1ec-1236-4856-97e8-771ea26b2d52" /> I have tried bullet list and number list. The problem is the overlay widget size.**intercom_flutter: ^9.5.5**   

I see that there is an MCP available for US accounts, any idea when will that be available for Europe? 

Hey community,I’m exploring ways to improve SEO performance by analyzing how customers engage with content and interact across different channels. Understanding their questions, search patterns, and preferences can really help refine keyword targeting and content structure.For anyone working in digital marketing services, these insights often become a game-changer — they make it easier to design content that matches user intent, optimize landing pages, and improve organic visibility.I’d love to hear how others integrate customer analytics or feedback into their SEO planning. What strategies have you found effective for aligning content with real user needs while boosting rankings?

Hi everyone, Is it possible to list all snippets from our system? I would like to list them like I list articles (https://developers.intercom.com/docs/references/rest-api/api.intercom.io/articles/listarticles) Best regards

Hi!One of our customers uses Intercom, and in order to create a pipeline between our backend and their order processing workflow, we created an API account in Intercom which we set to our company’s email. The customer now wants to have full control of the API account, without having to fiddle with changing the API token. Will the API token remain functional if the API account’s email is changed? Thanks!

Hi there,I've been looking through Intercom documentation, and it seems like there's something called a Custom Channel and an event called "custom channel base event." However, when I dig a little deeper, it seems that’s somehow connected to Fin?Not trying to integrate a conversation with the Fin chatbot; rather, I am looking to use my own pipeline for our users to interact with my customer service team in Inbox.What I'm looking to do is integrate my custom app as a custom channel in Inbox so that our team can interact through our own managed integration via API.Does anyone know:How to access this capability? If this feature is gated? Whether usage of this feature is billable or if it is included in the standard subscription tier?Thank you!

The Claude integration has access just to the conversations. It will be good to give access also to the Help Center and The Articles and help us to improve the content.

There is a vulnerability not fixed even in latest Intercom Android SDK 17.4.2:org.msgpack:msgpack-core should be 0.9.11 or greater|    +--- io.intercom.android:intercom-sdk-base:17.4.2|    |    +--- io.ably:ably-android:1.5.0|    |    |    +--- io.ably:network-client-okhttp:1.5.0|    |    |    |    +--- io.ably:network-client-core:1.5.0|    |    |    |    \--- com.squareup.okhttp3:okhttp:4.12.0 (*)|    |    |    +--- org.msgpack:msgpack-core:0.8.11Could you please update io.ably:ably-android to latest 1.6.1 to see if it fixes the vulnerability?Thanks!More Infoorg.msgpack:msgpack-core(Maven)< 0.9.110.9.11SummaryAffected Components:org.msgpack.core.MessageUnpacker.readPayload()org.msgpack.core.MessageUnpacker.unpackValue()org.msgpack.value.ExtensionValue.getData()A denial-of-service vulnerability exists in MessagePack for Java when deserializing .msgpack files containing EXT32 objects with attacker-controlled payload lengths. While MessagePack-Java parses extension headers lazily, it

Issue:The TypeScript type definition for the companies property in the @intercom/messenger-js-sdk (v0.0.18) appears to be incorrectly defined as a single-item tuple rather than a standard array.Details: In the SDK's type definitions, the companies property is defined as: companies?: [any];In TypeScript, the [any] syntax defines a tuple of length 1. However, Intercom's own documentation and the actual JavaScript API support an array of multiple company objects.The Error: When attempting to pass an array of multiple companies, the TypeScript compiler throws the following error:TS2322: Type '{ name: string; company_id: string; }[]' is not assignable to type '[any]'. Target requires 1 element(s) but source may have fewer.Steps to Reproduce: Try to boot the messenger with more than one company:TypeScriptimport { boot } from '@intercom/messenger-js-sdk';const companies: { company_id: string; name: string }[] = [ { company_id: '1', name: 'Company A' }, { company_id: '2', name: 'Company B' }

Hi everyone,We’ve noticed some users reporting that parts of our in-app widgets stop responding after they add third-party tools to customize their experience. While discussing this with a teammate, we mentioned hub script as one example people often try when experimenting with UI behavior.Has anyone seen similar conflicts with Intercom widgets, chat triggers, or tracking after users add custom scripts? What’s the best way to isolate whether the issue is coming from Intercom or from external tools?

Please help, previously there was no problem. But now the image sent from the webhook does not include the complete url.

Hello,We noticed a UI issue in the Intercom chat screen (Messenger) when using iOS 26 with the Liquid Glass design.When tapping the attachment button in the message input area, the popup with attachment sources appears (Camera, Photo and Video Library, Add file). However, there are a couple of visual issues: The popup is sometimes partially overlapped by the keyboard. The "Photo and Video Library" button occasionally appears without its rounded background, unlike the other buttons. Environment iOS: 26+ Intercom iOS SDK: 19.5.3 (latest) Screen: Intercom chat (Messenger)  

Hi Intercom team, we receive several errors after trying to login a user with attributes using react-native sdk.We check if the user is logged in before making a Intercom.loginUserWithUserAttributes call.A short stack-trace for the error we receive: code: 102,domain: io.intercom.ios.error.network,message: Error in loginUserWithUserAttributes,name: Error,NSLocalizedDescription: HTTP Error: 400 bad requestWe send email and userId to the method call, like this: Intercom.loginUserWithUserAttributes({ email, userId }) Could you help us understand why we still get an error, I’ve run a console.log for both email and userId and both seem legit.

I just shipped a free app called Smart Routing - reads the conversation, suggests which team should handle it + tags. One click to assign.Now figuring out what to build next. Auto-routing? Priority detection? Custom rules?What actually wastes your time when deciding where a conversation should go?

Hello, I’m experiencing a problem where the Intercom chat does not open when a user taps on a push notification on iOS. I have implemented the Intercom React Native plugin as per the documentation, and the messaging functionality works perfectly. Notifications are received correctly, but tapping on them does not open the chat as expected. Environment Details: • Platform: iOS• React Native Version: 0.74• Intercom React Native Plugin Version: 8.1.0 Problem Description: • The Intercom messenger is fully integrated into my app, and users can send and receive messages without any issues.• Push notifications from Intercom are successfully delivered to the device.• According to the documentation, tapping on a push notification should automatically open the relevant chat within the app. However, this is not happening on iOS.• When I tap on a push notification while the app is closed, the app opens but does not display the chat. Instead, it remains on the previous screen or the home screen.• I

I’m following the below document to set up a custom domain for our help centres but am unable to do so given HTTPS (manual setup) appears to not support our domain’s Cloudflare SSL mode (full strict). HTTPS (quick setup) is not available for our existing account1 - Does HTTPS (quick setup) support full strict SSL via Cloudflare?2 - Are we able to have HTTPS (quick setup) enabled for our account retroactively?https://developers.intercom.com/docs/guides/help-center/custom-domainsCheers Russ

Hello,We integrate with Intercom using webhooks. When an admin replies to a conversation, we receive the reply via the conversation.admin.replied webhook event.When AI Inbox Translations is enabled, we continue to receive the original replies through the webhook, but we’re unable to receive the translated versions of those messages.Could you please advise on how translations can be accessed via the API or webhooks? 

  SDK Version: Intercom iOS SDK 19.4.1  Platform: iOS 26.1 Integration: Flutter (via intercom_flutter wrapper) Description:  The close button (X) on surveys does not respond to touch events on iOS. Users cannot dismiss surveys by tapping the close button and must complete the survey to proceed. Swiping down to dismiss still works.  Steps to Reproduce:  1. Initialize Intercom with valid credentials  2. Trigger an Intercom Survey (programmatically via presentContent:surveyWithId: or via auto-targeting)  3. Attempt to tap the close button (X) on the survey modal  4. Observe that the tap is ignored and the survey remains open  Expected Behavior:  The survey should close immediately when the close button is tapped.  Actual Behavior:  The close button does not respond to touch events. No console errors are logged.  Additional Context:  - This issue does not occur on Android - only iOS  - Swiping down to dismiss the survey still works  - No error logs appear in the console when tapping the bu

We are using the Intercom React Native Plugin in our Expo project. We integrate Intercom using the @intercom/intercom-react-native plugin.Below are our project dependency versions: "expo": "~54.0.20" "react-native": "0.81.5" "@intercom/intercom-react-native": "^9.6.1" We are facing an issue where it is not possible to disable push notifications once a device push token has been registered.The SDK provides the method:Intercom.sendTokenToIntercom(token: string)to register a device token. However: Even if we pass an invalid or random string to this method, the user continues to receive push notifications. There is no available SDK method to remove or unregister a previously registered push token. We also verified this behavior using the Intercom REST API: Updating the contact via the PUT /contacts/{id} endpoint does not override the enabled_push_messaging field. Explicitly setting enabled_push_messaging to false or null has no effect. Based on our testing, once a device token is r