> For the complete documentation index, see [llms.txt](https://docs.dos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dos.ai/dosclaw/channels/overview.md).

# Overview

DOSClaw connects your autonomous AI agents directly to customer inboxes, team communication workspaces, and social messaging channels. Agents receive inbound messages in real time, apply relevant tools and knowledge bases, and send back rich interactive responses.

## Supported Channels

| Channel                                              | Protocol                       | Message Types                    | Key Capabilities                              |
| ---------------------------------------------------- | ------------------------------ | -------------------------------- | --------------------------------------------- |
| [Zalo OA](/dosclaw/channels/zalo.md)                 | Webhook / Official Account API | Text, Images, Interactive Cards  | Follower sync, human takeover, 2-way chat     |
| [Telegram](/dosclaw/channels/telegram.md)            | Bot API / Webhook              | MarkdownV2, Media, Commands      | Group chats, inline queries, instant pairing  |
| [Facebook Messenger](/dosclaw/channels/messenger.md) | Meta Graph API / Webhook       | Text, Quick Replies, Media       | Page inbox, comment-to-inbox auto-reply       |
| [Discord](/dosclaw/channels/discord.md)              | Discord Gateway / REST         | Markdown, Embeds, Slash Commands | Server moderation, threads, role-based access |
| [Slack](/dosclaw/channels/slack.md)                  | Slack Events API / Block Kit   | Blocks, Modals, Mentions         | Team assistant, channel monitoring, workflows |
| [WhatsApp](/dosclaw/channels/whatsapp.md)            | WhatsApp Cloud API             | Text, Media, Templates           | Global reach, end-to-end encrypted, concierge |
| [Lark / Feishu](/dosclaw/channels/lark.md)           | Open Platform Bot API          | Interactive Cards, Rich Text     | Enterprise chat, group mentions, card actions |

***

## How Channels Work

```
User Message
     │
     ▼
[Messaging Provider] (Zalo, Telegram, Meta, Slack, etc.)
     │  (Inbound Webhook)
     ▼
[DOSClaw Gateway / Event Router]
     │  (Context + Identity + Scope Guard)
     ▼
[Agent Container / Engine]
     │  (Knowledge Base + MCP Tools + Reasoning)
     ▼
[Outbound Dispatcher]
     │  (Formatted response, cards, media)
     ▼
User In-App Reply
```

### Key Architectural Concepts

1. **Independent Channel Bindings**: A single AI agent can listen and respond across multiple channels simultaneously (e.g. Zalo OA for Vietnam customers, Telegram for global community, and Slack for internal staff) while sharing the same underlying memory, personality, and knowledge base.
2. **Cross-Channel Identity**: DOSClaw associates customer identity across different channels when an identifying attribute (phone number, email, or verified account ID) is provided.
3. **Human Takeover & Handoff**: Every channel supports human agent takeover. When an agent detects customer frustration, an explicit request for human support, or when a human agent sends a message from the native channel console, the AI automatically pauses for that conversation session.
4. **Rate Limiting & Safety**: Inbound webhooks are signature-verified and rate-limited. Egress responses adhere to platform quotas and prevent spam loops.

***

## Getting Started

To connect a channel to an agent:

1. Open your agent in the **DOS.AI Dashboard** (`https://app.dos.ai/agents`).
2. Navigate to the **Channels** tab.
3. Select your desired platform and follow the step-by-step connection wizard.
4. Verify the connection by sending a test message to your bot.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dos.ai/dosclaw/channels/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.