Which messaging app should I use with OpenClaw?

Use whatever you already message in. Telegram is the easiest to set up (just a BotFather token). WhatsApp gives you the broadest reach for personal contacts. Slack and Microsoft Teams are best for work contexts. iMessage requires a Mac and is iOS-friendly. Discord works well for community or hobby use. There is no single best — pick the one your daily chats already happen in. See choosing a channel for a detailed comparison.

Do I need a paid plan for any OpenClaw channel?

No. Every OpenClaw channel — Telegram, WhatsApp, Slack, Discord, Signal, iMessage, Microsoft Teams, webchat — works on the free tier of the underlying platform. You only pay for AI API calls to your chosen provider (OpenAI, Anthropic, Google, or local Ollama). Typical personal use runs $1–10/month. See pricing for a full cost breakdown.

Can I connect OpenClaw to more than one channel at the same time?

Yes. OpenClaw can serve multiple channels simultaneously from one gateway — for example, Telegram for personal chats, Slack for work, and Discord for a community, all on the same agent. Each channel has its own setup guide, and you can add new channels at any time without restarting existing ones.

What hardware do I need to run OpenClaw channels?

Any machine running Node.js 22.16+ on macOS, Linux, or Windows. The gateway uses under 200 MB RAM, so a Raspberry Pi 5, an old laptop, or a $5/month VPS all work. iMessage is the one exception — it requires macOS. See system requirements for the full hardware matrix.

Channels – HowOpenClaw

Channels are how you communicate with your agent. Rather than forcing you into a dedicated app, OpenClaw meets you in the messaging tools you already use — your phone, your workspace, your community.

Each channel has its own setup guide with step-by-step instructions.

Pick your channel

Slack

Best for work and team contexts. Socket Mode keeps your agent connected behind firewalls and corporate VPNs — no public URL required.

The easiest channel to start with. Create a bot in 2 minutes and message it from any device, anywhere in the world.

Discord

Great for communities and casual use. Works across servers with per-channel routing and optional auto-generated thread names.

Use your existing WhatsApp number. Unofficial API — ideal for personal use rather than business accounts.

Signal

Maximum privacy. End-to-end encrypted by default. Best for sensitive use cases where data confidentiality matters.

iMessage

Connect via BlueBubbles for reliable iMessage integration. Requires a Mac running the BlueBubbles server.

WebChat

Zero setup — the fastest way to test OpenClaw locally. No account needed. Start here before connecting other channels.

Microsoft Teams

Enterprise-grade deployment with the official Teams SDK. Streaming replies, welcome cards, typing indicators, and native AI labeling.

Not sure which channel to pick? See the channel decision guide.

Starting strategy

Don't connect everything at once. The most common mistake is setting up five channels simultaneously and ending up with five unstable connections and no idea which config is the problem.

Recommended starting order:

WebChat — zero setup, perfect for testing your agent locally
Telegram or Slack — whichever fits your primary daily context
Add more channels once the first two are stable

Security is per-channel

A critical point: security settings are per-channel. An allowlist on iMessage doesn't automatically apply to Telegram. An open DM policy on WebChat doesn't affect Slack.

Review DM policy and tool permissions separately for each channel you connect. Start restrictive and loosen as needed.

Message routing

The MESSAGING.md file controls how your agent handles incoming messages across all channels. Write it in plain English — your agent reads it as natural language instructions.

Route all work-related requests from Slack to my work assistant mode.
For iMessage, use a casual conversational tone.
Priority messages that require immediate attention should respond even during quiet hours.

For advanced multi-channel routing, see Module 2: Connecting Apps.