Pioneer: A summit where CX leaders redefine what's possible
-
Recently active
Release Date: 02-07-2026 🐛 Bug Fixes Fixed an issue where the composer could retain text after sending a message dictated with the iOS keyboard.
Release Date: 01-04-2026 🐛 Bug Fixes Fixed an issue where some conversation parts may not appear when launching directly to a conversation. Fixed an issue where duplicate conversation screens could appear when launching directly to a conversation. Fixed an issue where text colors could appear incorrect in Note and small Post messages. Fixed an issue where YouTube video thumbnails could fail to fill the full container width.
Release Date: 16-12-2025 🐛 Bug Fixes Fixed an issue where localizations could fail to load. Fixed an issue the composer text occasionally wasn't cleared after sending a message.
Release Date: 04-12-2025 🚀 Enhancements Added titles to the Messages screen to help users differentiate between their conversations. 🐛 Bug Fixes Fixed an issue where image height within carousels was incorrectly capped.
Release Date: 17-11-2025 🐛 Bug Fixes Fixed a crash related to ICMPersistenceProxy where reading objects from cache was not correctly handling errors.
Release Date: 24-10-2025 🚀 Enhancements Added support for transcribing messages using your voice. To enable this feature, add the following to your Info.plist: xml <key>NSMicrophoneUsageDescription</key> <string>YOUR DESCRIPTION HERE</string> 🐛 Bug Fixes Fixed an issue where composer buttons and help center articles could render incorrectly on Liquid Glass. Adjusted how translations are bundled resolving an edge case where they could fail to load correctly.
I want to make this post as I have spent the last day trying to understand why the X-Hub-Signature being sent in the header wasn’t matching the the HMAC signature that I was getting when converting the JSON body and Client Secret from the request.If you are using Python, MAKE SURE YOU USE SEPARATORS IN THE JSON DUMP BEFORE ENCODING. Here is the method that worked for me: def authenticate_intercom_request(self,x_hub_sig): json_string = json.dumps(self.body, separators=(',', ':')) hashed = hmac.new(self.secret.encode('utf-8'), json_string.encode('utf-8'), sha1) return hmac.compare_digest(hashed.hexdigest(), x_hub_sig[5:])Python by default will add chars in the body that will alter the returned value from Intercom, and without the separators listed above it will always fail.
Release Date: 24-09-2025 🐛 Bug Fixes Fixed device token registration for JWT-based identity verification. Previously, when identity verification was enabled with JWT tokens, device token registration would fail with error 4003. The SDK now properly supports both HMAC and JWT tokens for device token registration.
Release Date: 18-08-2025 🚀 Enhancements UI Improvements for events in conversations.
Release Date: 08-08-2025 🚀 Enhancements Typing indicators are now shown in the Messages screen.
Release Date: 14-07-2025 🚀 Enhancements You can now present specific Tickets with the presentContent method. Tweaked dark mode colors to be more harmonious.
Release Date: 26-06-2025 🚀 Enhancements Added support for Dark Mode. This feature is currently in beta, and will be enabled for all customers in a future release.
Release Date: 06-05-2025 🚀 Enhancements Improved handling of conversations merged across channels and conversations merged between users.
Release Date: 23-04-2025 🚀 Enhancements Some improvements to the rendering and height management of messenger apps.
It seems that connecting my intercom account to the community here has locked in my username. I’d rather not have my full name on posts, but it doesn’t seem like there’s a way to change my username. Is there any way to change it? For reference, I know that Gainsight (the community platform that the community is built on) has the option to use SSO and still let users choose their own usernames. Personally, I prefer that in communities than being forced to use whatever details are pulled across by the SSO. Thanks!
Hi Intercom support,It seems like something quite big was added to the intercom-ios repo on Github, such that cloning the repo is now a >3GB download.(see https://api.github.com/repos/intercom/intercom-ios -- size: 3144481!)SwiftPM does deep clones, so a fresh build on xcode now takes several hours due to waiting for the intercom package.Can something be done about this?Cheers,Tom McLean
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
We've had the iOS Messenger down for ~2 months on our production app (React Native, @intercom/intercom-react-native 10.3.4, US workspace, appId m4e3h09o). Android works fine with the identical integration.Symptoms: the Messenger opens but content stays empty; the native console shows repeated "network error – the data couldn't be read because it isn't in the correct format" on update-user and fetch-composer-suggestions. curl to api.intercom.io succeeds, so it isn't connectivity — the SDK is receiving a response it can't parse (JSON deserialization failure).What we've already done: confirmed appId + iOS key resolve to the same workspace; ruled out init order, ATS, SSL pinning, duplicate packages and region routing.The telling part: a minimal, empty Expo project with the same appId/key loaded the Messenger correctly on one run, then reproduced the exact same error on a later run — with nothing changed locally. An identical client that passes and then fails with zero local changes points
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?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.