# Connect

Channels, the chat widget, and integrations with the tools you already run.

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

How customers reach your agent, and how your agent reaches your other systems.

| Surface | What it is for |
|---|---|
| **Widget** | The chat widget on your website. Appearance, placement, language, and what it offers before anyone types. |
| **Channels** | The other places customers message you. |
| **Short links and QR codes** | Your agent at `ou.chat/yourbrand`, on a phone, with nothing installed. |
| **Integrations** | Connections to the tools you already run. |
| **AI assistants** | Let Claude or another MCP client work on a business directly. |

## The widget is a product decision, not a snippet

It is the first thing a visitor sees, and its landing state does more for
resolution rate than most agent tuning. What it offers before a question is
asked, whether it leads with a catalog or a question, and how it looks on a
phone are all configurable, and all worth deciding deliberately.

## In this section

- [Channels and integrations](/how-to/connect/channels/) the other doors in
- [Connect an AI assistant](/how-to/connect/mcp/) give Claude scoped access to one business

Two doors have their own sections: [Widget](/how-to/widget/) for your website, and
[OU AI app](/how-to/app/) for the short link, the QR code, and the phone. The link and
the code are the cheapest doors you have, and they need no code at all.

Still to come: appearance and layout, and the landing state in depth.