Popular Topics

We are utilising the 6.0.2 version of the capacitor-community/intercom package, which is using a 12.x version of the Intercom Android SDK internally.What seems to be happening is that when the plugin registers it is making an initial call to Intercom (probably for the reasons outlined in this thread: Our JS implementation code does not do anything until the user logs in. At which point we call `setUserHash` and `registerIdentifiedUser` respectively. We then have a button that launches the intercom bubble (displayMessenger).On a fresh install an Android 15 this works fine. We can login, click the button and intercom launches. On Android 16 it doesn’t. If you exit the app and restart it works fine from that point onwards.When monitoring the logs on the Android 16 device, with a release build, we get this error immediately upon app launch, before the user has a chance to interact (or even grant permissions for things like push notifications):Failed to register or update user: {"type":"err

Hello, according to FIN there is no way to merge conversation besides using the UI. Can you confirm if this is true? Merging conversations via api is a crucial part of our workflow. 

From virtual styling to personalized product recommendations, AI is reshaping eCommerce. How do you think jewellery brands like Ears Decor can use AI to improve the customer experience? Explore their collections at https://earsdecor.com.

AI is changing how customers discover and buy jewellery through personalized recommendations, virtual try-ons, and smart search. I noticed Ears Decor uses a modern online shopping experience for diamond and gemstone earrings. Do you think AI will become the standard for jewellery retailers? https://earsdecor.com

I have the Slack integration working, so all messages sent via the live chat widget on our webiste are going to a Slack channel. How can I set it up so replies in a Slack thread go back to the Intercom conversation, and to the live chat widget? I have tried builing a “Teammate sends any message” workflow, and also a “Teammate adds a note” workflow, but neither one worked. Any suggestions?

Hi team,We're integrating Intercom's MCP server into Fieldwork, an AI agent platform for consumer-brand operators. Our users connect their own Intercom accounts, and the agent calls Intercom tools on their behalf.Dynamic Client Registration against https://mcp.intercom.com currently returns:{ "error": "invalid_redirect_uri", "error_description": "Redirect URI https://app.getfieldwork.ai/api/connectors/oauth/callback is not in the allowlist, reach out to Intercom Customer Support if you believe we should support it"}Following the format Seán set out in the earlier thread on this:Product or tool name: Fieldwork (https://getfieldwork.ai) Exact redirect URI to review: https://app.getfieldwork.ai/api/connectors/oauth/callback Production or staging: production (our only environment) MCP endpoint targeted: https://mcp.intercom.com Use case and distribution model: Fieldwork is a multi-tenant SaaS product. Each end user authorizes their own Intercom workspace through OAuth 2.1 authorization c

EXC_BAD_ACCESS: Exception 1, Code 2, Subcode 6132301816 >Stack overflow  CoreFoundation      0x193f04a10  __CFStringEqual  CoreFoundation      0x193f39e24  CFCachedStringEqual  CoreFoundation      0x193f39dc0  _CFXNotificationRegistrarFindName  CoreFoundation      0x193f63ea8  CFXNotificationRegistrarFind  CoreFoundation      0x193f63864  _CFXNotificationPost  Foundation          0x1911b1088  -[NSNotificationCenter postNotificationName:object:userInfo:]  Intercom            0x105a9d1b8  -[ICMRootViewController postIntercomModalViewControllerWillHideNotification]  Intercom            0x105a9c2e0  -[ICMRootViewController closeIntercomModalWithCompletion:]  Intercom            0x105a9bee8  -[ICMRootViewController dismissAllIntercomViews]  UIKitCore           0x199e1dd40  -[UIViewController dismissViewControllerWithTransition:completion:]  UIKitCore           0x199e1d92c  -[UIViewController dismissViewControllerWithTransition:completion:]  UIKitCore           0x199ee4784  -[UIViewContro

Is it possible to change the Data Hosting Region Configuration at runtime? We’re using native Android and iOS apps. The documentation says we need to set the region in the AndroidManifest or the plist (iOS). But we have US and AU customers. Attempting to just change the app ID and API key grabs most of the helpful stuff (I can see the icon color changing for example...) but when opened, the Intercom app just says “Something’s gone wrong.”Are mobile apps able to support multiple regions with Intercom?

 Hey community,Trying to connect Intercom to our Discord server and hitting this error:"This bot can't join more servers as it has not been verified or is requesting gateway intents it has not been verified for."Fin confirmed the bot is pending Discord verification and there's no workaround. Raised it with Engineering Support, they confirmed it's a known bug, created a ticket, no ETA.A few questions:Is anyone successfully using the Discord integration right now? Was there a point where it worked and stopped, or has it never worked? Any workaround — e.g. does the server need to be a verified/community Discord server?Seems like a critical gap given Intercom is promoting it as a supported channel. Curious if others are affected.

Bug Report: Unrecognized selector sent to CPTemplateApplicationScene (CarPlay) — iOS 27 Summary The Intercom iOS SDK crashes the host app with an **unrecognized selector** exception when aCarPlay scene is involved in scene lifecycle. Intercom sends a `UIWindowScene`-only selector to`CPTemplateApplicationScene`, which is a sibling of `UIWindowScene`, not a subclass — so themessage is unhandled and the app terminates. This is the same long-standing defect previously reported as`-[CPTemplateApplicationScene windows]: unrecognized selector`( and )On **iOS 27** the selector has changed to a different `UIWindowScene`-only API: -[CPTemplateApplicationScene _enhancedWindowingEnabled]: unrecognized selector sent to instance Environment Intercom SDK | 19.3.2 (intercom-ios-sp, SPM). Also reproduces on latest 19.6.3 — updating does not fix it.iOS 27 (also historically reproduced on earlier iOS with the `windows` selector variant)SwiftUI/UIKit app with a separate CarPlay scene (`CPTemplateApplicati

I work for a company that rents out vehicles. We've introduced a user attribute that displays the license plate of the vehicle that is being reserved. As soon as a user reserves a different vehicle, this attribute changes into a different license plate.  I want to be able to instantly start a chat, or send a message, as soon as this attribute changes. During our tests we were only able to send chats and posts when a user matches the rules at the start of their session when they launch our app, but not after that. Does anybody have any idea on how to send chats, post, carrousels etc. after the initial launch of our mobile app?

Release Date: 01-07-2026 🐛 Bug Fixes Fixed a crash that could occur at launch on some iOS Simulator runtimes.

The Intercom platform has following webhook topics: - conversation.admin.replied -- Admin conversation replies - conversation.operator.replied --  Fin/Bot replies to a conversationHere all topics https://developers.intercom.com/docs/references/webhooks/webhook-modelsDuring the tests with reusable workflow, I noticed that Bot replied are send in both topic. As a result, service receive two messages.Below an example of Bot reply message in `conversation.admin.replied`:{ "type": "notification_event", "app_id": "l4e36xhv", "data": { "type": "notification_event_data", "item": { "id": "215474343849634", "...": "...", "conversation_rating": null, "title": "Andrew", "custom_attributes": {}, "conversation_parts": { "type": "conversation_part.list", "conversation_parts": [ { "type": "conversation_part", "id": "4576

Release Date: 09-06-2026 🚀 Enhancements Added security enhancements. 🐛 Bug Fixes Fixed a crash that could occur during app launch.

Clari and Salesloft announced the gradual sunset of Drift in March 2026. No hard end-of-life date, no confirmed migration runway. If you're waiting for a firm deadline before you act, that deadline may arrive with less lead time than your data volume requires.This is what to prioritize before your access disappears.The data that's hardest to recover once it's goneNot everything in Drift carries equal weight. Contacts and lead records are relatively portable — CSV exports handle most of it. What's harder to reconstruct is conversation history: transcripts, timestamps, assignees, thread structure, tags, and the metadata that makes historical conversations searchable and useful.Drift enforces a 600 requests/minute API rate limit. That's the hard ceiling on extraction speed regardless of which method you use. If conversation transcripts matter to your team — for training, compliance, context, or handoffs — budget 2–3 weeks for the extraction alone. That's not a migration timeline. That's j

Hey everyone - just shipped TicketReel, a Canvas Kit app I built for the Intercom inbox.The idea: when an agent resolves a ticket, they add an internal note with the resolution steps, then click Generate Video in the TicketReel panel. The app turns that note into a 60-second branded AI avatar video — scripted by GPT-4o, rendered via HeyGen, captioned via Whisper — and posts the video link back to the conversation as an internal note.The video can be shared with the customer or published to your knowledge base, so the same resolution helps future customers who hit the same issue.Built with Canvas Kit + the Conversations API. Happy to answer any questions about how it works under the hood.App Store listing:https://ticketreel.chriscastle.com/   

If you're still on Drift, you've probably heard: Clari + Salesloft announced the gradual sunset of Drift in March 2026, with no hard end-of-life date confirmed. A vague timeline isn't a safety net — it's a risk. Post-acquisition, releases slowed, CSM support was eliminated for most accounts, and a 2025 data breach took the platform offline for ten days with limited communication. That's what you're migrating away from.  Why Intercom?The use case overlap is real. Intercom has evolved into a full AI-first platform that combines live chat, ticketing, and Fin AI in a unified workspace — so if your Drift setup handled both inbound leads and post-sale support, Intercom handles both natively.A few things that matter when you're comparing:Pricing: Drift's minimum entry was $2,500/month. Intercom's Essential plan starts at $29/seat/month and includes a shared inbox, Fin AI, and a help center. Integrations: Intercom offers 400+ integrations across support, analytics, and marketing. Drift's deepe

We’re migrating from Zendesk to Intercom.In our App, we have notes that preserve certain actions and any associated Zendesk tickets with URLs to that ticket, like https://{workspace}.zendesk.com/agent/tickets/12345.We’d like to record a direct URL to a ticket in the same fashion with Intercom. However, it’s not immediately apparent what that URL would look like.If I have just created an Intercom ticket via the API with id 12345, what would the URL to that ticket look like?

Hi there.Intercom chat does not load on Safari Mobile (iPhone). The window.Intercom object is not available, and the chat widget does not appear. However, the same implementation works correctly on: Chrome (desktop and mobile) Safari on macOS desktop Expected behavior Intercom should initialize and expose window.Intercom, and the chat widget should be available on all supported browsers, including iOS Safari. Intercom is integrated via GTM and it’s initialized in a React hook: Library: react-gtm-module

Hi,I’m using the Intercom Messenger SDK in a React application and I’m trying to pass contextual data onto the conversation as conversation attributes.For example, I want to set values such as:workspace_name workspace_id current_url subscription_plan item_id item_title item_urlThese values are specific to the conversation the user is starting, as a user may be in different workspaces or different parts of the application at different times, so storing this as user attributes is not appropriate because the values can change from conversation to conversation.Fin suggested updating user attributes via the SDK, but that does not solve the problem for us. We need the data attached to the conversation itself, so it can be used reliably in Workflows, Inbox, and downstream connectors.It feels like the Messenger SDK should support setting conversation attributes when opening or creating a conversation. I’d prefer not to make a separate REST API call to update the conversation after it has been

Scribe tutorial videos are very helpful for customers.  We would like to embed in Intercom using iframe.  Is this something product is considering, or may have already implemented?

Hey everyone,Small finding I wanted to share for those of you who prefer a cleaner workspace.A common complaint is that Intercom is browser-only, but there's a neat trick to make it feel like a proper desktop app, at least visually. No extra software needed. Here's how:Press Windows + R, type the following, and hit Enter: chrome --app=https://app.intercom.comIn the code snippet above and in the following snippets below, the command is shown as chrome -, but it should be chrome - - (double dash). However, the markdown editor converts this to just one dash. If you simply copy the commands everywhere, it will always be correct!This opens Intercom in a stripped-down Chrome window: no tabs, no address bar, no browser toolbar. It sits in your taskbar like any other app and feels much more focused.To be clear: this doesn't improve performance, loading times, or anything under the hood. It's purely a visual/UX improvement for those who like a dedicated window without browser distractions.Inter

I noticed a regression in conversation webhooks. The regression effects messages with embedded images.Previously, in version of API 2.14 , embedded image in a message (e.g. paste screenshot from clipboard) was send as in webhook as an embeedded `IMG` in conversation part’s body. After releasing 2.15, the behaivor of v2.14 also has changed. The embedded image(-s) are available both in `body` and `attachments`. As a result, users receive a duplicated images in replies. Is there a way to restore the previous behaivour for v2.14 and not include an embedded images in `attachments`? Example of conversation part from webhook payload (v.2.14):{ "type": "conversation_part", "id": "45209530418", "part_type": "assignment", "body": "<p class=\"no-margin\">Image test<br>​</p>\n<div class=\"intercom-container\"><img src=\"https://downloads.intercomcdn.com/i/o/l4e36xhv/2373221822/cdc43c786608e690132109617c4e/image.png?expires=1778501700&signature=2421a4a292d391e9aeb

For those of you managing multiple brands within Intercom, I'd love to hear about your approach and any lessons learned.What best practices have worked well for you when using Intercom and Fin across multiple brands? Are there specific do's and don'ts you would recommend?Intercom appears to be optimized primarily for single-brand organizations, so I'm interested in learning how others have structured their instance, content, workflows, and AI experiences to support a multi-brand environment.  As an Intercom Manager, my focus is on managing the customer experience, support operations, content, and AI performance—not on building and maintaining complex technical integrations or data connector strategies. We have dedicated teams for that. I'm particularly interested in understanding how other organizations have kept multi-brand management simple, scalable, and sustainable from an operational perspective.What has been most successful for your team? And just as importantly, what mistakes or

I was wondering if there’s a timeline or expected timeframe at least to when can we expect intercom’s MCP to expand outside the US hosted servers?