ClawHosters
by Daniel Samer
5 min read
Most people think you need the WhatsApp Business API, Meta developer approval, and per-message fees to run a whatsapp ai chatbot. You don't. OpenClaw connects through Baileys, an open-source implementation of WhatsApp's Web protocol. It works exactly like linking WhatsApp Web to your phone. No approval process, no monthly message charges.
But there are a few things you should sort out before scanning that QR code.
Before You Start
Check your linked devices. Open WhatsApp on your phone, go to Settings, then Linked Devices. WhatsApp allows a maximum of four companions per account, and OpenClaw takes one slot. If you're already using WhatsApp Web on two browsers and an iPad, you're at the limit.
Pick your phone number carefully. A dedicated eSIM from a normal carrier is the safest option. If your bot number gets flagged, your personal chats stay untouched. VoIP numbers from providers like Google Voice or TextNow won't work. WhatsApp blocks them within 48 hours. That's not a recommendation, it's a hard technical requirement.
Setting Up WhatsApp on ClawHosters
If you're running OpenClaw through ClawHosters, the process takes about two minutes.
Step 1: Log into your ClawHosters dashboard and enable the WhatsApp channel for your agent.
Step 2: The dashboard generates a QR code. You have 60 seconds to scan it. On your phone, open WhatsApp, go to Settings, tap Linked Devices, then Add Device. Point your camera at the QR code.
That's it for the connection itself.
Step 3: Choose your access policy. This controls who can talk to your bot.
Pairing mode (default): New contacts send a message, receive a pairing code, and you approve them through the dashboard. Probably the right choice for most setups.
Allowlist: Only phone numbers you've pre-approved (in E.164 format, like +15551234567) can reach your agent. Stricter, good for business use.
Open: Anyone can message your bot. I'd only use this for testing.
Step 4: If you want your agent responding in group chats, enable that separately. Mention-only mode is worth considering here so the bot only replies when someone @-tags it, rather than jumping into every conversation.
Self-Hosted vs. ClawHosters
You can absolutely run OpenClaw on your own VPS. But WhatsApp is the channel where self-hosting creates the most headaches.
The biggest one: credential persistence. OpenClaw stores WhatsApp session data locally. On a self-hosted Docker setup, if you forget to bind-mount the credentials directory, every container restart forces a fresh QR code scan. At 3 AM when your server reboots after a kernel update, that's not fun. ClawHosters handles persistent storage automatically, so your session survives restarts without intervention.
Static IP matters too. VPS deployments with stable IPs maintained sessions for 23 days straight in testing. Mobile hotspot setups disconnected three times more often within 48 hours.
ClawHosters also handles automatic OpenClaw updates, which matters for security patches and Baileys protocol compatibility. You can start with a 3-day free trial to test it.
Common Issues and Fixes
QR code expired before you could scan it. Re-trigger the login from your dashboard. The 60-second window is tight, so have your phone ready before you generate the code.
Session dropped. This usually means your phone was offline for more than 14 days, or you hit the four-device limit by linking something else. Unlink a device you're not using and reconnect.
VoIP number got banned. There's no fix. Get a real SIM or eSIM and start over.
Bot doesn't respond to new contacts. If you're in pairing mode, new contacts need approval. Check your dashboard for pending pairing requests.
For more detailed troubleshooting, the WhatsApp setup docs cover edge cases we can't fit here.
A Note on WhatsApp's Terms of Service
Honest answer: WhatsApp's Terms of Service don't allow automation on personal accounts. In October 2025, WhatsApp updated its terms to ban general-purpose chatbots from its Business API platform. That ban targets companies distributing chatbots at scale through official channels, not personal linked devices running a private assistant.
Using OpenClaw as a personal AI assistant on a dedicated number with low message volume is where most users land. It's a gray area. Know the risk, use a dedicated number, and keep volumes reasonable.
