# OU AI app

The customer-facing mobile app: what it is, how it differs from your agent, and why a business should care about it.

Source: https://docs.omazy.ai/how-to/app/

OU AI is the mobile app on the other end of `ou.chat`. It is a personal
assistant someone installs for themselves, and it is also where the agents
businesses publish can be reached and resumed.

Two products share one name, and keeping them apart is the whole of this
section:

| | **The personal assistant** | **Your business agent** |
|---|---|---|
| Belongs to | The person holding the phone | Your workspace |
| Knows | What they told it, across all their chats | What you published to it |
| Configured by | Nobody. It has no console. | You, in the console |
| Hands over to a human | Never | Yes, into your inbox |

Both appear in the same conversation list on the phone. Neither can read the
other, which is the point of the next section.

## Where it is up to

The app is in **private early access**. There is no App Store or Google Play
listing yet, and invites go out in batches by email. It runs on iOS 14 or later
and Android 7.0 or later, and ships dark themed only.

None of that blocks the parts you care about. Your agent is reachable at
`ou.chat/{your-handle}` in any phone browser today, with no app installed and no
account, which is how most people will meet it either way.

## What stays separate

A business agent published on `ou.chat` cannot read anything from a person's
personal assistant. The separation is enforced where the model and the tools are
resolved, not by policy or convention:

- Personal assistant memory is scoped to the person and carries no app. Your
  agent's retrieval cannot reach it.
- The personal assistant is given only platform-curated tools. It never receives
  a workspace's tools.
- The personal assistant never hands off to a human. There is no path from it
  into any operator inbox, including yours.

This runs in both directions, and it is worth saying out loud to a customer who
asks. What they tell your agent stays with your agent, and what they tell their
own assistant never reaches you.

## Why it matters to you

The app is another door to the same agent, and the useful property is that the
conversation survives the trip. Someone can start in the widget on your website,
scan a code at your counter, and pick the same thread up later, with everything
already said still there.

That means the work you do on the agent counts everywhere. You do not configure
a mobile version of it, and there is nothing to publish twice.

## In this section

- [Touchpoints](/how-to/app/touchpoints/) the six ways your agent and the app meet, and
  what you control at each
- [Using the app](/how-to/app/user-guide/) a guide for the person holding the phone,
  which your support team can point people at