Answered

How can I remove the languages that are enabled for Fin? I have so many languages enabled, and I don’t want them enabled. But if I delete these messages, I can’t save those changes. 

Device: Nexus 5XOS Version: Android 13App Version: 2.0.19 (82)Date: August 22, 2025, 15:22:48 GMT+03:00Issue Description:Our Flutter application is experiencing a ForegroundServiceDidNotStartInTimeException on Android 13 devices when using both Firebase Messaging and Intercom. This error specifically occurs when the Firebase Messaging background service (FlutterFirebaseMessagingBackgroundService) is initiated.Android expects a foreground service to call Service.startForeground() within 5 seconds after Context.startForegroundService() is invoked. In our case, this timeout is occurring, leading to an application crash.Key Detail from Logs:Upon reviewing the crash logs, a significant detail observed is the activity on a thread named DefaultDispatcher-worker-3, which is related to the Intercom SDK. This thread shows operations involving okhttp3.Cache and io.intercom.android.sdk.AppIdentityInjector.initializeEvents. DefaultDispatcher-worker-3:       at okhttp3.internal.io.FileSystem.<cli

I have a light background colour as my header, however the text is white and illegible. How do I change the colour of this text?

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.

Hi, I cannot connect to my admin account in Vietnam. My company is based in France. I have made a research and understand that I need to change the Javascript code into api_base: 'https://[your app ID].intercom-messenger.com' Could you please confirm to me if this is still working as a workaround? If yes, can you show me how to change the Javascript code with screenshots, it would be much easier from my side? Because after doing this, I still cannot load Intercom.If this solution is not working anymore, would it be possible to have another solution on this please? Thank you for your help!Kind regards,Phuong

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

I have a few questions regarding push notifications and ticketing: Does Intercom send push notifications for the following events: Ticket creation? Ticket response? Ticket status updates? Is it possible to send a push notification when a ticket has been processed? If so, what is the recommended approach to implement this?

Android API 36 is ignoring the orientation configuration. The Android SDK is fixing the orientation as portrait. We have got the following warning on Google Play: From Android 16, Android will ignore resizability and orientation restrictions for large screen devices, such as foldables and tablets. This may lead to layout and usability issues for your users.We detected the following resizability and orientation restrictions in your app:<activity android:name="io.intercom.android.sdk.activities.IntercomCarouselActivity" android:screenOrientation="PORTRAIT" />To improve the user experience for your app, remove these restrictions and check that your app layouts work on various screen sizes and orientations by testing on Android 16 and below.Would it be possible to avoid orientation restrictions in the SDK?

Are there plans to add more to Article reporting?Specifically, I’d love to see the filter options from other reports on Intercom so I can easy have a breakdown of the views an article gets in different languages or be able to filter to see how many users from a specific customer are viewing an article. 

I am experiencing an issue with the tracker ticket system in Intercom. I have a set number of tracker tickets that I use to organize my inbox, but occasionally, the system creates duplicate tickets for the same issue. This results in multiple (sometimes three) tracker tickets for a single conversation, which makes inbox management less efficient and can cause confusion. Do you know why this is happening?  Or how I can stop it?

Is there any roadmap for being able to add multiple email addresses to a contact?We integrate with Hubspot and we can merge profiles together in the console along with being able to have multiple email addresses for the same contact. The issue we are facing is that we have someone reach out to us who isn't authenticated and they enter their email address, it's different to the one they authenticate with and it creates a lead profile. Or the send us an email or they reply to an email in a thread from a different email address. It creates them as a lead.We can have some users with 4 different email addresses, but they're the same person representing different brands. We treat them as 1 user in our platform also.Intercom counts them as 4 people towards your contacts and also holds it for 90 days since the last contact which means we end up using more contacts than we really are. It would be handy if you can identify them in the console and hit a merge function, the same way Hu

Hi everyone!I’ve uploaded a glossary with 3 languages (default Traditional Chinese, plus English and Simplified Chinese).However, when I run workflow auto-translate, it only applies correctly to one term (in one workflow button).Here’s what I’ve tried so far: Re-uploaded the glossary Turned off all workflow auto-translate and turned it back on But the workflows still don’t translate according to the glossary.Has anyone experienced the same issue? Or any advice on how to get the workflow auto-translate to fully follow the glossary? 

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 reviewing our platforms to ensure they meet the requirements of the European Accessibility Act (Directive (EU) 2019/882).For support services such as Intercom, the EAA requires that: Help desks, call centres, technical support, relay services, and training services provide information on the accessibility of the service. Services must be compatible with assistive technologies (e.g., screen readers, braille displays, voice input). Support and communication must be offered in accessible modes (not only voice but also text, relay, or other inclusive formats). Documentation and guidance should be provided in a clear, understandable, and perceivable format. This is meant to ensure that customers with disabilities can get support in a way they can actually use. For example: A deaf customer might need a text-based chat or relay service. A blind customer might need documentation in a format that works with screen readers. Training on how to use the service with ass

I'm curious to learn how some companies using Intercom keep track of conversation topics or common query themes without having to manually tag each conversation.We occasionally need to pull reports for customers to highlight common questions or trends, and I'm looking for ways to make this process more efficient.Would love to hear any best practices or tools you recommend!

Hi everyone. In my workflow, I am using a custom action, which tests in the test step of the action builder without errors: In the following result step of the action builder, I am (trying to) map the results as follows: In my workflow, I am calling the action like so, however, although the request goes through without errors the answer fields {{business_name}} and {{address_city}} are not shown in the answer: Clearly, I am doing something wrong mapping/linking/using the result, but I can’t figure out what. Could somebody kindly assist? Sunny greetings from Belgium! :) 

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.

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

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.

I added a “New Converstation” widget in Home but it is not visible to the visitorsOnly “search for help” widget is visible.“New Converstation” widget should be added under “search for help” widget.How can i fix this issue? 

We would like to request a new data point in the reports section for tickets: "Last Comment”. 

Hi,I created data connector to connect Intercom to Zendesk and tested it. It creates a Zendesk ticket at that testing phase. Then I created a workflow where I trigger the Zendesk data connector if the customer requests talking to a human and offer to add Name and Email. There are two paths: first path (A, when selected, tells the requester that a ticket was created and second path (B) in case the ticket creation has failed.In the preview, it shows that path A was selected and a ticket was created (without receiving concretely a ticket on Zendesk but this is fine since it is preview). When I make live test, it shows always path B i.e. connection to Zendesk has failed. There are no logs shown in the Intercom account. It is impossible to debug I contacted you since last Friday to get human assistance and I followed all the instructions then silent radio for 24 hours.  We are paying a lot of money for a service not working as announced and with no assistance. On our way to cancel subscript

We use Intercom in Russia and due to blocking by Roscomnadzor we can’t collect surveys (customers see no emoji and either click the bad rating on accident or don’t leave any). My question is if we can somehow make a workflow which collects surveys and feedback? We can’t just use the “collect feedback” feature since the emojis don’t work

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).