OpenClaw Messaging Channels: Telegram, WhatsApp, Discord and More

OpenClaw is not a website you visit. It's an agent you talk to — wherever you already spend time. The channel system is what makes this possible: a flexible layer that routes your messages from any platform to the AI agent and back. This guide covers every major messaging channel, how to set each one up, and when to use which.

How the Channel System Works#

When you install DenchClaw and start the gateway, the agent goes online on port 19001. By default, you can talk to it via the web chat at localhost:3100. But that's just one channel. OpenClaw can simultaneously listen on dozens of channels — each one acting as a different "phone line" into the same agent.

When you send a message on Telegram, OpenClaw's Telegram channel adapter receives it, creates or retrieves your session context, and routes the message to the agent. The agent processes it, calls whatever tools are needed (querying DuckDB, browsing the web, sending an email), and the response gets routed back through the Telegram adapter to your phone.

Every channel shares the same agent and the same workspace. A contact you add via WhatsApp shows up in the same CRM you see in web chat. A cron job you schedule via Discord runs in the same OpenClaw instance. The channel is just the interface; the brain is shared.

Web Chat (Default)#

The web chat at localhost:3100 is the default and most feature-rich interface. It supports:

• Rich text responses with markdown rendering
• File uploads and attachments
• Code blocks with syntax highlighting
• Inline charts and data visualizations from the CRM
• Multi-session tabs

If you add the PWA to your Mac Dock (from Safari or Chrome, "Add to Dock"), it feels like a native app. This is the best channel for complex interactions — building apps, detailed CRM queries, running gstack workflows.

Telegram#

Telegram is the most popular channel for DenchClaw users because it combines mobile convenience with a robust API. Setup takes about 5 minutes:

1. Open Telegram and message @BotFather
2. Send /newbot and follow the prompts to create a bot
3. Copy the API token you receive
4. In your DenchClaw config, add the Telegram token under the telegram plugin
5. Message your new bot — it will respond through the OpenClaw agent

Telegram supports most response formatting: bold, code, and code blocks render correctly. Long responses get split into multiple messages automatically.

Best for: Quick CRM queries while mobile, adding contacts after meetings, checking pipeline status.

WhatsApp#

WhatsApp integration uses a QR code scan approach — no business API account required for personal use:

1. In your DenchClaw config, enable the wacli plugin
2. Run the setup command, which opens a WhatsApp Web session
3. Scan the QR code with your phone's WhatsApp
4. The agent is now connected to your WhatsApp session

DenchClaw can both receive messages (you text the bot) and send outbound messages to contacts. Note: WhatsApp's terms of service prohibit certain automated messaging patterns — use it for personal productivity, not bulk outreach.

Best for: Personal CRM on the go, quick lookups, conversational queries.

Discord#

Discord integration makes DenchClaw available as a bot in your server. This is particularly useful for small teams using Discord as their primary communication tool. See the openclaw-discord-bot guide for the full setup.

Key features of the Discord channel:

• Thread support — complex queries spin up a thread to keep context
• Multi-user — multiple team members can interact with the same agent
• Reactions — the agent can react to messages with emoji
• Slash commands — configure common queries as /commands

Best for: Team use, keeping CRM accessible in team communication, shared pipeline visibility.

Signal#

Signal integration is available through OpenClaw's Signal adapter. It requires running a signal-cli backend on your machine. See openclaw-signal-setup for setup instructions.

The Signal channel is the most private option — all communications are end-to-end encrypted. For security-conscious users (lawyers, healthcare providers, financial advisors), this is the recommended channel.

Best for: Privacy-sensitive workflows, healthcare or legal contexts.

iMessage#

The iMessage channel integrates through BlueBubbles or the imsg skill on macOS. It requires your Mac to be the primary iMessage device for your Apple ID. See openclaw-imessage for setup.

When connected, you can text your own Apple ID (from another device or contact yourself), and the agent responds. It also means the agent can send iMessages to your contacts — useful for sending follow-up messages drafted by the AI.

Best for: iPhone users who want native SMS/iMessage access, no third-party apps required.

Slack#

The Slack channel works through a Slack app integration. Install the OpenClaw Slack app in your workspace, add the bot to channels, and mention it with @openclaw to invoke the agent.

Slack's threading model works well with OpenClaw — complex tasks spawn threads, simple queries reply inline.

Best for: Teams already on Slack, enterprise deployments, keeping CRM in the same tool as team communication.

Email (Himalaya)#

Through the himalaya skill, OpenClaw can receive and process emails. You configure a dedicated email address (or use a subaddress like you+openclaw@gmail.com) that pipes incoming messages to the agent.

This enables email-to-action workflows: forward an email to your OpenClaw address, and the agent can add the sender to your CRM, extract action items, draft a reply for review, or add follow-up tasks.

Best for: Email-heavy workflows, processing inbound leads from email, email-first teams.

Choosing the Right Channel#

Here's a quick reference:

Multi-Channel Use#

You don't have to pick one channel. Most DenchClaw users run 2–3 channels simultaneously. A common setup:

• Web chat for complex sessions (building apps, detailed CRM work)
• Telegram for mobile access and quick queries
• Discord for team pipeline visibility

All channels share the same session context and the same workspace. The agent remembers context across channels — a conversation you start on Telegram can be continued in web chat.

Channel-Specific Formatting#

Different channels have different formatting support. OpenClaw's channel adapters handle this automatically, but it's good to know:

• Markdown tables work in web chat and Telegram, but not WhatsApp
• Code blocks render in Telegram, Discord, Slack — not in SMS/iMessage
• Long responses are automatically chunked for SMS channels
• File attachments are supported in all channels, but thumbnails vary

The agent adapts its response format based on the channel. Ask for a CRM report in WhatsApp and you'll get a bulleted list; ask in web chat and you get a rendered data table.

Frequently Asked Questions#

Can multiple people use the same OpenClaw agent across different channels?#

Yes. The Discord and Slack channels support multiple users. Each user gets their own session context while sharing the same workspace data. For a small sales team, this means everyone can query the same CRM pipeline from their preferred app.

What happens if my Mac is sleeping and someone sends a message?#

Messages queue in the channel (Telegram, Discord etc.) and are processed when the agent comes back online. The gateway needs to be running for real-time responses. You can configure the gateway to run as a launch agent that starts automatically on login.

Is there a channel for Google Chat or Teams?#

Google Chat and Microsoft Teams adapters are available but require more complex setup (workspace/OAuth apps). Check the OpenClaw docs for the current list of supported channels.

Can I use multiple Telegram bots with one OpenClaw instance?#

Yes — you can configure separate bots for different purposes: one for personal use, one shared with a team. Each bot gets its own session context.

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →