Engage customers with email, push, and in‑app messages and support them with an integrated knowledge base and help desk.
The Intercom Messenger
The Intercom Messenger is the home for the conversations your customers have with you via Intercom, and the place where they can self-serve for support or to learn more about your product.
The Messenger works for both logged in and logged out users. It’s worth reading the detailed instructions in our developer docs on user management before you get started.
You can open the Intercom Messenger from a button in your app, programmatically when someone does something, or from a persistent button that sits over your app’s UI.
When you trigger the Intercom Messenger, your customer is presented with a home screen. This is configurable inside Intercom to change how it looks and what’s presented.
From there, your customer can search for help articles or start a conversation. A conversation goes to your inbox inside Intercom, and replies in both directions happen in real time. You can also send push notifications to your customers to let them know they have a reply after they’ve left your app.
You can send messages to your customers from Intercom, and the mobile SDK will present them in your app. Messages can be targeted at specific users or groups of users, and can be scheduled to be sent during specific time windows.
Companies use this for many use cases, including onboarding new users, announcing features, proactive support, important notices etc.
The mobile SDK supports many different message formats, all of which can be created and configured inside Intercom. These include:
Push notifications - these can open your app or follow a deep link.
Chats - messages from someone in your team to your customer.
Mobile Carousels - highly customizable, multi-screen messages with calls to action and device permissions.
Small posts - a short announcement.
Large posts - a full screen announcement.
We check for new messages when your app opens and whenever your customer or your app interacts with Intercom.
Installation
Intercom for Android supports API 21 and above.
There are 2 options for installing Intercom on your Android app.
Option 1: Install Intercom with Firebase Cloud Messaging (FCM)
Add the following dependency to your app's build.gradle file:
Apps targeting Android 13 should request a runtime permission to enable notifications.
Add the following code to request permission.
registerForActivityResult(
ActivityResultContracts.RequestPermission()
) {
if (isGranted) {
// Permission is granted. Continue the action or workflow in your// app.
} else {
// Explain to the user that the feature is unavailable because the// features requires a permission that the user has denied. At the// same time, respect the user's decision. Don't link to system// settings in an effort to convince the user to change their// decision.
}
}
Customer Support
👋 Contact us with any issues at Intercom Developer Hub available here. If you bump into any problems or need more support, just start a conversation using Intercom there and it will be immediately routed to our Customer Support Engineers.
Sample Apps
A project with some basic example integrations is provided here.
Setup and Configuration
Our installation guide contains full setup and initialisation instructions.
The configuration guide provides info on how to configure Intercom for Android.
Intercom Android SDK transitively depends on the above libraries. If your app is using any one of these libraries, they should at least be on the same major version that Intercom SDK is using.
When there are two versions of a library at build time, Gradle automatically picks the newer version.
This means if you are currently using say Glide 3.x, your app would automatically get Glide 4.x after including Intercom.
FAQs
Message composer used in Intercom SDK
We found that com.intercom:android-composer-gallery demonstrated a not healthy version release cadence and project activity because the last version was released a year ago.It has 0 open source maintainers collaborating on the project.
Package last updated on 14 Oct 2022
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.
A malicious npm campaign is targeting Ethereum developers by impersonating Hardhat plugins and the Nomic Foundation, stealing sensitive data like private keys.