You've got OpenClaw running and now you want it talking to real people, which in the Gulf means WhatsApp first. This is a hands-on OpenClaw WhatsApp setup guide, and it covers Telegram and Slack too, because most teams we work with end up connecting all three. The order matters, the auth differs per channel, and there are a handful of gotchas that will eat an afternoon if nobody warns you. Consider this the warning, with the fixes attached.
Quick context for anyone arriving cold. OpenClaw is the open-source, self-hosted AI agent (MIT licensed, OpenAI-sponsored, formerly Clawdbot and Moltbot). It runs as a local-first gateway that organises sessions, channels, tools, and events. Channels are how the agent reaches humans, and it supports a long list: WhatsApp, Telegram, Slack, Discord, Google Chat, Signal, iMessage, Teams, and Matrix. We'll focus on the three that cover most business needs. If you haven't installed yet, start with our pillar OpenClaw setup guide, then come back here.
Before you connect anything
A connected channel is only as reliable as the gateway behind it. Get the foundation right first.
- Confirm OpenClaw is installed and onboarded. The install is one line, `curl -fsSL https://openclaw.ai/install.sh | bash`, followed by `openclaw onboard`.
- Make sure you're on Node 24, or at least 22.19, and that your provider API key is configured.
- Run on a VPS with at least 2 vCPU and 4 GB RAM. If any channel will trigger browser automation, go to 8 GB or more.
- Apply the security hardening that shipped between late March and mid-April 2026. Channels are an exposed surface; don't connect them to an unpatched gateway.
One opinion worth stating up front: connect one channel, get it boringly stable, then add the next. Wiring all three at once turns a simple debugging session into a guessing game about which integration broke.
Connecting WhatsApp
WhatsApp is the one Gulf businesses care about most, and it is also the fussiest. Plan for it to take the longest.
The two paths
There are broadly two ways to connect WhatsApp, and the choice shapes everything after.
The first is the official WhatsApp Business API (via Meta). You provision a phone number, get it approved, and authenticate through Meta's platform with the relevant tokens. This is the right path for a real business: it's compliant and it won't get your number banned. It's also more setup work, and it involves Meta's approval process and message-template rules.
The second is an unofficial bridge that links a regular WhatsApp account. It's faster to stand up and tempting for a quick demo. Our honest take: don't run a business on it. These bridges break when WhatsApp changes things, and they risk your number. Use the official API for anything you depend on.
Setup and auth
For the official path, you configure your WhatsApp Business number and its access token in OpenClaw's channel configuration, then point Meta's webhook at your gateway so inbound messages route through. The verification handshake between Meta and your endpoint is where most first attempts fail.
WhatsApp-specific gotchas to expect:
- The 24-hour window. Outside a 24-hour window from the customer's last message, you can only send pre-approved template messages, not free-form text. Design your flows around this or your agent will go silent at the wrong moment.
- Template approval. Templates need Meta approval before use. Submit them early; approval isn't instant.
- Webhook reachability. Your gateway needs a stable, publicly reachable HTTPS endpoint with a valid certificate. Behind a flaky tunnel, messages drop silently.
- Number reputation. Sudden high volume from a fresh number invites rate limiting. Warm it up.
Connecting Telegram
After WhatsApp, Telegram feels like a holiday. It is the simplest of the three.
You create a bot through Telegram's BotFather, which hands you a bot token. Drop that token into OpenClaw's Telegram channel configuration, and the gateway connects. That's most of it.
A couple of notes that save confusion:
- Privacy mode. By default a Telegram bot in a group only sees messages that mention it or are commands. If you want the agent to read all group messages, you disable privacy mode via BotFather. Forget this and you'll swear the bot is broken when it's just being polite.
- Groups versus direct messages. Behaviour differs between one-to-one chats and groups. Decide which you're supporting and test both.
- Long polling versus webhooks. Telegram supports both. Polling is simpler to start; webhooks scale better. Begin with what gets you working, switch later if volume demands it.
Connecting Slack
Slack is the internal-team channel. This is where the agent helps your own staff: answering questions, monitoring GitHub, running commands, summarising threads.
You create a Slack app in their developer console, set the OAuth scopes the agent needs (reading messages, posting, and whatever tools you're exposing), then install it to your workspace to get the tokens. Slack also uses an Events API subscription so the gateway receives messages, which again means a reachable endpoint.
Slack gotchas:
- Scope discipline. Request only the scopes you actually use. Over-broad permissions are a security liability and they'll come up in any review.
- Event subscription verification. Slack pings your endpoint with a challenge on setup; it has to respond correctly or the subscription won't activate.
- Socket Mode. For deployments where you'd rather not expose a public endpoint, Slack's Socket Mode lets the app connect outbound instead. Handy when your gateway sits behind a tight firewall.
Keeping it reliable in production
Connecting a channel is the easy half. Keeping it reliable is the half that earns trust, and it's where the Human in the Loop philosophy pays off, because a person should be watching what the agent does on live channels.
- Monitor every channel. Track delivery, errors, and latency per channel. WhatsApp failing while Telegram is fine is a common, telling pattern.
- Handle tokens properly. Tokens expire and get rotated. Store them securely, watch for auth failures, and refresh before they bite.
- Rate-limit gracefully. Each platform has its own limits. Queue and back off rather than hammering and getting throttled.
- Stay patched. Channels are your exposed edge. Keep up with OpenClaw releases, especially security ones.
- Build escalation paths. When the agent is unsure, it should hand to a human, not improvise on a customer-facing channel.
A Dubai example
A Dubai real estate brokerage wanted one agent across WhatsApp for clients and Slack for their internal team. We connected WhatsApp through the official Business API so client conversations stayed compliant and template messages handled after-hours replies, then wired Slack so agents could query listing details and log leads without leaving their workspace. The early-uncertainty escalation rule meant any genuine negotiation went straight to a human broker. Stable inside a few days, and the brokers stopped copy-pasting the same answers into WhatsApp all evening.
Frequently Asked Questions
Should I use the official WhatsApp API or an unofficial bridge?
For any real business, the official WhatsApp Business API. Unofficial bridges are quicker to set up but break when WhatsApp changes things and can get your number banned. The official path is more work upfront and far safer to depend on.
Why does my agent ignore messages in a Telegram group?
Almost certainly Telegram's privacy mode, which is on by default and limits a bot in groups to seeing only mentions and commands. Disable it through BotFather if you want the agent to read all group messages. This catches nearly everyone the first time.
Do I need a public endpoint for all three channels?
WhatsApp and Slack's Events API generally need a reachable HTTPS endpoint, while Telegram can use long polling without one. If you can't expose a public endpoint, Slack's Socket Mode is a good outbound-only alternative.
How many channels can OpenClaw run at once?
Technically many at once, since the gateway is built for multiple channels. Practically, add them one at a time so you can confirm each is stable before the next. Memory is the main constraint; budget more RAM if a channel triggers browser automation.
Connecting OpenClaw to WhatsApp, Telegram, and Slack is straightforward once you know the auth path and gotchas for each, but production reliability is where most teams stumble. If you'd rather have it set up, hardened, and monitored from day one, our OpenClaw setup service deploys multi-channel agents in days and cuts onboarding complexity by around 90 percent. Start with the OpenClaw setup guide, then reach us at team@ins.ae or +971 58 995 4553.