Add help, support conversations and Ask AI to your mobile app

The messenger gives people one place in your app to get help. They can ask a question and get an AI answer drawn from your help center, start a conversation with your support team, or browse your help articles. Conversations land in your Userorbit support inbox, and your team's replies appear in the app as they're sent.

Before you begin

• Install the SDK: iOS or Android. On Android, the built-in messenger needs userorbit-android-ui.
• Identify signed-in people with identify, so conversations are linked to the right contact and your team knows who they're talking to.

Open the messenger

// iOS: opens a native sheet
Userorbit.shared.showMessenger()
swift

// Android: pass the current activity
UserorbitUI.showMessenger(activity)
kotlin

The messenger shows the sections your workspace has turned on for the widget:

Section	Shown when	What people can do
Ask a question	Ask AI is enabled	Type a question or tap a suggested one, and read a streamed answer with related articles.
Conversations	The support inbox is enabled for the widget	Start a conversation, see past ones and reply.
Browse help articles	Your workspace has a help center	Read your help center in an in-app web view.

Suggested questions come from your Ask AI settings in Userorbit, so you can change them without an app release.

Ask AI and handing off to your team

Answers stream in as they're written and keep formatting such as bold text and lists. Related help articles appear under the answer and open inside the app. The person can ask follow-up questions in the same thread.

If the answer doesn't help, the person taps Talk to a person. The SDK starts a support conversation that includes the full AI exchange, so your team can pick up where the AI left off without asking the person to repeat the question.

Support conversations

A new conversation opens with your greeting message. When an agent replies from the support inbox, the reply appears in the app right away, and the person sees a typing indicator while the agent writes.

The conversation list marks unread replies. Conversations belong to the current person, so reset on sign-out removes them from the device. They stay in your support inbox.

Build your own support interface

The built-in screens are optional. To use your own design, call the data methods directly:

• fetchMessengerSettings tells you which sections are enabled and returns suggested questions and the help center URL.
• fetchSupportThreads and fetchSupportThread load conversations and their messages.
• startSupportThread and sendSupportMessage send messages, with an optional JPEG screenshot.
• setSupportTyping reports when the person starts and stops typing.
• On Android, askAi, handOffToSupport and openSupportEvents cover Ask AI, the handoff and live updates. Their callbacks run off the main thread.

Good to know

• Live replies use a long-lived connection while a conversation is open. When the app is closed, new replies show the next time the person opens the messenger. The SDK doesn't send push notifications.
• The help center opens in an in-app web view, not the system browser.
• Your team answers mobile conversations in the same support inbox as web conversations.