How Nuuly turned AI savings into higher pay for its support team
-
Recently active
When a user replies to an email notification from Intercom Messenger, the email is duplicated. Has anyone found the cause and a solution to this issue?
Hi everyone,I’ve been sending newsletters and promotional emails for my small business, but a significant number of them are ending up in recipients’ spam folders.I’m trying to improve engagement, but low deliverability is holding me back. I’ve heard about authentication protocols like SPF, DKIM, and DMARC, but I’m not sure how to implement them correctly.Can anyone share practical tips or strategies for maintaining a clean email list, avoiding spam triggers, and improving sender reputation?I’d love guidance on how to increase email deliverability effectively without overcomplicating things.
I'm seding custom attributes using the update function from react-use-intercomBut I'm having problems using those custom attributes in the text and messages on the intercom painel After reseach a lot, I found those 3 options, but I couldn't find any oficial documentation about it// {{custom_token}}// {{prop.custom_token}}// {{custom_attributes.custom_token}}could someone confirm to me, how is the correct syntax is to use the custom attributes as placeholders in my texts
Hello everyone, our app (Coview) implemented the health check. Based on the following description from the documentation, we assumed that we would receive at least one call for each of the installations of our app each day: This will happen at least once a day for each workspace where the app is installed. With this information, we expect you to discover if the app is in a healthy state for this workspace and respond to the request telling us whether it's healthy, unhealthy, or you don't currently know.However, according to our logs we just a handful of checks each day although we have a few hundred installations. Do we misunderstand something here?
Hi everyone,I'm seeking advice on effectively managing our company's online reputation using Intercom. Specifically, how can we leverage Intercom's features to monitor customer feedback, address concerns promptly, and build trust with our audience?For more insights on this, you might want to check out Reputation Prime. Are there any tools or integrations within Intercom that can assist in this process? Additionally, how can we ensure our team maintains a consistent and positive tone when responding to customer inquiries?Any insights or experiences would be greatly appreciated.Looking forward to your suggestions!
I’m curious if there is a known issue with the Users Scroll API? The Company one works just fine, but the users one returns that it is not a valid resource.I found a github incident from 2018 where something similar happened and I’m wondering if something similar is at play again. I notice that the users scroll documentation page doesn’t have a Try It option like Companies does, which leads me to believe it may be a known issue that the endpoint doesn’t actually work.Current Documentation: https://developers.intercom.com/docs/references/1.3/rest-api/users/iterating-over-all-users
Hi there,we’ve recently added events tracking and it was noticed that we get ad hock "User Not Found" error however user exists years. Request we send:{ "event_name": "post_autopublished", "created_at": 1731959712, "user_id": "..."} Response we received:{ "type": "error.list", "request_id": "0045a0lc51qku6vpphg0", "errors": [ { "code": "not_found", "message": "User Not Found" } ]} Retrying the API call can work but would be great to know what causes the issue. Any help would be appriciated. Best,Antal
It seems that in v2 when the User and Lead models have been merged into Contacts, the session_count attribute has been removed from the response. The Company object displays the session_count information so I'm wondering if there's a specific reason why the user session_count has been removed or if it's just a slip?
I’m getting “Something went wrong loading this message” error. And I see below JavascriptError.vendors~sentry~app.47087327.js:1 DOMException: Failed to execute 'setAttribute' on 'Element': 'data-といったエラーが発生する。' is not a valid attribute name. at g (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:368553) at Qs (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:451809) at Sc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:474108) at xc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:473848) at bc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:473715) at gc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:473578) at uc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:470413) at fc (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:470795) at Vo (https://js.intercomcdn.com/vendor.b8d3fa93.js:2:411940) at https://js.intercomcdn.com/vendor.b8d3fa93.js:2:468368
The Contacts model have an attribute called language_override, but when I try to set it when creating a new Contact, or to update it on an existing Contact the attribute seems to be ignored. Docs also doesn't mention it for those operations, so I guess that is as-designed. Is there any way I can change it?
Hello Intercom Team,We are using @intercom/intercom-react-native for in-app support, which is a core feature of our app. Users often need to attach screenshots when contacting support.According to the official documentation, the SDK requires storage permission. On Android 13+, this maps to READ_MEDIA_IMAGES.However, Google Play has rejected our app, even after appeal, because this permission is considered sensitive. They are asking us to justify its usage, and one-time photo pickers are not accepted since the Intercom SDK manages its own gallery internally.This is now blocking our app release. We saw intercom-android PR #587 regarding Android 13 media permissions. Can you please confirm if this is the only way for the SDK to work, or if you plan to move towards the system photo picker (which Play Store prefers)? Is there an official statement from Intercom that we can submit to Google to justify this permission? This is a critical blocker — without this permission, our users cannot
I’m fetching articles from Intercom using the API. In the case where multiple help centers are present, how do I fetch the articles from only a specific help center and not all articles? Alternatively, I am also open to fetching all articles but filtering them on the basis of help center. How can I do this using the API?
This was reported 4 years ago in another post here:and supposed to have been fixed in Intercom’s iOS SDK 17.0.4:but unfortunately we’re seeing it again. This started happening after we turned on push notification integration for our app, and seems related to calling Intercom.setDeviceToken when iOS gives us an APNS token.In case it’s relevant, we have IntercomAutoIntegratePushNotifications turned off because it caused problems with Firebase Cloud Messaging’s similiar swizzling.
I’m trying to create a Zapier integration that syncs Intercom conversations to ClickUp tasks. We have the Intercom ClickUp integration set up such that we can link conversations to tasks just fine. The problem is that the Intercom API does not expose the ClickUp task ID or any other identifiers that could allow Zapier to see that Interom → ClickUp link.Is there a workaround for this, and if not, is it possible for the API to be extended to provide access to the third-party integration’s conversation attributes?
I’m Prakash Hinduja, a financial strategist, born in Amritsar, India, and now reside in Geneva, Switzerland (Swiss), where I continue to pursue innovative financial solutions.I’m starting to explore apps and integrations within Intercom, and I’d love to hear how you’re using them in your setup. Which integrations have been the most helpful for you, and do you have any tips or recommendations to get the most out of them?RegardsPrakash Hinduja Geneva, Switzerland (Swiss)
Hi, We have been using Intercom without any issue. But recently we have started getting following error after the user has logged into our platform. Access to XMLHttpRequest at ‘https://api-iam.intercom.io/messenger/web/embedded/content’ from origin ‘https://portal.product.com’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. When the page is refreshed, the error disappears and status code changes to 200 OK but the user data is not updated in Intercom.What’s the possible solution to this issue?
My Flutter application has reported a crash in the Google Play Console. The crash is a java.lang.RuntimeException with an underlying ClassNotFoundException, specifically because the Android runtime is unable to find the io.maido.intercom.PushInterceptReceiver class.Crash Stack Trace (Core):Fatal Exception: java.lang.RuntimeException: Unable to instantiate receiver io.maido.intercom.PushInterceptReceiver: java.lang.ClassNotFoundException: Didn't find class "io.maido.intercom.PushInterceptReceiver" on path: DexPathList[...]My Project Configuration: Intercom Plugin Version: intercom-android: 17.0.2 ProGuard/R8 Rules: I have already added a keep rule for the Intercom SDK in my proguard-rules.pro file: -keep class io.intercom.android.** { *; }-keep class com.intercom.** { *; } Troubleshooting Steps Taken: I've checked my AndroidManifest.xml and there is no manual declaration for PushInterceptReceiver, which I believe is automatically merged by the intercom_flutter plugin. Since the cr
Hi team,I'm using @intercom/intercom-react-native with Expo bare workflow and the plugin is generating hardcoded API keys in my AppDelegate.swift Is there a proper way to configure the plugin to use environment variables at runtime rather than hardcoding them during build? I want to avoid committing secrets to my repository.Thanks!
Hi everyone,As our team increasingly relies on mobile agents, I'm seeking advice on effectively managing a mobile workforce using Intercom. What strategies have you implemented to ensure seamless communication, task management, and performance tracking for mobile agents?Are there specific features or integrations within Intercom that have proven beneficial for mobile workforce management? Additionally, how do you handle challenges such as varying time zones and connectivity issues?Any insights or best practices would be greatly appreciated.
Despite the fact that mobile SDK does not support dark mode, the articles and some parts of the help center use dark mode features. SDK Android 16.3.0 (changelog) iOS 18.8.0 (changelog)
Hi there I am hoping to create some dashboards based off of our product’s intercom data that surfaces insights about # of tickets created and average conversation rating. High level mockup of the dashboard: Diving into the intercom API, it looks like the only way to get aggregate data is by calling the search APIs and checking the total_count property. This is un-ideal in the case of average satisfaction score where I would need to query 5 times for each satisfaction score value per data bucket. If I have a time series with 12 month buckets, that would mean I would have to query Intercom 70 times per dashboard render. Is there a better alternative to accomplish this? I saw reference of a reporting feature coming to the API at some point: Also, what is intercom’s data retention policy? Can I expect to be able to retrieve all of our intercom data or is there a cut-off?
Hi Intercom team,I’m working on a web app that’s embedded in a partner’s mobile app via WebView. Both our web app and the partner’s mobile app use Intercom, but each with a separate workspace.Are there any known issues or best practices when two Intercom instances (in different workspaces) are running in this setup? Specifically: Could this cause conflicts with sessions or the Messenger widget? Does Intercom handle isolation properly in WebViews? Is there anything we should do to avoid interference between the two instances?
Fatal Exception: java.lang.IllegalArgumentException: Missing keys: [timestamp] in '{teammate} moved ticket into {status} {timestamp}' at io.intercom.android.sdk.utilities.Phrase.format(Phrase.java:189) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.TicketInAppNotificationContent(InAppNotificationCard.kt:180) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.InAppNotificationCard(InAppNotificationCard.kt:124) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:75) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:74) at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:109) at androidx.compose.runtime.internal.ComposableLambdaImpl.invoke(ComposableLambda.jvm.kt:35) at androidx.compose.runtime.Composit
I'm trying to install the iOS SDK and have been following the provided guide. However, when I click the "Check Installation" button at the end, it doesn't seem to register as installed. I'm currently using Xcode 16.4 with an iOS 18.5 simulator.I noticed that the SDK's README mentions Xcode 15 as a requirement. Is this version required only for installation, or is it also necessary for Intercom to function correctly? Additionally, will support for Xcode 16 be available soon?This could be a blocker for us, as Xcode 15 isn't compatible with macOS Sequoia 15.5.
Having the ability to trigger a reusable workflow via API would be really helpful for making workflow/bot conversations more dynamic. A specific use case I’m working on right now is serving CSAT in conversations where customers interact only with a bot (no team member assigned). Unresponsive triggers only happen with human to human conversations. If a customer goes unresponsive while talking to the bot, the conversation is considered abandoned, not closed. My thought was to use Zapier to trigger closed conversations and filter by convos NOT assigned to a team member, however I have no way of serving CSAT in that conversation via the API. I played around with starting workflows using this non-documented endpoint:curl --request POST \ --url https://app.intercom.io/ember/inbox/workflows/start \ --header 'Accept: application/json' \ --header 'Authorization: Bearer REDACTED \ --header 'Content-Type: application/json' \ --header 'X-Csrf-Token: REDACTED' \ --cookie _intercom_session=RE
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.