Introduction
Hollo is a support chat that lives inside your iOS app. Your users tap Support, get an answer from Hollo's AI in seconds, and reach you when the AI can't help. You answer from one inbox, for every app you run.
This page explains the pieces, the words we use for them, and what's ready today.
How the pieces fit
| Piece | What it does |
|---|---|
| The SDK | A native chat screen you add to your app in Swift. It handles messages, push notifications and resending on reconnect. |
| Hollo AI | Answers from the docs and FAQs you give it, records its sources, and hands the conversation to you when it isn't sure. |
| The inbox | Where you see every conversation, from every app, with the user's details and device beside it. |
| Growth tools | Review requests, offers from your paywall and automations, all inside the same chat. These come later. |
A message takes this path:
- A user opens the chat in your app and writes to you.
- Hollo AI answers straight away, using only the sources you added.
- If the AI isn't confident, or the user asks for a person, the conversation is marked Needs you in your inbox.
- You reply from the inbox. The user gets a push notification and your reply appears in the chat.
Words we use
| Word | Meaning |
|---|---|
| Workspace | Your account on Hollo. It holds your apps, their users and conversations. |
| App | One of your apps. Each has its own settings, AI knowledge and app key. |
| App key | A public ID for your app, starting with app_. It's the only setting the SDK needs, and it's safe to ship. |
| User | Someone using your app. Anonymous by default, or named once you identify them. |
| Conversation | The one ongoing thread between a user and your team. It never splits into tickets. |
| Attributes | Short text values you attach to a user, like their plan, so your team can help faster. |
What your users see
- A Support button you place anywhere in your app, with an unread badge if you want one.
- A chat that looks like the rest of your app: your colours, font and wording.
- An answer in seconds, at any hour, clearly labelled as coming from AI.
- A person when they need one, and a push notification when you reply.
Users never create an account with Hollo. If your app has sign-in, you tell Hollo who they are, so you know who you're talking to and their history follows them across devices.
What's ready and what's coming
Hollo ships in stages. These docs mark anything that isn't ready yet as coming later.
| Area | Status |
|---|---|
| iOS SDK (SwiftUI and UIKit) | Early access |
| Identify users, attributes, sign-out, data deletion | Early access |
| Push notifications (APNs) | Early access |
| Theming in code, unread count | Early access |
| Hollo AI with sources and handoff | Early access |
| Inbox: filters, replies, close and reopen, basic profile | Early access |
| Setup with a coding agent, /llms.txt | Early access |
| Verified identity | Coming later |
| Photos in messages | Coming later |
| Remote appearance editor | Coming later |
| Team invites, roles, inbox search, Telegram | Coming later |
| Review requests, offers, automations, subscription webhooks | Coming later |
| React Native, Expo, Flutter, Android and web SDKs | Coming later, after iOS |
Requirements
- An iOS app that targets iOS 17 or later.
- Xcode 26 or later.
- Swift Package Manager. The SDK has no third-party dependencies.
Where to go next
- Early access: how invites, onboarding and pricing work.
- iOS quickstart: add Hollo to your app by hand in about ten minutes.
- Setup with a coding agent: let Claude Code, Cursor or Codex do it for you.
- Hollo AI: teach the AI what to say before you ship.