OpenClaw on Telegram, WhatsApp & iMessage: Which Channel Is Right for You?

OpenClaw supports Telegram, WhatsApp, iMessage, Signal, Discord, and more. But when people ask "which one should I use?" the answer isn't one-size-fits-all.

Telegram is the fastest to set up. WhatsApp reaches the most people. iMessage is the most seamless if you're in the Apple ecosystem. Each has real tradeoffs.

Here's the full breakdown — with setup steps for each one — so you can pick the right channel and stop second-guessing it.

Quick Comparison

Factor	Telegram	WhatsApp	iMessage
Setup difficulty	Easy (10 min)	Medium (30–60 min)	Medium (Mac required)
Requires paid API?	No — free forever	Meta Business API (free tier exists)	No — uses your Apple ID
Works on Android?	Yes	Yes	No — Apple only
File / media support	Excellent	Good	Good
Multi-user / group support	Full	Groups supported	Group chats work
Best for	Everyone — easiest start	Sharing agent with others / business use	Mac + iPhone users who want seamless

Option 1: Telegram

✈️ Telegram Easiest Setup

Telegram is the default recommendation for most OpenClaw users. It's fast, free, has a real bot API, and works everywhere. If you're not sure which to pick — start here.

Setup Steps

Open Telegram and search for @BotFather (verify the handle is exact)
Send /newbot, follow the prompts, choose a name and username
BotFather gives you a token — copy it

Open ~/.openclaw/openclaw.json and add your Telegram config:

"channels": {
  "telegram": {
    "enabled": true,
    "token": "YOUR_BOT_TOKEN_HERE",
    "dmPolicy": "pairing"
  }
}

Restart your OpenClaw gateway: openclaw gateway restart
Open your new bot in Telegram and send /start
Your agent will prompt you to approve the pairing — confirm it

Common gotcha: If you send /start and get no response to the approval command, your bot token may have a stale session. Go to BotFather → revoke token → generate new one → update openclaw.json → restart gateway.

✅ Pros

Free bot API, no account verification needed
Best file/media support of any channel
Fast message delivery
Works on all platforms
Easy to share with a team

❌ Cons

Your contacts probably aren't on Telegram
Separate app from your normal messaging
Bot can't initiate conversations (users must message first)

Option 2: WhatsApp

💬 WhatsApp Medium Setup

WhatsApp makes sense if you want to share your OpenClaw agent with clients, family, or a team who are already on WhatsApp — which is 2 billion people. The setup is more involved but the reach is unmatched.

Two Paths

Path A: WhatsApp Business API (recommended) — Meta's official API for business accounts. Requires a verified phone number, Meta Business Manager setup, and approval (usually 1–2 days). This is the right path for professional or client-facing use.

Path B: Personal WhatsApp via unofficial bridge — Various community bridges exist that link your personal WhatsApp to OpenClaw. Works, but violates WhatsApp's ToS and risks account bans. Only use for personal/testing purposes.

Setup Steps (Business API Path)

Set up a Meta Business Manager account if you don't have one
Add a WhatsApp Business account and verify your phone number
Create a Meta app → add WhatsApp product → note your Phone Number ID and Access Token

In openclaw.json:

"channels": {
  "whatsapp": {
    "enabled": true,
    "phoneNumberId": "YOUR_PHONE_NUMBER_ID",
    "accessToken": "YOUR_ACCESS_TOKEN",
    "verifyToken": "choose-any-string"
  }
}

Configure your webhook URL in Meta's developer console — use your gateway URL + /channels/whatsapp/webhook
Restart gateway and send a test message to your WhatsApp number

Note on gateway exposure: The WhatsApp Business API requires a publicly accessible webhook URL. If your OpenClaw is on a local machine behind NAT, you'll need a tunnel (Cloudflare Tunnel, ngrok, or a VPS) to expose the webhook endpoint. This is the most common setup blocker.

✅ Pros

Your clients / family are already there
2 billion users — no app install required for recipients
Great for sharing agent access with non-technical people
Agent can send outbound messages (with Business API)

❌ Cons

More complex setup than Telegram
Requires public webhook URL (gateway exposure)
Meta approval process takes 1–2 days
Message templates required for outbound (template approval needed)

Option 3: iMessage

🍎 iMessage Mac Required

If you're on a Mac and an iPhone, iMessage is the most seamless option. You talk to your agent the same way you text anyone — no separate app, no bot accounts, no tokens to manage. It just shows up in your Messages app.

The catch: it requires a Mac running your OpenClaw gateway. It uses the imsg bridge tool to relay messages through the macOS Messages app. This means it only works if your gateway machine is a Mac (not a NUC, not a Linux VPS).

Setup Steps

Install the imsg bridge: follow the official OpenClaw iMessage docs
Grant accessibility permissions to imsg in System Settings → Privacy → Accessibility

In openclaw.json:

"channels": {
  "imessage": {
    "enabled": true,
    "dmPolicy": "pairing"
  }
}

Restart gateway
Send yourself a message from your iPhone to the Apple ID associated with your Mac
Approve the pairing prompt in OpenClaw

Best use case: You run OpenClaw on a Mac Mini as your home server. Your iPhone messages the Mac Mini's Apple ID. Your agent responds through Messages just like a normal text. Zero friction once it's set up.

✅ Pros

Native Messages app — no extra app needed
Seamless for Apple users
No API tokens or business accounts
Works with existing Apple ID

❌ Cons

Mac gateway required — won't work on Linux/Windows
Apple-only — Android users can't use it
Accessibility permissions can be finicky
No outbound message initiation

Which One Should You Actually Pick?

🎯 Decision Guide

Just getting started / unsure → Telegram. 10 minutes, free forever, works everywhere. Start here and switch later if needed.
Running OpenClaw on a Mac Mini and use iPhone → iMessage. Most seamless experience in the Apple ecosystem. Worth the setup time.
Sharing agent access with clients or non-technical family → WhatsApp. They're already there. Worth the extra setup for the reach.
Running a business with multiple users → Telegram or WhatsApp Business. Both handle multi-user well. WhatsApp if your audience is already there.
Privacy-first → Signal. Not covered here but OpenClaw supports it. Strongest end-to-end encryption, best for sensitive use cases.

Common Setup Problems (All Channels)

Regardless of which channel you pick, these issues come up constantly:

Gateway not running — run openclaw gateway status first. If it's not running, nothing works.
Token/config not reloaded — always restart the gateway after config changes: openclaw gateway restart
DM policy blocking messages — default is pairing (requires approval). If messages aren't getting through, check dmPolicy in your config.
Stale bot session — especially on Telegram after token regeneration. Full gateway restart usually fixes it.
Webhook not reachable — WhatsApp specifically needs a public URL. Use curl from an external machine to verify your webhook endpoint is reachable before debugging anything else.

Pro tip: You can run multiple channels simultaneously. Many people use Telegram for personal use and WhatsApp Business for client-facing interactions — same agent, different entry points.

🦞 Need Help Getting a Channel Connected?

ClawReady sets up OpenClaw channels as part of every setup package. If you're stuck on webhook config, pairing issues, or just want it done right the first time — book a call.

Book a Free 15-Min Call →

OpenClaw on Telegram, WhatsApp & iMessage:Which Channel Is Right for You?

Quick Comparison

Option 1: Telegram

Setup Steps

✅ Pros

❌ Cons

Option 2: WhatsApp

Two Paths

Setup Steps (Business API Path)

✅ Pros

❌ Cons

Option 3: iMessage

Setup Steps

✅ Pros

❌ Cons

Which One Should You Actually Pick?

🎯 Decision Guide

Common Setup Problems (All Channels)

🦞 Need Help Getting a Channel Connected?

OpenClaw on Telegram, WhatsApp & iMessage:
Which Channel Is Right for You?