Popular Topics

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

Hello community,I'm experiencing an issue when trying to update the phone field in the user profile using the React Native SDK from Intercom.When I send the user data through the SDK method, all other fields are updated correctly, except for the phone field, which remains empty and is not saved.I have reviewed the documentation and understand that the phone number must be in E.164 format, and I am sending it in the correct format. However, the field still does not update.To rule out implementation errors, I tested the same update using the Intercom REST API, and in that case, the phone field is updated correctly using the exact same data.However, when I attempt to update the phone field using the React Native SDK, the value is not saved at all.Has anyone experienced this behavior or knows if I might be missing something?Could this be a limitation or a bug in the SDK? If I try to update the phone field using the React Native SDK with the provided method, it does not get updated. 

Just released Conversation Metrics — an app that shows per-conversation metrics directly in the Intercom sidebar:First agent response time Median agent response time Time to assignment Customer avg response time Longest wait (with snippet showing where the delay happened) Snooze analytics (who snoozed, how many times, total duration) Time to close Message count ReopensIt's free: https://www.intercom.com/app-store/?app_package_code=conversation-metrics-vvnbHere's what it looks like:  Happy to hear feedback or feature requests.

There has a crash happened when opening preview for an uploading file in conversation, this only happened on vivo V1963A.  I'm using the latest version 17.4.2, and the crash still occurs. This was the crash: java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=xxx, result=-1, data=Intent { (has extras) }} to activity {xxx/io.intercom.android.sdk.m5.IntercomRootActivity}: android.database.CursorIndexOutOfBoundsException: Index 0 requested, with a size of 0 The crash only happened on vivo V1963A with a specific path. Open the directory from the top left, select file manager, then documents, and then select any file, the crash will then occur. Thank you

We are experiencing an issue where conversations started via the JavaScript Messenger are not being associated with the company object provided during initialization. While the session ping correctly identifies the active_company_id, the resulting Conversation object via the REST API doesn’t returns companies at all.Steps to Reproduce: Initialize the Intercom Messenger using the window.intercomSettings snippet. Provide a valid user_id, user_hash (Identity Verification), and a company object (including a valid company_id). The Messenger boots successfully; identity_verified is true. Start a brand new conversation as the user. Fetch that specific conversation via the REST API (GET /conversations/{id}). Expected Result: The companies/company_id field in the Conversation JSON response should contain the company object passed during initialization.Actual Result: The companies field is either missing.Technical Context: Identity Verification: Enabled. The user_hash is generated correc

I have installed the Salesforce AppI have all fields syncing between contacts, accounts etc.I have setup the “Maintain lead and account ownership” section and it maps all the right Salesforce users with Intercom users. But….The only field it will not update in intercom is the user/lead owner. This is the one field I need so new conversation are assigned to the correct person. Has anybody come up against this before?  

Hi everyone,I’m seeing a strange issue with how intercom handles some external links shared inside messages and help center articles. One example I ran into was when a user tried to open a page related to the daily telenor quiz.When the link is clicked from an intercom message, some users either get a blank page, a blocked redirect, or the page opens without loading its scripts properly. If they copy and paste the same link into the browser directly, it works fine, which makes me think Intercom’s link handling, tracking, or iframe behavior might be interfering with how certain sites load.I’m wondering if this is caused by security headers, https enforcement, or how Intercom wraps outbound links for tracking. Could things like csp, mixed-content blocking, or redirects affect third-party pages that weren’t designed to be opened inside embedded or tracked links?Has anyone dealt with similar problems when linking out to external tools or informational pages from Intercom, and is there a re

I want to connect the Twitter channel with Intercome, but we need to see how it will happenhow the massaging appearhow will it reflect on the reportcan I send or receive massaging from it or not 

Hi Team,I’m Prakash Hinduja, a consultant and advisor based in Geneva, Switzerland (Swiss) , specializing in crypto, renewable energy, and gold investment. I’m currently looking to integrate the Intercom Messenger on my website to improve customer engagement.I’d love to hear from anyone who has experience with this. RegardsPrakash Hinduja Geneva, Switzerland  

Hi team,I'm looking to upgrade @intercom/messenger-js-sdk from 0.0.13 to 0.0.18 in our Angular application, but I can't find a changelog or release notes anywhere.The npm package doesn't link to a public GitHub repository, and there's no CHANGELOG.md in the package.Could you please:Publish a changelog for the SDK (even just in the README)? Or point me to where release notes are documented?This would help developers assess upgrade risk and understand new features. I've done a diff and can see additions like hideNotifications() and whoami(), but official documentation would be appreciated.Thanks!

I’m seeing an issue with a “blur” overlay being left on top of the conversation window when Intercom loads after calling [Intercom presentMessageComposer:NULL] or [Intercom presentMessageComposer:@”text”]This only happens when building on XCode and only when running on iOS 26. Any other combination (e.g. XCode 16 on iOS 26 or XCode 26 on an older iOS version) worksFeels like a race condition in the loading logic perhaps? But hard to investigate as it’s closed source.This happens on intercom-ios versions 16.6.2, 19.4.1 and several in betweenDoes anyone have any information or a workaround?  

We want to add a note to an Intercom conversation but without impersonating an existing admin user. The API docs suggest that to reply with a note, you need:message_type: note type: admin an admin_idWe’re triggering this from within our app and, under certain conditions, want to programmatically append additional context as an internal note. If there’s another way to attach context to a conversation, that could also work.Ideally, we’d post on behalf of a bot or app, but I can’t find anything in the docs that supports this. Impersonating a user feels like a security risk, and creating a dedicated seat for this purpose introduces its own concerns.Is there a recommended pattern for handling this?

The Jira Cloud–Intercom integration was originally set up by a user who has since been deactivated. As a result, the connection between Jira and Intercom is now broken.How can we restore the integration when the original installing user is no longer active?Reinstalling the integration using a service account may risk losing existing conversations, so we want to avoid that if possible.Can the Intercom Support team assist with safely restoring the connection without data loss?

Hi everyone,I’m working on a project where members access a digital membership card ( for users to open support or access perks via a mobile interface). I’d love to understand how other Intercom users are handling similar workflows.Specifically: Has anyone integrated Intercom with a digital membership card or access card system? Are you using Intercom APIs, Automations, or Workflows to update or verify membership info inside Intercom? Any tips on securely syncing member data ( status, expiry checks) so Intercom can display the correct access level or message? I’m excited to learn how others are solving related use cases in Intercom  thanks!