Active since last visit

 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.

Our need is to have agents always taking chats/calls at all times, without ability for them to switch away from one or the other.  A setting that prevents agents from modifying this is desirable.

 Yesterday and today we experienced two inbound phone calls in a short period where the phonecalls entered the Hold and assign call step and remained In queue.No available teammate was automatically offered the call, even though atleast one teammate was active and could immediately answer the call manually.Can someone of Intercom check the backend routing logs to determine why no teammate was selected for automatic assignment for these conversations? I've already tried to figure out what might have gone wrong, based on the logging I am thinking it might have something to do with the away status and how we have configured our workflow, but no clear reason could be determined.We have enabled Show team composition in conversation event log, but no team composition events are written to the conversation timeline for new inbound calls. Is there any prerequisite for this feature, or is it expected to work for all Phone conversations?We compared a successful inbound call with a failed inbound

We would love to see an option that allows callers to remain in the queue without having to make an active IVR selection.In our market, the most common expectation is simply to wait for an answer. Requiring callers to press a key to continue waiting can create unnecessary friction and may lead to confusion or abandoned calls.An option to let callers stay in the queue automatically, while still offering callback or other choices as optional alternatives, would create a more natural and user-friendly phone experience.Would anyone else find this useful?

Test Environment:OS: Windows 11 25H2 (OS Build 26200.6584)Browser: Edge (Version150.0.4078.42)URL: https://www.intercom.com/helpdesk User Impact:Keyboard-only users will face difficulty navigating the chat popup screen, leading to confusion and inefficiency. This can prevent them from accessing critical controls, impacting usability and accessibility compliance. Repro Steps:Open the URL:  https://www.intercom.com/help/en/articles/9639255-getting-started-with-intercom in edge browser in windows. Landing page will open. Press tab key to navigate to the chat button and activate it. Verify whether keyboard focus order is incorrect in the chat popup screen in windows or not. Actual Result:Keyboard focus order is incorrect in the chat popup screen in windows. After activating the chat control focus is moving to edit field instead of first interactive element i.e. back control. Refer Attachment:Keyboard focus order is incorrect in the chat popup screen in windows.png Keyboard focus order is i

Hi intercom,In order to integrate with other chat service.We're evaluating the possibility of replacing the Messenger widget with our own chat UI, backed by the conversation API / or intercom-node. I found this post before: You will need to handle apps inserted into the messenger and conversations. You will miss out on a lot of the features offered by Operator. May I know what exactly will miss / break if connecting via API ?this is what i found so far: 1. Canvas Kit apps in conversations2. Fin replies: does Fin's answer arrive as a normal `comment` part (plain text/HTML we can render) ?3. Read/seen stateAnything else that silently breaks in a custom UI when Operator/Workflows run ?Or is there a guidance in document regarding this approach?Thanks

With Fin for Sales, we aren't using the meeting booker integrations for qualified sales meetings. Instead, we route prospects with the gCal app to schedule meetings with sales reps based on territory. One limitation we've encountered is that we haven't been able to set the meeting owner to a field that syncs with the Salesforce record owner. How can this be made possible?

Can Fin read customer order forms sent by email as PDF attachments, including ones with complex or multi-column layouts, and convert the data into a standard JSON format? If not, can we use a workflow or integration in Fin to reliably process these documents and ensure the final output is in JSON format?

We have some team members that are not on Intercom all the time. However, some message do need their input. It would be great to be able to slack teammate when they are mentioned @____ in the notes.And also, when the chat is assigned to the person.

Hi everyone, I am trying to build a pre-purchase flow using Intercom's Custom Bots to reduce product returns on our e-commerce store.For some of our highly technical gear, like these Forclaz trekking gloves, customers frequently struggle to pick the right size based on hand measurements, which leads to high support ticket volumes.I want the Custom Bot to trigger on this specific page path, ask the customer to measure their hand, and then provide a direct size suggestion (S, M, L) based on their answer.What is the best way to set up this conditional logic inside the bot builder? Do I need to create custom user attributes for "hand_size", or can I handle this entirely with path branches based on temporary button responses? Any examples of similar setups would be amazing!

Hi everyone, I'm working on setting up Intercom Product Tours on our outdoor e-commerce site, and I’ve run into a bit of a logic issue.We want to show a highly specific sizing and care guide tour only when a user lands on our high-performance technical product pages—for example, on pages like this forclaz jackets. Because these items require precise fitting instructions, a generic onboarding tour doesn't work.

DISREGARD - MEANT TO SUBMIT THIS AS A FEATURE REQUEST.

Looking to connect with experts / consultants to assist us in setting up our intercom instance.Contact me here or on LinkedIn : https://www.linkedin.com/in/balthazar-villey-desmeserets/ Thx

Hello everyone,I am facing an issue with Intercom Push Notification when it is a cold start (App is terminated, you receive a Push Notification and this notification will wake the App). While testing on Simulator that, if i am running my app from Xcode, terminate the App (on Simulator, not on Xcode), send a message to my test user, wait the push notification, receive it, tap on it but when i tap on it, Intercom Messenger does not opens the modal chat, it keeps me on my WorkListView (WorkList is a subview of RootView, that appears after SplashViews finish animation and transit to WorkListView).I have already made installation (API Key, API ID and Push Notifications are enabled on Settings > Channel > Messenger > Install > Install for Mobiles), Apple Developer is already configured, when i open the Messenger on my App, i can send and receive messages. When App is open but in background i am able to receive and wake the app in the correct modal Intercom window chat, but only t

Fin reads phone numbers too quickly Request: add a setting to slow down or format phone number delivery

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

Hi everyone,I’m running into a frustrating glitch with the email builder and could really use some help or workarounds.The Issue: Whenever I send a newsletter (even just a test email to myself), the template's background colour completely disappears. To make matters worse, the system seems to inject random blocks of alternative colours out of nowhere, which completely breaks and "crashes" the newsletter's layout.What I’ve already tried to fix it: Custom Templates: I built brand new custom templates from scratch to see if the original was corrupted. Inspecting Settings: I went through every single style setting to ensure nothing is left on "default" and everything has a specifically assigned colour. Despite all of this, the layout still breaks every time it hits the inbox.Has anyone else experienced this colour-stretching/disappearing bug recently? Is there a hidden setting or a specific CSS clash in the new editor causing this?Thanks in advance for any insights!

I am no longer able to highlight text to copy it. It unhighlights too quickly. I never had this problem before I started seeing little floating icons for Co Pilot next to everything I highlight. Now that it’s there, nothing stays highlighted long enough for me to even press control + c

We are seeing an issue with Intercom outbound welcome messages in our Flutter Android app where the same outbound message is rendered multiple times repeatedly in the conversation/preview screen.Instead of showing the welcome message once, Intercom displays the exact same content duplicated 2–3+ times in the same thread/UI.Note:Issue comes in Android version 14 and 15. No issue in Android 16.  

The nutraceutical industry continues to experience rapid growth as consumers seek products that support immunity, digestive health, cognitive wellness, sports nutrition, and overall well-being. As demand for innovative formulations increases, manufacturers, ingredient suppliers, and product developers must navigate a growing ecosystem of ingredients, suppliers, certifications, and market trends.Relying on fragmented spreadsheets or outdated directories is no longer enough. Businesses need accurate, connected, and industry-specific information to make informed decisions quickly. This is where a functional ingredients database combined with a nutraceutical data platform becomes an invaluable resource.Together, these solutions provide businesses with the intelligence needed to streamline research, improve sourcing, accelerate innovation, and uncover new growth opportunities.The Growing Need for Reliable Ingredient DataDeveloping successful nutraceutical products requires more than identif

Our users are seeing blank screen on the app. And we are seeing it on multiple versions. We think it’s because of intercom. I reached out multiple times to human support but there is huge delay in response. Our users are unable to use the app - can you look into this? prioritize pls

After the recent update I cannot properly reply to customers on the iOS app. It goes to a new line randomly, then the text disappears. It’s unusuable.

We're trying to get Fin to behave differently depending on when the customer asks for a human. We've tested two separate guidance rules but it's not sticking. Anyone solved this?Here’s what we want to do:First message = "offer" escalationCustomer says "representative"? Fin should hit them with: “Would you like me to connect you with a human agent? Or if you tell me what you're looking for help with, I'd be happy to try assisting you first.”(Reason: Let Fin actually try to help before bouncing them out)Mid-conversation = "escalate immediately"Customer says "representative" after you've been chatting? Skip the offer—just connect them. No questions asked.(Reason: They're probably frustrated and have already interacted with Fin. Don't want to make them explain twice.) 

DescriptionOn Intercom iOS SDK 19.6.3, if a user opens a conversation and quickly swipes down twice (first to close chat → home, then immediately to dismiss messenger), the app freezes. The main screen is visible but unresponsive.Works fine: slow swipe, or tapping X.ReproIntercom.present() Open a conversation Fast swipe down (chat → home) Immediately swipe down again (home → dismiss)Expected: Messenger dismisses, app is interactive.Actual: App frozen. ICMWindow stays hidden: false, key: true. No IntercomWindowWillHide / DidHide notifications fire.LogsHealthy:WILL hide → DID hide → ICMWindow hidden: true, key: falseFrozen:(no WILL hide / DID hide)ICMWindow stuck: hidden: false, key: true, hasRoot: trueCauseConversation is pushed on ICMMessengerNavigationController, but dismissed via Intercom’s custom swipe-down pan. A second fast swipe-down starts the system sheet dismiss before the first transition finishes. Two overlapping interactive transitions wedge the window.We only call Intercom

Hello Intercom Community!We have been live with Fin for just over a year now. We began small with a subset of beta users, then went live with all users on our Cloud platform on January 1st 2026. While there are bumps and dissenters, overall the reception was positive and we saw steady growth/use AND witnessed a direct decline in the number of support cases, which is one of the primary goals.HOWEVER. We seemed to have plateaued and are now seeing a change in Customer behavior as users are actively avoiding Fin: while the number of daily chats remains about the same (as we are adding new users weekly), we have seen a steady increase in our support call and email volume over the last 2-3 months (see the below chart which clearly shows this shift in behavior; Fin is replacing the ‘In-app’ support channel, but notice how the Call and Email channels are now steadily increasing).Note: We currently have Fin setup to only act as a ‘first line of defense’ on questions, and he does NOT interact