Popular Topics

We are currently working on our upcoming release to the Google Play Store, ensuring compatibility with Android 15. As part of this effort, we have recently updated our app to use the latest version of the Intercom SDK (15.9.1).During our testing phase, we encountered an issue specific to devices running Android 15. The problem pertains to the UI when attaching a video or image in the Intercom messenger.The "X" close button overlaps with the status bar, making it difficult to close the attachment preview.This behavior is observed only on Android 15 and seems related to the new edge-to-edge enforcement introduced in this version of Android.Here are the steps to reproduce the issue:1. Open the Intercom messenger in our app.2. Click on the attachment icon and choose Gallery.3. Select an image or video.4. Observe that the close ("X") button overlaps with the status bar, making it difficult to close the preview. You can view a screen shot of the issue here: Intercom UI Issue android 15 on at

Release Date: 15-01-2025 🚀 Enhancements Added support for Fin for Platforms. Special notice view now supports links. Note This release contains some beta features.

I’m referencing this documentation: https://developers.intercom.com/docs/references/rest-api/api.intercom.io/conversations/updateconversation I’ve created a custom attribute on conversations called original_post_id (see below)And i’ve been successfully able to PUT https://api.intercom.io/conversations/{id} (200 response code) with the intention of updating the conversation with a custom attribute value:Yet the response shows that no custom attribute with original_post_id, which i’d expect to see populated with the value in my PUT request. I only see one custom attribute, which is ‘Copilot used’. Is the latest intercom API docs up to date? or does updating custom attributes on conversations not work yet?  

Hi! Regarding metrics in custom reports, we’d like to have the SLA hit rate based on the percentage of conversations where the team met the SLA, as shown in the SLA report.Ensuring timely responses to our community is paramount. Measuring the SLA hit rate based on the percentage of SLAs applied to conversations that hit their target (current available metric) can be misleading. For example, if a ticket has four SLA targets, and we hit three out of four, the SLA hit rate would show 75%. However, if we breached the first response SLA, we failed to meet our promise of timely communication to the member, making the true SLA hit rate for that ticket 0%.From our perspective, breaching even one SLA in a conversation means we didn't fully deliver on our commitment.

How can I effectively manage and link multiple workflows in Intercom to ensure seamless automation? I’m looking for guidance on organizing interconnected workflows (Read More), setting up triggers between them, and maintaining clarity while avoiding errors. Any best practices or tips for optimizing linked workflows would be greatly appreciated.

Hello! I’m wanting to know if there is a way to be able to measure and analyze the unique emails or names or users that are being routed to one of the workspaces myself and my team use. Is there a way to see which users are reaching out to us most frequently and about what to better be able to address why the volume is higher for those users?

Can we get list of all articles in a collection using the REST API?

Hi everyone,Our CS team is accustomed to receiving personalized Slack notifications for events like client replies, internal notes, etc., as supported by our previous platform provider. However, it appears that Intercom offers limited options for triggering built-in notifications, and the Slack integration only allows updates to be posted in channels, rather than directly to individual CS agents based on conversation assignments. I’d love to hear how others are addressing this. Are there any effective workarounds you’ve implemented within Intercom using automation, or perhaps an app that helps manage team member notifications? For us, personalized notifications are crucial due to high incoming volumes, as they act as timely reminders for agents to check specific client conversations that are currently in progress. Any insights or suggestions would be greatly appreciated!

Hi everyone,I’m Darshan Hiranandani, I’ve been using the Intercom interface to create notes, and I noticed that I can tag teammates in those notes. However, I’m wondering if it’s possible to do the same when creating notes through the Intercom API.Has anyone had experience with this or know if tagging users is supported when creating notes via the API? Any insights or guidance would be really helpful!Thanks in advance!RegardsDarshan Hiranandani

Hi, there’s an error when exporting tags in the new interface. When will it be fixed?https://www.loom.com/share/0074fbbe98c143dfb9eca4d4e38b5d56 

Release Date: 09-01-2025 🚀 Enhancements Added privacy policy to conversation screen. Updated icons in the more menu when you launch directly into a conversation. Updates to the Powered By Intercom view in conversations. 🐛 Bug Fixes Fixes issue around tapping on a message in a conversation to display timestamps. Fixes accessibility issue with icon colour in special notice view. Fixes an issue that could cause the typing indicator to continue displaying after a message was received. Note This release contains some beta features.

I have created a Python code with using API requests to fetching conversations by different words.However, when I try finding two words that contain in the conversations, it will not response me with any emails.Code here:import requestsimport csv# Replace with your Intercom access tokenaccess_token = 'PUT-YOUR-API-HERE'# URL for searching conversationsurl = "https://api.intercom.io/conversations/search"# Headers for authenticationheaders = {    "Intercom-Version": "2.11",    "Authorization": f"Bearer {access_token}",    "Accept": "application/json",    "Content-Type": "application/json"}data = {    "query": {        "operator": "AND",        "value": [            {                "field": "source.body",                "operator": "~",                "value": "two words"            }        ]    },    "pagination": {        "per_page": 150    }}# Function to retrieve all pagesdef fetch_all_conversations():    conversations = []    next_page_data = data  # Initial data for the first requ

Hi there,I'm attempting to obtain the content message of outbound messages using the content_stat.sms webhook.However, the data received only includes the content_title.Could you please guide me on how to retrieve the full content message of outbound messages through the API or webhook?Thank you.

Noticed that the intercom cookies don’t have the Secure and HttpOnly attributes set. Is it possible to do so?Could this be a security issue for our website without t?

I am getting user not found while trying to get all conversations.Trying to execute it through Postman and passing authorization bearer as well. URL - https://api.intercom.io/conversations'Authorization': 'Bearer <ACCESS_TOKEN>'Content-Type': 'application/json', Postman response -{    "type": "error.list",    "request_id": "003rmrddranpjr8ds4lg",    "errors": [        {            "code": "not_found",            "message": "User Not Found"        }    ]}

We are using PHP api client to add contacts to intercom. Occasionally then requests fail with 404 not found error which is weird since we are creating a new contact.$contact = $intercom->contacts->create($data);Http\Client\Common\Exception\ClientErrorException: Not FoundWe are adding and updating contacts all the time. In the last week we have had ~10 of these so the actual number of failed calls in relatively low but still were annoying.Any ideas what is causing this or how to fix this?

Hi there,The integration was successful and without errors. We can receive messages from users normally, but when FIN tries to respond or our team tries to respond from Intercom, we receive the error in the screenshot attached.When I contacted Intercom support, they gave me the following error message in the backend:"App doesn't have human agent tag access"anyone can help?thanks 

Can anyone share their experiences using Zapier with Intercom for automating workflows? I'm particularly interested in how you've set up Zaps to streamline tasks like lead management, customer follow-ups, or syncing data between platforms. Any tips on best practices (Read More), common challenges, or creative use cases would be greatly appreciated!

Release Date: 17-12-2024 🐛 Bug Fixes Resolves an issue with Fin streaming replies. Note This release contains some beta features.

   Intercom crashes every time you try to attach any type of content (even embedded gifs) on Android 9java.lang.NullPointerException at androidx.compose.ui.node.LayoutNodeDrawScope.drawContent(LayoutNodeDrawScope.kt:49) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$32$1$1.invoke(ConversationScreen.kt:581) at io.intercom.android.sdk.m5.conversation.ui.ConversationScreenKt$ConversationScreenContent$32$1$1.invoke(ConversationScreen.kt:580) at androidx.compose.ui.graphics.drawscope.DrawScope$record$1.invoke(DrawScope.kt:1077) at androidx.compose.ui.graphics.drawscope.DrawScope$record$1.invoke(DrawScope.kt:941) at androidx.compose.ui.graphics.layer.GraphicsLayer$clipDrawBlock$1.invoke(AndroidGraphicsLayer.android.kt:71) at androidx.compose.ui.graphics.layer.GraphicsLayer$clipDrawBlock$1.invoke(AndroidGraphicsLayer.android.kt:66

We have users that has multiple devices.We're using "Intercom for React native" SDK to allow these users to contact us via intercom.When a user contacts us we'd like to know which device is the device is it.We know that there are 2 ways to implement it:Option 1, which we've used till a few months ago, is to login to intercom using the same user in each of the devices, and use a "device_id" conversation attribute to identify the device. We found this method is a bit tricky cause when the user open intercom on another device they'll be able to continue the conversation although the conversation device id attribute is the first one…Option 2, which is currently implemented, was to login to Intercom in each device using a different user, and basically create multiple users for the same customer. It means that the same email address is associated with multiple intercom users. The problem here is that when the user contacts us through the email (sending an email to support@example.com through

Hi Team, We have our app in intercom, where we have customised component with a button of action as sheets and url given.{  type: "button",  id: "start-survey",  label: "Let's begin",  action: {    type: "sheet",    url: "https://url",  },}When we use our app and send this component in a conversation, the mail is also sent. When opening our app from the mail and clicking on the button, the url is not loaded. This used to work fine previously. We are getting the following error.Can we please get help regarding

Hello, We are about to add Germany to our French workspace. Any way to change the langage of what is display when we a customer receive an email: We would like to have it in German for German Inbox, French for French Inbox. Any workaround for this ? Thanks 

I have a script, which attempts to create a contact, and if it already exists but is archived, parses the id from the failed message and deletes the contact. Here are the logs from that script: ```Original contact id: 672291a52c6b471a4b20e202--- now let’s call the delete contact endpoint ---Deleted contact response: {"id":"672291a52c6b471a4b20e202","external_id":"<excluded>","type":"contact","deleted":true} -- now let’s attempt to recreate the contact --[16:45:54.629] FATAL (64427): Failed to recreate contact: {"type":"error.list","request_id":"0011vqbd9jo6drvesao0","errors":[{"code":"conflict","message":"An archived contact matching those details already exists with id=672291a52c6b471a4b20e202"}]}``` As you can see, the delete contact endpoint is returning success, but it’s not actually deleting the contact, because my subsequent attempt to recreate the contact fails.

I'm using Intercom in my React.js PWA,but the tool's default styles don't account for 'safe-area's, causing issues on devices with notches, such as the iPhone. Is there a solution for this? //padding: env(safe-area-inset-top) env(safe-area-inset-right) env(safe-area-inset-bottom) env(safe-area-inset-left); Adding the style to the “body” element would solve the problem, but custom styles aren’t available.