Recently active topics

Hello,We’re experiencing an issue when using showNewMessage with a pre-populated message.After the page and the Intercom widget are initialized, we call showNewMessage. However, if the chat widget has been opened and then closed beforehand, the chat opens without the pre-populated message. In contrast, if the widget has not been opened prior to calling showNewMessage, the message is correctly pre-filled and everything works as expected. Could you please help investigate whether this is a known issue and if there is a recommended workaround or planned fix? Thank you for your support!

We utilise auto translate in workflows, and on welcome, we share a message and offer the visitor options to select based on why they contact us, these selections in turn determine the path of the flow that is followed.  The issue is, The welcome message itself is sent in the detected language (browser or location, however this is being picked up), but, the choices (buttons) are displayed in the workspace default language, which is English. This means that we are contacted from say a Spanish or German customer, we send a localised welcome message, and present the options in English, this makes no sense.  Other than setting up individual workflows per language, is there a way to resolve this, if not, I would suggest that the same logic is followed for button translation and those are sent in the same language as the welcome message at the very least.  From research, the button translation comes once the language attribute is “locked in” by FIN, but that doesn’t seem to make much sense to

It appears that the Apple icon on users’ messages has now been switched to a phone symbol; Android remains the same. Is this a glitch or a permanent change? Just checking, as the Apple symbol was helpful in quickly recognizing the OS of our users. 

Hi everyone,We’ve noticed some users reporting that parts of our in-app widgets stop responding after they add third-party tools to customize their experience. While discussing this with a teammate, we mentioned hub script as one example people often try when experimenting with UI behavior.Has anyone seen similar conflicts with Intercom widgets, chat triggers, or tracking after users add custom scripts? What’s the best way to isolate whether the issue is coming from Intercom or from external tools?

I noticed what looks like a type inconsistency between two related schemas in the REST API.On the Admin object (/admins/admin), the id field is defined as a string — and the example values in the docs reflect this (e.g. "493881", "1295").However, on the Contact object, the owner_id field — which the docs describe as "the id of an admin that has been assigned account ownership of the contact" — is defined as an integer.These two fields represent the same value (an admin's ID), but they're typed differently depending on which side of the relationship you're looking at. This creates a few practical problems:Strict-typed languages choke on this. If I model Admin.id as a string and Contact.owner_id as an integer (matching the docs), I can't do a straightforward equality check without casting one or the other. Search filter confusion. When using the Search Contacts endpoint and filtering by owner_id, should I be passing a string or an integer? The field type says integer, but the actual admi

Please make this possible.

It’s the second time I encounter the same pain-point at a company: keeping our help center’s articles accurate as our release cadence accelerates. Our doc is becaming outdated. We create new articles for new features, but we’re always lacking the resources to update existing content impacted by those changes. That’s problematic because our product is available on iOS, Android, and the web, with small but important differences across platforms. To make things even worse, we are based in the EU and support three languages. The discrepancies between these languages became substantial, leading to increased support tickets…

The intercom-android Github repo includesSamples on how to use the Intercom Android SDK Changelog JavadocsHowever, the Javadocs seem to be very old (last updated 6 years ago). Is there a way to find the javadocs for a specific version of the SDK?

It would be very helpful to be able to open a preview view of an article before pushing publish, just to be able to check formatting, spacing, etc.While I know the Intercom editor is set up to be WYSIWYG, it still is slightly different because you don’t have the interactive Table of Contents in the draft editor, the spacing is sometimes slightly different, and you can’t see how the breadcrumbs across the top will populate. Nor do you get a picture of what the final URL will be, which relates to this similar request: Draft View or Preview View of Help Articles.  

Hi Intercom Team 👋🇬🇧, ℹ️ Feature Request: ✨ AI-Powered Semantic Prioritization & Smart Sorting 🤯 The Problem: Chronological BottlenecksCurrently, conversation sorting is limited to chronological or rigid SLA-based metrics (e.g., "Last activity" or "Next SLA"). In a high-volume environment with 30-40 open chats, this "dumb" sorting treats a simple "Thank you" with the same urgency as a "System Down" emergency. Agents waste significant mental energy manually triaging lists to find critical issues, leading to burnout and delayed responses for high-value customers. ✍️ The Solution: Semantic AI SortingWe propose adding a ✨ AI Priority sorting option to the conversation management dropdown. This feature would utilize a "Middleware Triage" to analyze the intent and sentiment of every incoming message in real-time. 😇 Dynamic Triage: The AI automatically identifies and bubbles up frustrated users or high-intent leads (e.g., "Payment failed" vs. "Just checking in").✅ Seamless Integratio

I have installed the Salesforce AppI have all fields syncing between contacts, accounts etc.I have setup the “Maintain lead and account ownership” section and it maps all the right Salesforce users with Intercom users. But….The only field it will not update in intercom is the user/lead owner. This is the one field I need so new conversation are assigned to the correct person. Has anybody come up against this before?  

We have unique URLs for every page for a user. For example, User A home page URL is: toddleapp.com/platform/32476/unitPlansUser B home page URL is: toddleapp.com/platform/99172/unitPlans Will product tour work here?

I’m trying to setup an onboarding checklist in which multiple steps will launch product tours. I have the first step setup and functioning fine, but the subsequent steps/product tours I cannot seem to configure to launch when/where it is needed. Here’s the issue:Our customer’s URLs are : subdomain.domain.com …..When a customer creates their account and logs in for the first time, they are brought to their homepage. The checklist appears and the first item in the checklist launches a product tour on that page. There’s no dynamic aspect to that URL, so we can simply setup the “Use your tour everywhere” setting to use {subdomain}.domain.comThat tour has them create a case/project in their dashboard, which generates a new page/URL. The issue arises here, because that URL is different every time, for every user, however, the URL itself is not unique to a user, meaning any user in that dashboard (which there are typically multiple) can access that case/project/URL. The URL ends up being some

At present Fin has a wide gap between confirmed resolved conversations and assumed resolved conversations. Our Help Centre articles are updated, it’s usually regarding more complex or personalised queries. Whilst some of the assumed resolved conversations are resolved, a lot of them are not. Is there a way to add in another follow up from Fin to check the resolution state and thus giving the user more time to respond to these. Moving forward it could be helpful to have inactive conversations to be escalated to a teammate so that the 'Assumed resolution' conversations can be automated within a workflow. From what I’ve been looking into it seems that a workflow on a customer being unresponsive can only start after a teammate reply rather than from a bot reply. When trying to set this up as an Attribute to route assumed resolved conversations to a teammate Fin just seemed to pass conversations along without trying to resolve them first.Any advice here would be appreciated - thank you!

We use the “Other” guidance heavily for our platform and voice isn’t supported yet. Wondering how other people have worked around this? I tried to update our FAQs as much as possible but there has been issues in which our Fin voice keeps repeating the wrong thing that would have worked in chat or email because of Other guidances set in place. 

Hey all,Fin just let me know that data connector fields can’t really be used in a workflow- only through a procedure. I can run the data connector function through a workflow, but then I can’t actually access any of the fields that data connector found to further the conversation. The answer Fin gave me is that this can only be accessed via a procedure.Is this the case? If so, I don’t understand why this functionality would be locked behind Fin procedures- there’s nothing fancy going on with this API call that requires AI.   

Hi all! I’m Alex from Lighthouse. I work as a technical support specialist and use Intercom every day to interact with customers. I am one of our help center specialist and automation specialists, so I’m always looking at what new features are coming from Intercom. Excited to learn more and become an expert in all the features that Intercom has to offer! Outside of work, I am a big reader and writer, love to travel, and play board games. My corgi, Daisy, also keeps me busy!

We've been using Fin for about 6 months and genuinely love it — but the analytics drive me crazy.I can see our resolution rate is 71%. Great. But when my manager asks "why isn't it higher?" I have nothing. Which topics is Fin struggling with? Did that KB article I wrote last week actually help? No idea.We ended up exporting conversations manually and doing our own analysis in spreadsheets, which is... not ideal.How are other teams handling this? Are you just accepting the top-line number, or has anyone found a good way to actually dig into where Fin is failing?Would love to know if there's something I'm missing in the native reporting, or if everyone's just cobbling something together.

I’m using a Custom Action with some Datetime elements.Whenever I have empty element I send the response back to Intercom using something like this:"0000-00-00T00:00:00+04:00",When I test the Custom Action, the “Test response” brings back exactly this Datetime format, and it gives me a 200 OK.Same for “Data transformation” and “Object Mapping”, all OK.However, in production, we are getting several errors. The Intercom Logs of this Custom Action suggest the Mapping is not happening (when the request and response are 200 OK). The only different data I saw between a Log with a mapping and a Log without the mapping was an “empty” Datetime, like the one above. What’s the proper way of sending an Empty Datetime? 

One of the main problems we’ve found with our Intercom chatbot is that it waits for the user to ask a question first - its reactive and passive.  We all want to solve software adoption and bring each user to value instantly - we believe you can achieve this by feeding your Intercom real-time user events so it can guide each user proactively to value. Copilots today face the following problems:Users don’t know your software so they don’t know what to ask. Users don’t always seek help when they need help and stay in limbo. Because they don’t know your software they may prompt in the wrong way and steer the conversation in the wrong direction. Therefore we think that if the chatbot had an additional real-time data source of what the user is doing the above painpoints could be solved. We’re iterating on this SDK to make building a proactive Intercom plug and play with a couple lines of code. Let me know if you’ve faced similar problems and how you’re solving it! 

Hi, Presuming this is not possible but it doesn’t hurt to ask! We currently have 2 separate websites set up with the same messenger brand, same workflows etc. However, in the near future, we need to change the messenger brand on site A. Once this is done, it means any conversations started on the Site A messenger will not be visible if the customer clicks on to site B mid-converstion, and vice versa. Does anyone know of any way around this? We want the actual messenger experience to be seamless, it’s just the branding that needs to be different.

You can use AI tools like Claude or ChatGPT to: Repurpose internal content: Quickly convert internal documents and product updates into customer-friendly Help Center articles. Review and rewrite: Rephrase content to match customer language. Ensure proper formatting (headers, bullet points, etc.). Clarify ambiguous terms.  Using AI tools works really well if you create a style guide with the structure, formatting, tone of voice, and template you'd like AI to use when generating articles for your Help Center. Once you’ve got a style guide, try using it with these AI prompts:New content creation You are an expert technical writer. Goal: Transform the attached “[name of internal document]” into a polished, customer-friendly Help Center article that strictly follows the attached “[name of Style Guide]”. The finished piece must be easy for humans to read and for AI systems to parse and extract structured information. Use only facts present in the internal doc. Do not inve

We are sending messages using Intercom’s REST API and after completing a task on our platform side, we would like to inform the customer that:“The team will get back to you on this. Our usual reply time is 1 day. You'll get replies here and to email@example.com.” (sent from William’s Admin ID)However, this causes an unintended side-effect with our auto-assignment rules:Because Intercom treats this as a teammate reply, when the auto-assignment occurs (balanced assignment). We auto-assign conversations based on “waiting longest”, so this causes these conversations to be de-prioritised and skipped, and they will only be picked up again if the customer replies.As a workaround, we currently: Do not send a message to the customer, and instead Use the API to unassign the conversation and move it into a manually monitored inbox where it auto-assigned and picked up. This avoids breaking the assignment logic, but it leaves the customer confused because they receive no acknowledgement that we a