Popular Topics

Hi everyone,I'm exploring ways to enhance customer support at our shooting range facility. Specifically, I'm interested in integrating shooting range software with Intercom to streamline operations and improve client interactions.Has anyone here implemented such integrations? I'm particularly keen on automating booking confirmations, handling membership inquiries, and providing real-time assistance during range sessions.Any insights or experiences with connecting range management systems to Intercom's suite would be invaluable.Looking forward to your recommendations!

I found the Webhook Topics article (https://developers.intercom.com/docs/references/webhooks/webhook-models) but cannot find the schema of specific notification item types. I’m specifically looking for conversation.user.replied.

Hi everyone! Is there anyone here using the Linear integration? We just added it and the search option to find and link a conversation to an existing issue or project is not working. It’s not showing relevant results. 

We’re using Intercom Android SDK 15.1.3. We use the Intercom.client().present() API to show the help center in our app.Our app currently requires READ_EXTERNAL_STORAGE permission and the only reason for this permission is for Intercom’s image attachments feature.From Android documentation, on API 33, READ_EXTERNAL_STORAGE is replaced with more granular permissions like READ_MEDIA_IMAGES etc. However, it also states that you can use the PhotoPicker to get the same behaviour without any permissions; and with the jetpack library PhotoPicker is available all the way back to API 19.My question is: Does Intercom Android SDK use PhotoPicker? What about on pre-API 33?The only reference to this I see is in the changlog for Intercom Android SDK v12.5.3 but it is not clear what that means for an app that integrates this SDK.

Hello, It seems we cannot reliably use Intercom on iOS due to an API error. We are trying to identify a customer with a uuid, email, and identity hash (derived from the uuid). Our integration was working until we upgraded to the 14 SDK. Now everytime we call either loginUser or updateUser we receive a “400 user already exists” error message. This happens for some users and not others, but is resulting in production customers not being identified.

Fatal Exception: java.lang.IllegalArgumentException: Missing keys: [timestamp] in '{teammate} moved ticket into {status} {timestamp}'       at io.intercom.android.sdk.utilities.Phrase.format(Phrase.java:189)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.TicketInAppNotificationContent(InAppNotificationCard.kt:180)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.InAppNotificationCard(InAppNotificationCard.kt:124)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:75)       at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:74)       at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:109)       at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:35)       at androidx.compose.runtime.Composit

Our advisors are using Microsoft machines and the Phone feature in Intercom within the contact centre. A few of them are experiencing issues where their microphones are picking up ambient background noise, which customers can hear.Has anyone else encountered this issue, and does anyone know how to resolve it? All the devices appear to be set up the same way, and nothing obvious is standing out as the cause.

Hi, We’re currently modelling our Intercom data. In the modelling process, I can’t find the answer to the following:How do we determine whether a conversation was started through the Intercom Chat on our web application or our mobile application? How do we determine whether a conversation was started and/or resolved by the automation workflow (self-service)?The source_type and first_contact_reply_type only indicate whether the conversation was started through 1) email, 2) conversation, 3) instagram. Hoping you help guide us to finding the necessary data.

Hello, I need to integrate Intercom into react-native app. I’m using official wrapper intercom/intercom-react-native. Android works as expected. On iOS I’m always getting `BadDeviceToken` listed as an issue in Intercom panel (website). I tried both ways to send the token to the intercom, first is native code (option 2 from here) and later tried JS option with token coming from @react-native-firebase/messaging `getToken` method.APN configuration is uploaded to Intercom and same values works properly when sending push messages from Firebase (both their website and java/nodejs SDK).I’m testing on the simulator (again messages from Firebase and our backend works fine).

I have already started a conversation through app but the solution offered is not a solution at all.Since we started using Intercom, we run all our support operations both for customers and potential users via Intercom conversations.Now many of our users are complaining that they cannot reach us out via support button and when we connect to their device and check the Intercom CDNs are banned by their modem. The affected user count increases day by day and our support team spends extra effort and time just to try to make it whitelisted, so instead of focusing the real problem Intercom now causes a time loss to fix the support button. Even our reputation is damaged because people need help about an issue but they cannot get to us effortlessly.This screenshot is taken from one of our customers’ device, they don’t use any adblocker but their modem does not allow to open the script because of safety issues: Sorry, but its unacceptable for you to tell us “tell your customers to whitelist Int

Recently, we have a lot of Fatal Exception: Java.lang.illeglegalstateexception.v15.15.0 and v16.3.0I attach the entire stack trace errors:          Fatal Exception: java.lang.IllegalStateException: The specified child already has a parent. You must call removeView() on the child's parent first.       at android.view.ViewGroup.addViewInner(ViewGroup.java:5401)       at android.view.ViewGroup.addView(ViewGroup.java:5216)       at android.view.ViewGroup.addView(ViewGroup.java:5156)       at android.view.ViewGroup.addView(ViewGroup.java:5128)       at androidx.compose.ui.viewinterop.AndroidViewHolder.<init>(AndroidViewHolder.android.kt:99)       at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:332)       at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:323)       at androidx.compose.ui.viewinterop.ViewFactoryHolder.<init>(AndroidView.android.kt:342)       at androidx.compose.ui.viewinterop.AndroidVi

Hi, I need your help with user data not showing correctly in Intercom.We are initializing Intercom with name, user_id, email, and user_hash.Everything works fine for most users, but starting from 3 weeks ago, new users only show user_id, and name and email are missing on their profiles.At first, we suspected it might be an issue on our end. However, we’re also sending the exact same user data to Pendo, and it’s working perfectly there — all fields are showing as expected.Could you help us check if there were any changes on Intercom's side, or suggest what else we can verify to resolve this?Thanks!

In our app we are sending Intercom Posts with universal links in them and opening a link from a post within the app does both - triggers the deeplink action and also opens Safari. In our AppDelegate we return true from application:continueUserActivity:restorationHandler: and even when we completely remove all deeplink related logic and the method contains nothing but return true it still opens Safari, this behavior contradicts to what's written here. We have IntercomUniversalLinkDomains configured in the Info.plist file. Expected behavior: Do not open Safari when a url is matched with an entry from IntercomUniversalLinkDomains  and application:continueUserActivity:restorationHandler: returns true.iOS SDK version 16.2.3  

Seeing a new crash on Samsung Galaxy S24 Ultra (in the field)  Android 15At least 3 different users all with this same device.  java.lang.IllegalStateException (crashed)ViewTreeLifecycleOwner not found from android.widget.FrameLayout{ff120ae V.E...... ........ 0,0-1080,2340 #7f0a04d4 app:id/intercom_overlay_root}androidx.compose.ui.internal.InlineClassHelperKt.throwIllegalStateExceptionForNullCheck (SourceFile:34)androidx.compose.ui.platform.WindowRecomposer_androidKt.createLifecycleAwareWindowRecomposer (SourceFile:455)androidx.compose.ui.platform.AbstractComposeView.ensureCompositionCreated (SourceFile:250)androidx.compose.ui.platform.AbstractComposeView.onMeasure (SourceFile:285)android.view.View.measure (View.java:29591)android.view.ViewGroup.measureChildWithMargins (ViewGroup.java:7383)android.widget.FrameLayout.onMeasure (FrameLayout.java:207)android.view.View.measure (View.java:29591)android.view.ViewGroup.measureChildWithMargins (ViewGroup.java:7383)android.widget.FrameLayout.o

When a user replies to an email notification from Intercom Messenger, the email is duplicated. Has anyone found the cause and a solution to this issue? 

Hi everyone,I’ve been sending newsletters and promotional emails for my small business, but a significant number of them are ending up in recipients’ spam folders.I’m trying to improve engagement, but low deliverability is holding me back. I’ve heard about authentication protocols like SPF, DKIM, and DMARC, but I’m not sure how to implement them correctly.Can anyone share practical tips or strategies for maintaining a clean email list, avoiding spam triggers, and improving sender reputation?I’d love guidance on how to increase email deliverability effectively without overcomplicating things.

I'm seding custom attributes using the update function from react-use-intercomBut I'm having problems using those custom attributes in the text and messages on the intercom painel After reseach a lot, I found those 3 options, but I couldn't find any oficial documentation about it// {{custom_token}}// {{prop.custom_token}}// {{custom_attributes.custom_token}}could someone confirm to me, how is the correct syntax is to use the custom attributes as placeholders in my texts

Hello everyone, our app (Coview) implemented the health check. Based on the following description from the documentation, we assumed that we would receive at least one call for each of the installations of our app each day: This will happen at least once a day for each workspace where the app is installed. With this information, we expect you to discover if the app is in a healthy state for this workspace and respond to the request telling us whether it's healthy, unhealthy, or you don't currently know.However, according to our logs we just a handful of checks each day although we have a few hundred installations. Do we misunderstand something here?

Hi everyone,I'm seeking advice on effectively managing our company's online reputation using Intercom. Specifically, how can we leverage Intercom's features to monitor customer feedback, address concerns promptly, and build trust with our audience?For more insights on this, you might want to check out Reputation Prime. Are there any tools or integrations within Intercom that can assist in this process? Additionally, how can we ensure our team maintains a consistent and positive tone when responding to customer inquiries?Any insights or experiences would be greatly appreciated.Looking forward to your suggestions!

I’m curious if there is a known issue with the Users Scroll API? The Company one works just fine, but the users one returns that it is not a valid resource.I found a github incident from 2018 where something similar happened and I’m wondering if something similar is at play again. I notice that the users scroll documentation page doesn’t have a Try It option like Companies does, which leads me to believe it may be a known issue that the endpoint doesn’t actually work.Current Documentation: https://developers.intercom.com/docs/references/1.3/rest-api/users/iterating-over-all-users

Hi there,we’ve recently added events tracking and it was noticed that we get ad hock "User Not Found" error however user exists years. Request we send:{  "event_name": "post_autopublished",  "created_at": 1731959712,  "user_id": "..."} Response we received:{  "type": "error.list",  "request_id": "0045a0lc51qku6vpphg0",  "errors": [    {      "code": "not_found",      "message": "User Not Found"    }  ]} Retrying the API call can work but would be great to know what causes the issue. Any help would be appriciated. Best,Antal

It seems that in v2 when the User and Lead models have been merged into Contacts, the session_count attribute has been removed from the response.  The Company object displays the session_count information so I'm wondering if there's a specific reason why the user session_count has been removed or if it's just a slip?

I’m getting “Something went wrong loading this message” error.  And I see below JavascriptError.vendors~sentry~app.47087327.js:1 DOMException: Failed to execute 'setAttribute' on 'Element': 'data-といったエラーが発生する。' is not a valid attribute name. at g (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:368553) at Qs (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:451809) at Sc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:474108) at xc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:473848) at bc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:473715) at gc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:473578) at uc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:470413) at fc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:470795) at Vo (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:411940) at https://js.intercomcdn.com/vendor.b8d3fa93.js:2:468368

The Contacts model have an attribute called language_override, but when I try to set it when creating a new Contact, or to update it on an existing Contact the attribute seems to be ignored. Docs also doesn't mention it for those operations, so I guess that is as-designed. Is there any way I can change it?

Hello Intercom Team,We are using @intercom/intercom-react-native for in-app support, which is a core feature of our app. Users often need to attach screenshots when contacting support.According to the official documentation, the SDK requires storage permission. On Android 13+, this maps to READ_MEDIA_IMAGES.However, Google Play has rejected our app, even after appeal, because this permission is considered sensitive. They are asking us to justify its usage, and one-time photo pickers are not accepted since the Intercom SDK manages its own gallery internally.This is now blocking our app release. We saw intercom-android PR #587 regarding Android 13 media permissions. Can you please confirm if this is the only way for the SDK to work, or if you plan to move towards the system photo picker (which Play Store prefers)? Is there an official statement from Intercom that we can submit to Google to justify this permission? This is a critical blocker — without this permission, our users cannot