Answered

When I try to select the color picker, it doesn’t appear. It was working since a week or two ago. Also, sometimes the column doesn’t adjust properly after I delete one. In this example, it should adjust to be the whole page wide. 

My teammates reported an issue with a Fin response that stemmed from a Guidance prompt that was never enabled. I spent lots of time testing our active prompts before opening the prompt that isn’t enabled. That prompt is where Fin was pulling from; I had to delete the prompt entirely so Fin wouldn’t use it. How can I ensure that draft prompts are not being used in the background? 

When we get new customers, a user profile is created with their email address and phone number included. However, it does not identify the existing profile whenever they finally use the messenger. We have enabled the workflow to search by email address, but it’s creating a new lead profile for each conversation. How can we stop the creation of duplicate profiles going forward?How can we force merge the existing duplicate profiles so their conversation history isn’t lost?

We utilize Fin as the first line of defense in supporting our software. I’d like to explore having Fin handle chats related to known bugs/issues. Right now, a user will message saying “I’m experiencing XYZ issue” and Fin will go through the normal troubleshooting steps. Ultimately these chats often get routed to a human agent who then lets the user know we are aware of the issue and working on a resolution. Users are often annoyed that they had to go through the process of explaining the issue to Fin just to find out we knew there was an issue. Sometimes these issues only impact a small subject of our user base so we don’t want to widely exclaim that there is an issue. Thoughts/Questions:Best way to implement something like this - I’m curious if we can utilize the Content and Sources (beta) section under Guidance? Best way to track these conversations - we track these reports so we can reach back out to the user once the issue is resolved. Ideally, these conversations would be assigned

Hello, I am trying to integrate a third-party app into our workspace, and the oauth screen displays the following:  I have full admin on the workspace - and ive tried signing in and out again.

Hi Intercom Support, I'm building a Slack bot to pull metrics from Intercom. I need to access the Fin AI Resolution Rate and conversation stats that appear in the Reports dashboard. Questions:1. Is there an API endpoint that provides the same metrics shown in Reports (AI resolution rate, conversation counts)?2. How can I identify which conversations were resolved by Fin AI via the API?3. Should I use the Data Export API or Conversations Search API for accurate reporting data? Current Issue:Metrics I calculate from the Conversations API don't match the dashboard. For example, my calculation shows 84% AI resolution but the dashboard shows 62%. (same issue happens with other stats as well) What do you think the best way is to programmatically access these report metrics? Thanks(The goal is to build an AI agent—a Slack bot app that connects with Intercom. When I ask in Slack, it responds correctly with proper reporting and provides AI insights - Reporting SHOULD BE ACCURATE.)

Hi,As part of our integration into intercom - we would like to know when a contact gets blocked so we can start ignoring that contact for tasks like updating user attributes etc when they change on our side.I had a look at the available webhooks, but it wasn’t obvious which (if any) webhooks would fire when a contact was blocked and which field would let us know that they were blocked.Is there any webhook that would assist us with this?

Hey Team! I am wondering if there is any way how I can do some auto-notification when SLA is breached? 

We have recently moved from a different ticketing system to Intercom.One of the features we miss the most of the old system is notifications on conversations that are ABOUT TO breach their SLA. This would serve as a reminder for any conversation that was in the queue and give us a chance to respond before it was officially out of compliance.As another submission posted, we bounce between applications all day long and it’s easy to miss a conversation on the verge of breaching SLA.

Hello Intercom Community,I'm encountering a persistent issue with retrieving and listening for unread conversation counts in my React Native application using the Intercom SDK. Neither Intercom.getUnreadConversationCount() nor the IntercomUnreadConversationCountDidChangeNotification event listener seems to be working as expected.Goal: My objective is to display the current unread message count from Intercom within my app's UI (outside of the Intercom messenger itself).Expected Behavior: When new messages arrive in Intercom conversations, the IntercomUnreadConversationCountDidChangeNotification listener should fire with the updated count. Intercom.getUnreadConversationCount() should return the correct number of unread conversations at the time of the call. Actual Behavior: Intercom.getUnreadConversationCount() consistently returns 0 (or null/undefined, please specify) even when there are clearly unread messages visible when I manually open the Intercom messenger. The Intercom.addEve

We’re presenting Intercom articles with Intercom.presentContent(content) . Everything was working well in version 8.8.0 but after bumping to 9.x, the close button at the top article header is broken in iOS and doesn’t respond to taps. The only way to close the article is to drag the overlay down (which is something that might not be obvious for every user). It is working correctly on Android.

Our product uses NextJS 13.4.9 and we are trying to integrate intercom messenger. In our _app.js we are using the useEffect below to check if the user is logged in or not (guest). What’s happening is that when he is a guest everything works well. When he logs in and opens the launcher for the first time it shows the message “Something’s gone wrong”. After a refresh everything works. We have seen other related topics and they don’t work in our case. We have also used shutdown in login/logout and nothing works. Something worth mentioning is that after the login when the user clicks the launcher the Intercom’s localStorage is cleared and the intercom-session-[id] cookie as well. After a refresh all works well. Now we don’t know if this is the cause. import { Intercom, shutdown } from '@intercom/messenger-js-sdk'; useEffect(() => {  if (process.env.hasIntercomMessenger && process.env.intercomMessengerAppId) {    if (user?.customerServiceIntegratorId) {      // for logged in user

There is a bug in Intercom's contact field timestamp display. After a day, the timestamp field switches to a "relative" format (e.g., '3 days ago'). When attempting to view or extract the absolute date after this period, some fields revert to displaying the Unix Epoch—January 1, 1970—instead of the correct timestamp  

Hello,I’ve been planning to make a customer portal and wanted to make it a PWA. I would like to be able to use Intercom push notifications on the PWA but from all the documentation I can find it seems like push notifications are only possible using the mobile SDK.I was wondering if there is a way to have push notifications without using the mobile SDK.

Are chat messages/Posts sent by email automatically or do you need to also create an email with that same information?

Hey friends, unsurprisingly enough - after reaching out to our clients for some feedback, Fin is their favorite education tool that we have - which we love! That being said, I’m trying to get MORE source documentation into Fin to reference and suggest - specifically, our University Courses (hosted in Northpass/Gainsight) - what’s the best way to go about this, so that it indexes correctly and really does become more helpful!? 

Hi, I’ve been having a helluva time trying to get JWT verification working with `@intercom/intercom-react-native`.For context, we have JWT working with our website, and the API secret is enabled for all platforms. We’re reusing the same endpoint we use for web to get the JWT for mobile.Our mobile app is built with:expo: @53.0.23 @intercom/intercom-react-native: 9.1.2 react-native: 0.79.5I have been testing the app in development mode, with `expo run:ios`.So far, I’ve been able to get Intercom working if JWT is not enforced. But once I activate “Enforce Messenger Security” in the Security Settings, Intercom views start returning “Something’s gone wrong” with a reload button. Here’s our JWT code:// Verified that `intercomToken` is valid, in Intercom’s online JWT decoder// // Token payload looks like:// {// "user_id": 3, // << Does this need to be a string?// "email": "person@place.com",// "name": "John Smith",// "exp": 1759892398// }await Intercom.setUserJwt(intercomToken

We use Fin AI to handle conversations. What we want to do is when Fin AI routes to a human, it gets put in the unassigned conversations bucket and we want to get notified when that happens. Is there anything specific we can use?I did notice intercom has desktop notifications, but that really depends on our user’s alert settings as well. We originally used a workflow to message a slack channel for all new conversations and replies. However I can’t find any webhooks that trigger when a conversation is moved into unsassigned. 

We’re using the Javascript API client to create a conversation programmatically when users sign up to our app.We’d like all messages of the conversation to each go through SMS. Is that possible, provided that the SMS channel is set up correctly in Intercom?I’m not seeing any way to specify a channel in the `intercom.conversations.create` method, or even in `intercom.messages.create`.Is this a dead end?Thanks!

Hello support!When fetching a conversation using GET conversations/{id} or POST /conversations/search, the statistics fields are all null. I’m using version 2.10 but tried with 2.14 as well and it doesn’t work either. This is the object I receive  "statistics": {      "type": "conversation_statistics",      "time_to_assignment": null,      "time_to_admin_reply": null,      "time_to_first_close": null,      "time_to_last_close": null,      "median_time_to_reply": null,      "first_contact_reply_at": null,      "first_assignment_at": null,      "first_admin_reply_at": null,      "first_close_at": null,      "last_assignment_at": null,      "last_assignment_admin_reply_at": null,      "last_contact_reply_at": null,      "last_admin_reply_at": null,      "last_close_at": null,      "last_closed_by_id": null,      "count_reopens": 0,      "count_assignments": 0,      "count_conversation_parts": 7    }  My close is to know when was last time a conversation was closed and intended to use stat

SDK version 19.2.0 has broken the close button on our carousels, and it's still broken on 19.2.1It would be good if we could update our SDK version for Intercom because Intercom have also fixed UI issues on iOS 26 (new iOS version) :(

There are multiple ways of sending a ticket form to a conversation as described here:https://www.intercom.com/help/en/articles/8300310-ticket-form-optionsIs there a way to send a ticket form to a conversation through the REST API?TIA

Looking at the implementation of intercom for IOS, the creator seems to leave the API key in the front end. Does this mean that this API key is fine if exposed to the end user? I don’t seem to see another way to obscure it, as keeping the key on the backend doesn’t seem like an option if I want to use intercom’s package.import Intercomlet INTERCOM_APP_ID = "<#YOUR APP ID#>"let INTERCOM_API_KEY = "<#YOUR API KEY#>"class SceneDelegate: UIResponder, UIWindowSceneDelegate { 

Hi everyone,I’m Hamza. I’ve been in B2B SaaS frontline support for 4 years, mostly on Intercom. I’m a big fan of Fin AI and want to learn how different teams are setting it up and putting it to use.I’m also open to L1 customer support specialist roles, so if your team is hiring I’d be glad to connect.—Hamza

I’m returning to Intercom after a long break, and I could use some advice from folks who’ve set up recent workflows.It looks like every customer interaction starts as a Conversation. And if it takes longer to resolve or needs extra structure, it can be turned into a Ticket. That all makes sense.But I’m trying to set things up in a way that keeps reporting clean and consistent.My goals:I want to capture the same core metadata for every interaction (things like feature area, source, etc.) I don’t want to double-count anything when pulling metrics I want to avoid having agents fill in fields twice, or inconsistently across conversations and ticketsMy questions:Do you only use tickets for escalations, or convert everything? Can you safely report on Conversations only, and still get reliable counts and resolution metrics? Are you adding custom fields to Conversations for universal stuff, and using ticket-only fields for more complex cases?Trying to figure out how to avoid having my metrics