Popular Topics

We are developing a workflow to assist users in troubleshooting issues by narrowing down their concerns through a hierarchical structure of business capabilities. This involves guiding users through: 20 Business Capability Domains 98 Business Capability Categories 597 Business Capabilities 12 Issue Types Approximately 20 Options per Issue Type On average, each domain encompasses about 4.9 categories (98 categories ÷ 20 domains), and each category includes approximately 6.1 capabilities (597 capabilities ÷ 98 categories).Notably, the 12 issue types are applicable across all 597 business capabilities, eliminating the need for individual paths beyond the business capability selection.Specific Requirements: Single Business Capability Selection: Users should be able to select one specific business capability from the hierarchy. Multiple Issue Types Selection: After selecting a business capability, users can choose multiple issue types from a list of 12 options. Detailed Options

Edit: Title should be “Intercom working fine on Xcode Simulator builds but not loading on testflight builds” but I can't edit it or delete this.I have added the camera privacy reason. Yet on TestFlight builds Intercom does not load. I am wondering if the SDKs access to a certain URL is being blocked because it needs to be manually allowlisted somewhere in the privacy configuration? But not sure on that. Documentation does not say anything about this.Are there other reasons this may happen?

Seems that when installed Intercom overrides the tint color for the whole app. There are ways around that of course but this is likely causing unexpected repercussions for SwiftUI apps using tints.

Hi, We have some set of tool which fetch an article by id. Recently it worked, however after the move of articles to knowledge hub i cant retire a single articles withcurl -i -X GET 'https://api.intercom.io/article/{articleId}' \ -H 'Authorization: Bearer <secret>' \ -H 'Intercom-Version: 2.11'.However we can fetch all articles with api.intercom.io/articles, so maybe something has changed.All help would be greatly appreciated.

Hello everyone,I’m Darshan Hiranandani, We're currently working on implementing a ticketing and ticket portal system, and we're looking to import customer tickets from another provider into Intercom. While we've successfully been able to create tickets using the API, we are running into a challenge when it comes to linking a company to a ticket.Currently, an admin can manually link a company to a ticket in the inbox, but we haven’t found a way to make this step mandatory. This is an issue because without a linked company, the customer won't be able to access the ticket via the portal, though they can still see it through the messenger. We want to avoid confusion in this regard.We also have trouble retrieving the company linked to a specific ticket using the GET /tickets/{id} endpoint.This leads to the following questions:Is there a way to link a company to a ticket programmatically through the API? Can we retrieve the linked company information through the API? How can we enforce the c

I wanted to know if you have any solution regarding this error?buildscript { ext { buildToolsVersion = "34.0.0" minSdkVersion = 23 compileSdkVersion = 34 targetSdkVersion = 34 ndkVersion = "26.1.10909125" kotlinVersion = "1.9.22" } repositories { google() mavenCentral() } dependencies { classpath("com.android.tools.build:gradle:4.0.1") classpath("com.facebook.react:react-native-gradle-plugin") classpath("org.jetbrains.kotlin:kotlin-gradle-plugin") }}apply plugin: "com.facebook.react.rootproject"gradlew propertiesdistributionBase=GRADLE_USER_HOMEdistributionPath=wrapper/distsdistributionUrl=https\://services.gradle.org/distributions/gradle-8.6-all.zipnetworkTimeout=10000validateDistributionUrl=truezipStoreBase=GRADLE_USER_HOMEzipStorePath=wrapper/distsI look forward to a quick response, thank you very much.

Hi!We’re experiencing a non negligible amount of crashes with our iOS app. We’re using the Intercom iOS SDK v18.2.0 (AKA the latest). As far as we can see, the user goes into the intercom integration, and at some point it crashes.Here is the crash-logs from Sentry: OS Version: iOS 18.0.1 (22A3370)Report Version: 104Exception Type: EXC_CRASH (SIGABRT)Crashed Thread: 0Application Specific Information:Expected dequeued view to be returned to the collection view in preparation for display. When the collection view's data source is asked to provide a view for a given index path, ensure that a single view is dequeued and returned to the collection view. Avoid dequeuing views without a request from the collection view. For retrieving an existing view in the collection view, use -[UICollectionView cellForItemAtIndexPath:] or -[UICollectionView supplementaryViewForElementKind:atIndexPath:]. Dequeued view: <IntercomSDK_ITBBlockCollectionViewCell: 0x1224ccc00; baseClass = UICollectionViewCell;

I’m referencing this API documentation https://developers.intercom.com/docs/references/unstable/rest-api/api.intercom.io/data-attributes/updatedataattribute for updating data attributes -1. is it possible to use APIs to update relationship attributes between different standard intercom objects (contact, conversation, ticket)?2. is it possible to use APIs to update relationship attributes between standard intercom objects (e.g. contact) and custom objects?

Execution failed for task ':app:mergeExtDexDevelopmentDebug'.> Could not resolve all files for configuration ':app:developmentDebugRuntimeClasspath'.   > Failed to transform intercom-sdk-base-15.11.3.aar (io.intercom.android:intercom-sdk-base:15.11.3) to match attributes {artifactType=android-dex, asm-transformed-variant=developmentDebug, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=24, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-runtime}.

I’m using the unstable version of the api to see if i can list data attributes on custom objects and doesn’t seem like this is possible.  When will this be allowed? {"type": "error.list","request_id": "001g71vtd1equmb5qab0","errors": [{"code": "parameter_invalid","message": "unsupported model parameter [campaign]"}]}

Hello!It looks like the reporting is going to be changed soon. The report for tag totals by month is somewhat limited, and it seems this is no longer going to be available beyond just listing 10 top tags used along with their total number.With the new layout, how can one download the conversation tags and total number used for the entire month, not just the top ten the new report shows?What I am finding is you’d have to download the conversations, sort by conversation tags, and then manually count those tags using this new layout. Is that true?? That just feels like this is making more work to produce what was already easy to pull on legacy reporting.Perhaps it’s my error and I am just not seeing this as being available in the new format, it’s entirely possible the report is available, but I am just not finding it on my end.Thank you so much for any assistance you might have and guidance. 

Hi!We’re using the Intercom SDK on our iOS app, currently using version 18.1.0. We’ve been getting a lot of crash reports and it seems to mostly happen to users on iOS 15.8, looking into it we found a stack trace that points to swizzling done by the Intercom SDK: Any ideas on how to fix this?

App ConditionsIn our AppDelegate we return true from application:continueUserActivity:restorationHandler:  We have IntercomUniversalLinkDomains configured in the Info.plist fileSteps to ReproduceOpen and intercom chat and type in the link https://www.nuuly.com/feedbackTap on the link, once it becomes tappable in Intercom chatExpected Behavior:Do not open Safari when a url is matched with an entry from IntercomUniversalLinkDomains and ONLY handle in application:continueUserActivity:restorationHandler: returns true Actual BehaviorApp handles link in application:continueUserActivity:restorationHandler:b but Safari also opens the link before App can handle it Intercom SDK: 17.0.0iOS: 17.2

I have determined that Our iPad app is experiencing Airplay issues that are being caused by the Intercom API. Setup:Intercom.setApiKey(apiKey, forAppId: appId)let userAttributes = ICMUserAttributes()userAttributes.userId = user.userIDIntercom.setUserHash(userHash)Intercom.loginUser(with: userAttributes) Steps to reproduce:cold launch the app Have above code run for Authenticated users Turn on Airplay to TV or Apple TV Issue: External screen is blackNote: Turning airplay off and back on solves the issue. Troubleshooting:Commenting the following lines of code solves the issue:Intercom.setUserHash(userHash)Intercom.loginUser(with: userAttributes)I have tried disabling Intercom swizzling as per your documentation but it has no affect.  Currently using Intercom 17.4.0

There seems to be an issue with the Intercom API. I'm using the tickets/search POST call and it's only retrieving 97 of my 225 tracker tickets.POST: https://api.intercom.io/tickets/searchThe body of my API call looks like this:{"query": {"operator": "AND","value": [{"field": "open","operator": "=","value": true},{"field": "ticket_type_id","operator": "=","value": 2}]},"pagination": {"per_page": 100}} I also tried:{"query": {"operator": "AND","value": [{"field": "open","operator": "=","value": true},{"field": "ticket_type_id","operator": "=","value": 2}]},"pagination": {"per_page": 100}}

Hi everyone,We’re working on setting up email aliases to route specific queries to a main inbox (support@....com) while keeping them categorized separately by type (e.g., premium, legal, billing).For instance, we want emails sent to premium.support@....com or legal.support@....com to be forwarded to the main support inbox, but with tags that categorize them as “premium” or “legal” accordingly.Could anyone assist with configuring these aliases so that customer queries are correctly tagged when they land in the main inbox?Thanks 

Release Date: 11-12-2024 🐛 Bug Fixes Solves a crash in carousels. Addressed issue where video input wasn’t available in a conversation. Fixes issue where first part in a conversation would fail to show as failed in the scenario where it didn’t send. Resolved some layout issues in the conversation screen for users with large font sizes enabled. Note This release contains some beta features.

Good day. Could you please advise how to download conversations by filtering them based on workspaces, views, agent, tags, and closed status? I tried filtering by workspaces and views, but I couldn't find how to do it.

While I’m typing Japanese text with IME (Input Method Editor)  If I hit enter here, I expect it to finalize the Japanese text with IME BUT not sent it as a chat message yet. But this widget sent the unfinished text any way.

When entering Japanese text with an IME, pressing the Enter key mistakenly sends the incomplete text to chat. If I press Enter here, I anticipate finalizing the Japanese text with the IME, but not sending it as a chat message yet. However, this widget still sends the unfinished text anyway.

Hi everyone, I’m newbie in Intercom and I would like to custom the inbox app, so it will have a button when hover over the message which will call our API when press. I guess it will be involved to develop an inbox app, but how to add the button to the message like below?Thanks in advanceRegards,James 

Is there any setting where customers will see the name of an agent, but internally within our organization, we will be able to see the original name?

Hey everyone, I’m using the official Intercom Jira add-on and it works great. We also have some workflows set up to sync Jira and Intercom ticket statuses 🔥How are you keeping track of which issues are linked with Intercom in the Jira issue though? For example, let’s say we’re closing out a sprint and a handful of Jira issues might be linked with Intercom tickets. How do you know which ones to go close out?

Description:We are facing an issue where push notifications are not working on iOS in our Ionic app. Below are the details of our setup and steps taken:App Setup:We are using Ionic version 7.2.0.The Intercom integration is done using the @capacitor-community/intercom plugin.Intercom and Capacitor Registration:We have registered Intercom with the following keys:androidApiKey: android_sdk-xxxxxandroidAppId: lnp0halaiosApiKey: ios_sdk-xxxxxiosAppId: lnp0halaPush Notification Setup:An iOS push key was created and successfully uploaded to the "Set Up Push Notifications" section in Intercom.Issue:Despite the above setup, push notifications are not working on iOS devices. We can make sure the correct permissions are set and when app launching it asks for the specific access.Could you please help us troubleshoot and resolve this issue? Let us know if you need additional details or logs to assist in the investigation.Thank you 8:39

hi expert team,i recenty use my iphone mobile phone but non idia how can integrat my mobile api?