Popular Topics

Intercom is telling us that they dont support a sync using salesforce’s default record ID! How does everyone else work around this severe limitation? I cant imagine changing our business processes and adding a new unique field just to get data synced. Adding a new unique field is not a big thing but we would have to change our sales processes to now update a field upon account creation :( 

Hi,We are currently facing a significant issue related to time zone discrepancies that is affecting customer access to our contact center services.Our contact center is based in Melbourne, with operational hours set from 9:00 AM to 7:00 PM local Melbourne time. However, due to the diverse time zones across Australia, customers from different regions, such as Perth, are encountering difficulties reaching us at suitable times. The time difference between Melbourne and Perth is approximately 2 hours.To enhance customer experience, we urgently need a solution for dynamically routing customer interactions based on their local time and our operational hours. This issue significantly affects our ability to deliver efficient customer service to clients across Australia.Your assistance in addressing this matter promptly is greatly appreciated.

I need to setup the Intercom webhook to an external endpoint. But the external endpoint needs an authorization header. I could not find the HTTP header fields in Intercom's webhook configuration. ​https://www.rfc-editor.org/rfc/rfc6750#section-5 "Don't pass bearer tokens in page URLs: Bearer tokens SHOULD NOT be passed in page URLs (for example, as query string parameters). Instead, bearer tokens SHOULD be passed in HTTP message headers or message bodies for which confidentiality measures are taken. Browsers, web servers, and other software may not adequately secure URLs in the browser history, web server logs, and other data structures. If bearer tokens are passed in page URLs, attackers might be able to steal them from the history data, logs, or other unsecured locations."

I have custom action to open a case in salesforce. when I’m testing it in setup it works properly, when I’m sending the same values in postman it works properly. but in live chat I’m getting” Error occurred validating request values” Endpoint: https://mydomain.my.salesforce.com/services/data/v57.0/sobjects/Case/Any ideas? 

Hello!I hide my Intercom widget on some pages of the app using Intercom('update', {hide_default_launcher: true});.The problem is that the user still hears messages sound even when the chat is hidden.Is there any way to mute the chat?Or any other methods to hide chat completely, including the sound? 

Hi, I’m trying to use a snippet code i got from your developer party, to search conversations between two epochs. The codes runs without a problem on your platform, but when I use it in google scripts I get the response:{"code":"invalid_query","message":"Query body must contain a query hash"} I guess it is related to the JSON payload, though the string seems to be ok.I was able to work with the API without any problem, when I don’t send a body, but I always get the error whenever I include a body.Any clue?  const str = JSON.stringify({ query: { value: [ {field: 'created_at', operator: '>', value: '1690081199'}, {field: 'created_at', operator: '<', value: '1690167601'} ], operator: 'AND' } }); const options = { method: 'POST', headers: { accept: 'application/json', 'content-type': 'application/json', authorization: 'Bearer XXXXXXXXXXXXXXXXXXXXXX' }, body: str }; const response = UrlFetchApp.fetch('ht

Hey, I'm getting the following build error trying to integrate the React Native SDK with iOS builds. Android build works fine. I have tried the both ways (Automatic & Manual) of installation the sdk.Intercom package version : 5.2.0X-Code - 14.2React-Native Version: 0.66.4Node : 14.17.0

After upgrading from an older Intercom React Native version to the latest version (see details below) we’re no longer able to use the Intercom.displayMessenger() API to open the message composer with the logic mentioned in the docs here, which says:Then we’ll ensure the Messenger opens in the best place for each user.For example:If a user has one unread conversation, we open that conversation. If a user has no conversations, we open the composer. If a user has more than one unread conversation, we open the conversations list. If a user has no unread conversations, we open the last screen they were on when they closed it.The docs still mention the Intercom.displayMessenger() API, but according to comments in the code it’s deprecated and will be removed in the future. Currently calling the function seems to simply do the same as the Intercom.present() API. Our customer support team really likes the old Intercom.displayMessenger() UX and messenger display logic and would prefer to keep it

Hi, am currently struggling to add the Octopods Omnichannel app  to our test environment. We worked on prod up to the go live and now we set up the test environment but a few other apps also do not have the install now button in the app store. can anyone tell me why or how to install them?

We’re trying out the canvas app. When we pass the header and text components, the Canvas is loading correctly in the Inbox.This is the request body: {    "canvas": {        "content": {            "components": [{                "type": "text",                "text": "Create Case in SF",                "style": "header",                "label": "sf create case",                "align": "center"            }, {                "type": "text",                "text": "his is a text component."            }]        }    }}But, when we try to add a button as well, along with the text components, it is showing an error.{    "canvas": {        "content": {            "components": [{                "type": "text",                "text": "Create Case in SF",                "style": "header",                "label": "sf create case",                "align": "center"            }, {                "type": "text",                "text": "his is a text component."            }, {                "ty

We use @capacitor/intercom plugin to use Intercom in Ionic app. According to logs device token is passed inside the plugin. And user is registered in Intercom. But without device token. So it is unable to send push notification to it

I want to reply message from instagram, do i need to buy a PRO or a Starter? 

Hi Intercom:When using Intercom, some users have provided feedback that they are unable to send pictures on the Android system. when trying to send pictures, it prompts an error: unable to send.However, we can still receive text messages.we use @intercom/intercom-react-native, here is the dependencies:{ "react-native": "0.64.4", "@intercom/intercom-react-native": "3.0.0", "expo": "^44.0.4"}android/build.gradle information:buildscript { ext { buildToolsVersion = "30.0.3" minSdkVersion = 24 compileSdkVersion = 32 targetSdkVersion = 31 multiDexEnabled = true readerSdkVersion = "1.5.6" }}here is the information collected from users.Android Device: SM-A426UAndroid OS version: 13Could you please take a look, Thanks in advance!

Getting reports of crashes. It’s pretty explicit, the SDK tries to launch an app to handle `mailto` but none are found on the device.Intercom Android SDK version: `15.0.0`android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.VIEW dat=mailto:xxxxxxx@xxxx.xxx } at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1945) at android.app.Instrumentation.execStartActivity(Instrumentation.java:1620) at android.app.Activity.startActivityForResult(Activity.java:4541) at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:754) at android.app.Activity.startActivityForResult(Activity.java:4499) at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:735) at android.app.Activity.startActivity(Activity.java:4860) at android.app.Activity.startActivity(Activity.java:4828) at io.intercom.android.sdk.articles.ArticleWebViewClient.shouldOverrideU

Curious if anyone’s done it. thx.

Using React Native SDK, I see this error each time I open the app. Here is my codeIntercom.loginUserWithUserAttributes({ userId: `${authData.id}` }).then(() => { this.updateUser(authData, onUpdate)}) Even when I wrap this inside logout then callback, I get the same error.Intercom.logout().then(() => {  Intercom.loginUserWithUserAttributes({ userId: `${authData.id}` }).then(() => {    this.updateUser(authData, onUpdate)  })})Note: This happens only on Android. 

Getting more and more timing out or internal server errors. Anyone else has the same issue?

We're getting an error in our Android app when we attempt to call loginIdentifiedUser() The code is very simple and we can't work out why we're seeing this error. Here's the logs from logcat: D/IntercomAPI: login identified.. I/Intercom: Dispatched Action: SOFT_RESET: No Value I/Intercom: Successfully reset the user. To resume communicating with Intercom, you can register a user I/Intercom: Dispatched Action: HARD_RESET: No Value I/Intercom: We already have a registered user. Updating this user with the attributes provided. E/Intercom: Failed to register or update user: A network request was made with no user registered on this device.Please call registerUnidentifiedUser() or registerIdentifiedUser(Registration). D/IntercomAPI: login identified failed: 1001 : ERROR - [HTTP -1] - Something went wrongThe log seems to be stating that the network call to loginIdentifiedUser is failing because we haven't logged in. That doesn't really make sense. Here's the code

Greetings.With the update to the latest version of Intercom 15.1.4 and addition of “Inline reply and smart suggestions to chat notification” feature, while testing this functionality on Galaxy A51/Android 13 it caused this to happen:java.lang.IllegalArgumentException: Shortcut must have a non-empty label18:02:43.782 System.err W at androidx.core.content.pm.w$b.a(ShortcutInfoCompat.java:249)18:02:43.782 System.err W at io.intercom.android.sdk.m5.push.ui.ConversationShortcutKt.createTemporaryShortcut(ConversationShortcut.kt:178)18:02:43.782 System.err W at io.intercom.android.sdk.m5.push.IntercomNotificationHandler$processConversationPushNotification$1.invoke(IntercomNotificationHandler.kt:10)18:02:43.782 System.err W at io.intercom.android.sdk.m5.push.IntercomNotificationHandler$processConversationPushNotification$1.invoke(IntercomNotificationHandler.kt:1)18:02:43.782 System.err W at io.intercom.android.sdk.

Hi everyone, I have recently setup a new workspace in intercom. I have added slack as an app to this new workspace. But I am getting an error saying that I have already conencted this workspace to the slack environment.That's because my other workspace is linked to the same slack workspace. Is there any way I can have the new intercom workspace linked to the same slack workspace? I could really use the help! Thanks a lot :)

Hi!  I have a question about which to rely on in the API v2.9 Models documentation: the example JSON object, or the documented fields / field datatypes.  In some cases the inconsistencies can be significant.  For example, in looking at https://developers.intercom.com/intercom-api-reference/reference/the-contact-model I can see the following differences:Documentation does not include the external_id field from the example JSON. Documentation lists avatar as having type object but in the example object it has type string. Documentation does not include the opted_out_subscription_types field from the example JSON. Documentation does not include the opted_in_subscription_types field from the example JSON. Documentation does not include the utm_campaign field from the example JSON. Documentation does not include the utm_content field from the example JSON. Documentation does not include the utm_medium field from the example JSON. Documentation does not include the utm_source field from the

Hey! I try to build an auto respond integration but I have a problem with sending a message to the Customer using an API.I’m using https://github.com/intercom/intercom-node as a library for communication with intercom API. When I try to reply to the conversation using the adminID and I’ll provide operator user ID everything seems fine at the first glance so:api doesn’t return any error, message is added to the conversation in the inbox,But unfortunately email never arrives to the user.When I use different adminID everything works fine. I tried to search in the docs but I didn’t see if there are some limits related to sending a message as an operator. So my questions are: Is it possible to reply to the conversation using an Operator from the API?If it is possible do I need to add some extra configuration for the Operator in order to send messages to the user.

Hello, I simply need to know if it is possible to integrate Intercom's api using Google App Script. Every week, we require specific set of data, including chat participation, replies sent, customer satisfaction rate, and other data that you can see in Intercom's reports page. We currently don't have an API integration system for Intercom; instead, all the data we needed on a weekly basis is manually entered onto a specific Google sheet. It would be wonderful if you could suggest further approaches so that we may begin an API integration with Intercom. Thanks in advance.

Our platform uses our own Intercom instance for chat support, but a recent integration provided us with a second Intercom instance to also include in our application for customers to reach out to their support as needed.  I have been looking for documentation about the feasibility of this, but have been unable to locate any across the site. For our instance, we use the Intercom JavaScript library loaded by Segment.  Our instance uses the identify verification functionality, but the new instance to be included does not. Thanks for any insight into the feasibility of this, as well as any supporting documentation.

 Good morning, currently we are using the Intercom API with WhatsApp (inbound) and replying via the API. However, we are unable to find in the documentation how to respond to a conversation via API with an image. We would like to send an image directly, not just a URL.