How to Set Up OpenClaw on WhatsApp: Complete Guide 2026

WhatsApp is the world's most popular messaging platform, with over 2 billion monthly active users across 180+ countries. It is also one of the most complex channels to connect to an AI agent. This guide walks you through every step: from setting up a Meta Business account to configuring OpenClaw's WhatsApp plugin, handling message templates, navigating the 24-hour messaging window, and dealing with the compliance requirements that trip up most teams.

If you have set up a Telegram bot before, you know the process takes about 5 minutes: talk to BotFather, get a token, paste it into your config, done. WhatsApp is a different story. Meta's business verification process, API access tiers, message template approvals, and opt-in requirements make WhatsApp integration significantly more involved. The payoff is access to the largest messaging audience on the planet, in a channel where business messaging open rates exceed 95%.

This guide covers the full process from scratch. If you already have a Meta Business account or WhatsApp Business API access, skip ahead to the relevant section. If you want to skip the entire process and have it handled for you, jump to Skip the WhatsApp Headaches.

Why WhatsApp for AI Agents

WhatsApp is not just another messaging channel. It occupies a unique position in business communication that makes it especially valuable for AI agents:

• 2 billion+ monthly active users. In markets like India, Brazil, Indonesia, Nigeria, and much of Europe, WhatsApp is the primary communication tool. It is not an alternative to SMS or email. It is the default.
• 95%+ open rates. Email averages 20-30% open rates. SMS averages 45-50%. WhatsApp business messages consistently exceed 95%. When your AI agent sends a message on WhatsApp, it gets read.
• Rich media support. WhatsApp handles text, images, documents, PDFs, audio messages, video, location pins, and contacts natively. Your agent can send invoices, product catalogs, receipts, and visual responses without pushing users to a web link.
• End-to-end encryption. WhatsApp messages are encrypted in transit by default. This matters for businesses handling sensitive customer data, and it matters for the compliance conversation with your legal team.
• Business-first features. Interactive message templates with buttons, quick replies, product catalogs, payment integration (in supported markets), and verified business profiles give AI agents more capabilities than plain text chat.

The catch is that Meta controls the platform, and Meta has strict rules about how businesses use WhatsApp. These rules exist to prevent spam and protect users, which is good for the ecosystem, but they add complexity that other channels do not have.

WhatsApp Business API vs. WhatsApp Cloud API

Before you start, you need to understand the two ways to connect to WhatsApp programmatically. This decision affects your setup process, cost structure, and operational flexibility.

WhatsApp Cloud API (Recommended)

The Cloud API is hosted by Meta directly. It is the newer, simpler option and the one most teams should use.

• Hosting: Meta hosts the API infrastructure. You do not need to run a separate API server.
• Cost: Free for the first 1,000 service conversations per month. After that, pricing varies by country (roughly $0.005-$0.08 per conversation depending on the market).
• Setup time: 30-60 minutes for basic access (once your Meta Business account is verified).
• Rate limits: Starts at 250 messages per 24 hours for new numbers. Increases to 1,000, then 10,000, then 100,000 as you build quality history.
• Best for: Most businesses, especially those starting out or handling fewer than 100,000 conversations per month.

WhatsApp Business API (On-Premises)

The on-premises API runs on your own infrastructure. It is the original option, now largely superseded by the Cloud API.

• Hosting: You host the API on your own servers. Requires Docker and a dedicated database.
• Cost: Same per-conversation pricing as Cloud API, plus your server costs.
• Setup time: 2-8 hours including server provisioning and configuration.
• Rate limits: Same tier system as Cloud API.
• Best for: Enterprises with strict data residency requirements or those needing very high throughput (100,000+ conversations per month).

For connecting to OpenClaw, use the Cloud API. It is simpler to set up, easier to maintain, and does not require additional server infrastructure. The OpenClaw WhatsApp plugin supports both, but the Cloud API path has fewer failure points.

Step 1: Create a Meta Business Account

Everything in the WhatsApp Business ecosystem starts with a Meta Business account. If you already have one (for Facebook ads, Instagram business, etc.), you can use it. If not, here is how to create one.

1. Go to business.facebook.com and click "Create Account."
2. Enter your business name, your name, and your business email address.
3. Fill in your business details: legal name, address, phone number, website, and business category.
4. Accept Meta's terms of service.

After creation, you will land on the Meta Business Suite dashboard. Note your Business Manager ID (visible in the URL or under Business Settings > Business Info). You will need this later.

The Verification Process

Here is where things get complicated. Meta requires business verification before granting full WhatsApp API access. This is not a rubber stamp.

What Meta needs from you:

• A legal business name that matches official documents
• A business phone number (landline or mobile)
• A business address that matches official documents
• At least one of: business registration certificate, articles of incorporation, tax filing, utility bill in the business name, or bank statement
• A business website with a matching domain in your email address

How long verification takes:

• Best case: 2-3 business days
• Typical: 1-2 weeks
• Worst case: 4-6 weeks (if documents are rejected and you need to resubmit)

Common rejection reasons:

• Business name on documents does not match the name in your Meta Business account exactly (including punctuation, capitalization, and legal suffixes like "LLC" or "Inc.")
• Documents are expired, illegible, or in a language Meta cannot verify
• The website domain does not match the business email domain
• The business category selected does not match what the documents describe
• Using a personal phone number instead of a business number

Pro tip: Before submitting for verification, double-check that every field in your Meta Business account matches your official documents character for character. A mismatch between "MyCompany LLC" and "MyCompany, LLC" (note the comma) is enough to trigger a rejection. Each rejection resets the review queue timer.

Step 2: Set Up a WhatsApp Business Account

With your Meta Business account verified (or while waiting for verification, since you can start some of these steps in parallel), create a WhatsApp Business account.

1. In the Meta Business Suite, go to Business Settings > Accounts > WhatsApp Accounts.
2. Click "Add" and follow the prompts to create a new WhatsApp Business account.
3. You will be asked to add a phone number. This is the number your AI agent will use to send and receive messages.

Choosing a Phone Number

The phone number you register is the identity of your AI agent on WhatsApp. Choose carefully:

• Dedicated number: Use a number exclusively for your AI agent. Do not use your personal number or your main business line. Once a number is registered with the WhatsApp Business API, it cannot simultaneously be used with the regular WhatsApp app.
• Virtual numbers: You can use a virtual phone number (from providers like Twilio, Vonage, or a local VoIP provider), but it must be able to receive either an SMS verification code or a phone call for the initial verification step.
• Country code matters: The country code of your number affects messaging pricing. Messages sent to users in the same country as your number are cheaper than cross-border messages in most markets.

Number Verification

WhatsApp will verify your phone number by sending an SMS code or making a voice call. Make sure the number can receive one of these before starting the process. If using a virtual number, confirm SMS delivery works with your provider beforehand.

Step 3: Access the WhatsApp Cloud API

Now you need to connect your WhatsApp Business account to the Cloud API so your OpenClaw agent can send and receive messages programmatically.

1. Go to developers.facebook.com and log in with the same account linked to your Meta Business account.
2. Click "My Apps" in the top navigation, then "Create App."
3. Select "Business" as the app type.
4. Give your app a name (e.g., "MyCompany AI Agent") and select your Meta Business account.
5. Once the app is created, find "WhatsApp" in the product list on the left sidebar and click "Set Up."
6. Link your WhatsApp Business account to this app.

Get Your API Credentials

From the WhatsApp section of your app dashboard, you need three pieces of information:

• Phone Number ID: Found under WhatsApp > API Setup. This identifies your registered phone number in API calls.
• WhatsApp Business Account ID: Also on the API Setup page. This identifies your WhatsApp Business account.
• Access Token: You can generate a temporary token from the API Setup page for testing. For production, you need a permanent System User token (covered below).

Create a Permanent Access Token

The temporary token from the API Setup page expires after 24 hours. For production use with OpenClaw, you need a permanent token.

1. In your Meta Business Suite, go to Business Settings > Users > System Users.
2. Click "Add" to create a new system user. Name it something descriptive like "OpenClaw Agent."
3. Set the role to "Admin" (required for full WhatsApp API access).
4. Click "Generate New Token" for the system user.
5. Select your WhatsApp app from the dropdown.
6. Grant the following permissions:
   • whatsapp_business_messaging
   • whatsapp_business_management
7. Click "Generate Token." Copy and save this token immediately. It will not be shown again.

Security note: This token grants full control over your WhatsApp Business account. Store it securely. Do not commit it to version control, paste it in Slack, or include it in screenshots. If you are running OpenClaw on your own server, the token should be in an environment variable or a secrets manager, not in a configuration file.

Step 4: Configure the Webhook

WhatsApp delivers incoming messages to your server via webhooks. You need to tell Meta where to send them.

Webhook Requirements

• Your server must be accessible over HTTPS (not HTTP). Meta will not deliver webhooks to unencrypted endpoints.
• Your endpoint must respond to a GET verification request with a specific challenge token.
• Your endpoint must respond to POST requests containing incoming messages within 5 seconds (or Meta will retry and eventually throttle you).

Set Up the Webhook Endpoint

If you are running OpenClaw on a VPS behind a reverse proxy with TLS (as described in our OpenClaw setup guide), your webhook URL will look something like:

https://your-domain.com/webhook/whatsapp

OpenClaw's WhatsApp plugin handles the webhook verification and message processing automatically. You just need to configure the URL and a verify token.

Register the Webhook with Meta

1. In your app dashboard on developers.facebook.com, go to WhatsApp > Configuration.
2. Under "Webhook," click "Edit."
3. Enter your callback URL (the HTTPS endpoint on your server).
4. Enter a verify token. This is a string you choose. It must match the verifyToken in your OpenClaw configuration. Use a random string: openssl rand -hex 16 will generate one.
5. Click "Verify and Save." Meta will send a GET request to your endpoint with the challenge token. If your server responds correctly, the webhook is registered.
6. After verification, subscribe to the "messages" webhook field. This tells Meta to send incoming message events to your endpoint.

If verification fails, check these common issues:

• Your server is not accessible from the public internet (firewall rules, DNS not propagated yet)
• TLS certificate is invalid, expired, or self-signed (Meta requires a valid certificate from a trusted CA)
• The verify token in Meta's dashboard does not match the one in your OpenClaw config
• Your server is not responding within the 5-second timeout

Step 5: Configure OpenClaw's WhatsApp Plugin

With your WhatsApp Cloud API credentials and webhook set up, configure OpenClaw to use the WhatsApp plugin.

OpenClaw Configuration

Add the WhatsApp plugin configuration to your openclaw.yaml file:

# openclaw.yaml
plugins:
  entries:
    whatsapp:
      enabled: true

channels:
  whatsapp:
    phoneNumberId: "YOUR_PHONE_NUMBER_ID"
    accessToken: "${WHATSAPP_ACCESS_TOKEN}"
    verifyToken: "${WHATSAPP_VERIFY_TOKEN}"
    webhookPath: "/webhook/whatsapp"
    dmPolicy: "pairing"

Important settings explained:

• phoneNumberId is the ID from your WhatsApp API Setup page (a numeric string, not your actual phone number).
• accessToken is the permanent system user token you generated. Use an environment variable (${WHATSAPP_ACCESS_TOKEN}) rather than pasting the token directly in the YAML file.
• verifyToken is the same verify token you entered in Meta's webhook configuration.
• dmPolicy: "pairing" requires users to be approved before the agent responds to them. This prevents unauthorized access. Without this, anyone who discovers your WhatsApp number can interact with your agent.

Environment Variables

Add the sensitive values to your .env file (or your secrets manager):

WHATSAPP_ACCESS_TOKEN=your_permanent_system_user_token_here
WHATSAPP_VERIFY_TOKEN=your_random_verify_token_here

Restart OpenClaw

docker compose down && docker compose up -d

# Check the logs for WhatsApp plugin initialization
docker compose logs -f openclaw | grep -i whatsapp

You should see log output indicating the WhatsApp plugin is loaded and the webhook endpoint is active. If you see errors about missing credentials or invalid tokens, double-check your environment variables.

Step 6: Message Templates

This is where WhatsApp diverges significantly from every other messaging channel. On Telegram, Slack, or Discord, your agent can send any message to any approved user at any time. WhatsApp does not work that way.

The 24-Hour Messaging Window

WhatsApp enforces a strict 24-hour messaging window:

• When a user messages your agent, a 24-hour "session" opens. During this window, your agent can respond freely with any content: text, images, documents, interactive messages, anything.
• After 24 hours of inactivity, the session closes. Your agent can no longer send free-form messages to that user.
• To re-initiate contact after the window closes, you must use a pre-approved message template. No exceptions.

This is Meta's anti-spam mechanism, and it has significant implications for AI agent use cases:

• Proactive notifications (appointment reminders, order updates, follow-ups) require message templates.
• If a customer asks a question and your agent does not respond within 24 hours, the next response must be a template.
• Templates must be submitted to Meta for review and approved before use. This review process typically takes 1-24 hours, but can take several days for templates that trigger additional scrutiny.

Creating Message Templates

Message templates are created in the WhatsApp Manager section of your Meta Business account, or via the API.

1. Go to your WhatsApp Business account in Meta Business Suite.
2. Navigate to Account Tools > Message Templates.
3. Click "Create Template."
4. Choose a category:
   • Utility: Transaction confirmations, account updates, order status. Higher delivery priority.
   • Marketing: Promotions, offers, product announcements. Lower delivery priority, subject to opt-in rules.
   • Authentication: One-time passwords and verification codes.
5. Write your template text. Use {{1}}, {{2}}, etc. as placeholders for dynamic content.

Template Examples for AI Agents

Here are templates that cover common AI agent use cases:

Follow-up template (Utility):

Hi {{1}}, this is {{2}} following up on our earlier conversation about {{3}}.

I have an update for you. Would you like to continue our conversation?

[Quick Reply: Yes, tell me more]
[Quick Reply: Not right now]

Appointment reminder (Utility):

Hi {{1}}, this is a reminder about your upcoming appointment:

Date: {{2}}
Time: {{3}}

Would you like to confirm, reschedule, or cancel?

[Quick Reply: Confirm]
[Quick Reply: Reschedule]
[Quick Reply: Cancel]

Order update (Utility):

Hi {{1}}, your order #{{2}} has been updated.

Status: {{3}}

Reply to this message if you have any questions, and I will assist you right away.

Template Approval Tips

• Keep templates clear and professional. Avoid excessive emoji, all-caps, or aggressive calls to action.
• Utility templates have higher approval rates than marketing templates.
• Include a clear opt-out mechanism ("Reply STOP to unsubscribe") in marketing templates.
• Do not include URLs that redirect through link shorteners. Meta flags these as potentially deceptive.
• Test with sample variables before submitting. Ensure the template reads naturally with real data in the placeholders.
• If a template is rejected, read the rejection reason carefully. Fix the specific issue and resubmit rather than creating a new template with minor changes.

Step 7: Media Handling

WhatsApp supports rich media, and your AI agent can both send and receive files. Here is what you need to know about media handling through the WhatsApp Cloud API.

Supported Media Types

Type	Formats	Max Size
Images	JPEG, PNG	5 MB
Documents	PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT	100 MB
Audio	AAC, MP3, OGG, AMR, MP4 audio	16 MB
Video	MP4, 3GPP	16 MB
Stickers	WebP	100 KB (static), 500 KB (animated)

Receiving Media from Users

When a user sends a file to your agent, WhatsApp delivers a media ID in the webhook payload, not the file itself. OpenClaw's WhatsApp plugin handles the download automatically:

1. User sends an image or document to your agent on WhatsApp.
2. Meta's webhook delivers the message event with a media ID.
3. OpenClaw's WhatsApp plugin uses the media ID to download the file from Meta's servers.
4. The file is passed to the agent as part of the conversation context.

For images, the agent can analyze the visual content if it is connected to a vision-capable model (Claude Sonnet 4, GPT-4o, etc.). For documents, the agent can read and summarize the content.

Sending Media to Users

Your agent can send files back to users through the WhatsApp API. The process involves uploading the media to Meta's servers first, then referencing the media ID in the message:

# Upload media to Meta's servers
curl -X POST "https://graph.facebook.com/v21.0/PHONE_NUMBER_ID/media" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -F "messaging_product=whatsapp" \
  -F "type=document" \
  -F "file=@/path/to/invoice.pdf"

# Response includes a media_id
# Use this media_id in your message

OpenClaw's WhatsApp plugin abstracts this process. When your agent generates a file (a report, an invoice, a chart), the plugin handles the upload and delivery automatically.

Group Chat Considerations

WhatsApp groups work differently from Telegram or Discord groups when it comes to AI agents.

What Works

• Your agent can be added to WhatsApp groups.
• It can receive and respond to messages in group chats.
• It can process images and documents shared in groups.

What Does Not Work (or Works Differently)

• No @mention triggers. Unlike Telegram or Discord, WhatsApp does not support @mentioning bots. Every message in the group is delivered to the webhook. Your agent needs logic to decide when to respond and when to stay silent. Without this, the agent will reply to every message in the group, which is disruptive.
• Group admin controls. Only group admins can add or remove participants, including your agent. If someone removes the agent, it cannot re-join on its own.
• No thread support. WhatsApp groups do not have threads like Slack or Discord. All messages are in a single stream. For multi-topic groups, this can create confusing interactions if the agent is responding to different conversations simultaneously.
• Privacy considerations. When your agent is in a group, it receives every message from every participant. Consider the privacy implications, especially in groups where sensitive business information is shared. Make sure your team understands the agent is present and processing messages.

Recommended Group Configuration

If you want your agent to participate in groups, configure it to respond only when explicitly addressed (e.g., messages starting with a keyword like "Agent:" or "AI:"). This prevents the agent from flooding the group with unsolicited responses.

# In your agent's system prompt or skills configuration
# Define a trigger keyword for group contexts
group_trigger: "Agent:"
group_behavior: "respond_only_when_addressed"

WhatsApp Compliance Requirements

WhatsApp's compliance requirements are more stringent than any other messaging channel. Violating these rules can result in your number being banned, your business account being suspended, or your messaging rate limits being reduced. These are not theoretical risks. Meta enforces them actively.

Opt-In Requirements

Before your agent can send messages to a user (outside of the 24-hour reply window), the user must have explicitly opted in to receive messages from your business. This means:

• Active consent required. The user must take a positive action to opt in: checking a box, sending a message first, filling out a form. Pre-checked boxes or assumed consent do not qualify.
• Clear disclosure. The user must understand what they are opting in to: the types of messages, approximate frequency, and how to opt out.
• Record keeping. You must retain records of when and how each user opted in. If Meta audits your account, you need to produce this evidence.
• Easy opt-out. Users must be able to stop receiving messages at any time. The standard approach is responding to "STOP" or "Unsubscribe."

Quality Signals

Meta monitors the quality of your WhatsApp messaging and uses it to determine your rate limits:

• Quality rating: Green (high), yellow (medium), or red (low). This is based on user feedback signals, including blocks and reports.
• If your quality rating drops to red, your messaging rate limits are reduced. If it stays red, your number can be banned.
• Tier progression: New numbers start at 250 messages/day. As you maintain good quality, Meta automatically increases your limit to 1K, then 10K, then 100K.
• Going backward: If quality drops, Meta can reduce your tier. Recovering from a tier reduction takes weeks of good behavior.

Content Restrictions

WhatsApp has specific content rules that AI agents must follow:

• No spam or bulk unsolicited messages
• No misleading content or impersonation
• No content that violates local laws (gambling promotions, regulated substances, etc.)
• Messages must clearly identify the business sending them
• Your agent must identify itself as an AI or automated system if asked. Do not instruct it to claim to be human.

GDPR and Data Protection

If you serve users in the EU or handle data of EU residents:

• You need a lawful basis for processing WhatsApp messages (typically legitimate interest or consent)
• Your privacy policy must disclose that you use automated messaging and AI
• Users have the right to request deletion of their data, including conversation history
• Data transfer considerations apply if your OpenClaw server is outside the EU (Meta processes some data in the US)

Testing Your WhatsApp Integration

Before going live, test thoroughly. WhatsApp issues are harder to debug than other channels because error messages from Meta are often vague.

Basic Test

1. Send a message from your personal WhatsApp to your agent's number.
2. If DM pairing is enabled (recommended), you will need to approve the pairing request first through your OpenClaw admin interface or paired channel.
3. After approval, send another message. The agent should respond within a few seconds.

Media Test

1. Send an image to the agent and ask it to describe what it sees.
2. Send a PDF document and ask the agent to summarize it.
3. Ask the agent to generate and send you a file (if your agent has skills that produce documents).

Template Test

1. Wait for a 24-hour session to expire (or use a separate test number that has not messaged the agent recently).
2. Trigger your agent to send a template message to the test number.
3. Verify the template renders correctly with dynamic variables filled in.
4. Reply to the template message to confirm it opens a new 24-hour session.

What to Check in Logs

# Check OpenClaw logs for WhatsApp events
docker compose logs -f openclaw | grep -i whatsapp

# Common log entries to look for:
# - "WhatsApp plugin initialized" (startup success)
# - "Webhook verified" (Meta handshake success)
# - "Message received" (incoming message processed)
# - "Message sent" (outgoing message delivered)
# - "Template sent" (template message delivered)

# Error patterns to watch for:
# - "401 Unauthorized" (invalid or expired access token)
# - "400 Bad Request" (malformed API call)
# - "130429" (rate limit exceeded)
# - "131026" (message failed to send, usually outside 24-hour window without template)

Troubleshooting Common Issues

WhatsApp integration has more failure points than other channels. Here are the issues you are most likely to encounter and how to fix them.

Webhook Verification Fails

Symptom: Meta's "Verify and Save" button returns an error.

Causes and fixes:

• SSL certificate issue. Your endpoint must use a valid TLS certificate from a trusted CA. Self-signed certificates are rejected. Use Let's Encrypt (free) via Certbot or Caddy.
• Verify token mismatch. The token in Meta's dashboard must exactly match the verifyToken in your OpenClaw config. Copy-paste to avoid typos.
• Endpoint not reachable. Check that your domain resolves to the correct IP, your firewall allows HTTPS traffic on port 443, and your reverse proxy is forwarding to OpenClaw.
• Timeout. Your server must respond to the verification GET request within 5 seconds. If OpenClaw is slow to start, the verification will fail.

Messages Not Arriving

Symptom: Users send messages but your agent never receives them.

Causes and fixes:

• Webhook not subscribed to "messages" field. After webhook verification, you must explicitly subscribe to the "messages" field in the WhatsApp configuration.
• App not connected to WhatsApp Business account. Verify the app and WhatsApp Business account are linked in Meta Business Suite.
• Number in test mode. By default, new WhatsApp API numbers can only receive messages from phone numbers added to the test list. Add your test numbers under WhatsApp > API Setup > To field, or switch to production mode.

Agent Responds to Test Number but Not Real Users

Symptom: The agent works in testing but real users get no response.

Causes and fixes:

• Still in test mode. Your WhatsApp Business API might still be in development/test mode. Check your app's status in the Meta Developer dashboard and switch to live mode.
• DM pairing blocking unknown users. If dmPolicy: "pairing" is enabled (recommended), new users need to be approved. Check your pairing requests queue.
• Rate limit reached. New numbers start at 250 messages/day. If you have exceeded this, messages will be queued or dropped.

Template Messages Failing

Symptom: Template messages return errors or are not delivered.

Causes and fixes:

• Template not approved. Check the template status in WhatsApp Manager. Only approved templates can be sent.
• Wrong number of variables. If your template has {{1}} and {{2}} placeholders, you must provide exactly two variable values. Too few or too many will cause a 400 error.
• Template paused or disabled. Meta can pause templates that receive poor quality feedback. Check the template quality rating.
• User has not opted in. For marketing templates, the user must have opted in to receive marketing messages from your business.

Error Code Reference

Code	Meaning	Fix
130429	Rate limit exceeded	Wait and retry, or request a tier upgrade
131026	Message outside session window	Use an approved template to re-open the conversation
131047	Re-engagement message needed	Session expired, send a template first
132000	Template parameter count mismatch	Check that you are sending the correct number of template variables
132012	Template not found	Verify template name, language, and approval status
133010	Phone number not registered	Re-register the number in WhatsApp Manager
368	Account temporarily blocked	Quality rating too low. Review and improve message quality

WhatsApp vs. Telegram for AI Agents

If you are deciding between WhatsApp and Telegram (or using both), here is how they compare specifically for AI agent use cases:

Feature	WhatsApp	Telegram
Setup time	Days to weeks (verification)	5 minutes
User base	2B+ monthly active users	950M+ monthly active users
Bot creation	Business verification required	Talk to BotFather, done
Messaging rules	24-hour window + templates	No restrictions
Cost	Per-conversation pricing	Free
Group support	Limited (no @mentions)	Full (commands, @mentions)
File size limits	5-100 MB depending on type	Up to 2 GB
Business presence	Dominant globally	Strong in tech/crypto communities
Compliance burden	High (opt-in, templates, quality)	Low
Proactive messaging	Templates only after 24h	Anytime to any subscriber

When to use WhatsApp: Your customers are already on WhatsApp (especially in LATAM, South/Southeast Asia, Europe, Africa), you need professional business messaging with verified profiles, or your use case involves customer support, order updates, or appointment management where WhatsApp's rich templates add value.

When to use Telegram: You need fast setup, your audience is tech-forward, you need unrestricted messaging (no templates, no 24-hour windows), or you are building internal tools where you control the user base. See our Telegram setup guide for that channel.

When to use both: Most businesses benefit from connecting multiple channels. Your AI agent can handle conversations on WhatsApp, Telegram, Slack, Discord, and email simultaneously, each channel reaching a different audience segment.

Skip the WhatsApp Headaches: ClawTrust

If you have read through this guide, you have a sense of what WhatsApp integration involves: Meta Business verification (days to weeks), Cloud API setup, permanent token generation, webhook configuration, SSL certificates, message template creation and approval, compliance requirements, rate limit management, and ongoing quality monitoring.

That is a lot of moving parts. And if any single piece breaks (an expired token, a dropped quality rating, a webhook misconfiguration), your agent goes silent on WhatsApp with no fallback.

ClawTrust eliminates the entire setup process. WhatsApp is available on all tiers (Starter, Pro, and Enterprise), and here is what is different:

• Pre-configured WhatsApp plugin. The OpenClaw WhatsApp plugin is installed, configured, and tested before your agent goes live. No YAML editing, no environment variables, no webhook debugging.
• Dashboard channel connection. Connect WhatsApp (and Telegram, Slack, Discord, and 10+ other channels) through a visual dashboard. Enter your credentials, click connect, done.
• Webhook infrastructure handled. Your agent runs behind a secure, encrypted tunnel with valid TLS certificates. No reverse proxy setup, no Let's Encrypt renewal, no firewall rules. The webhook endpoint is accessible and properly secured from the moment your agent is provisioned.
• Security included. DM pairing, token authentication, loopback gateway binding, container sandboxing, and credential isolation are all configured by default. Your WhatsApp access token is stored in an encrypted vault, not on the agent's server. See our security architecture for details.
• Multi-channel from day one. Most teams that set up WhatsApp also want Telegram, Slack, and email. On ClawTrust, all channels are configured the same way: through the dashboard. No separate setup process per channel.
• AI budget controls. WhatsApp API conversations have their own costs, and AI model usage adds more. ClawTrust includes per-agent AI budgets ($5-$30/mo depending on your plan) with automatic caps. No surprise bills from runaway agent loops.

You still need to handle Meta Business verification and WhatsApp Business account setup yourself (Meta requires the business owner to complete these steps). But everything after that, the entire technical integration, is handled by ClawTrust.

Plans start at $79/mo with a 5-day free trial. All plans include WhatsApp support, plus every other messaging channel OpenClaw supports.

Frequently Asked Questions

How long does it take to set up WhatsApp with OpenClaw?

The technical integration (API credentials, webhook, OpenClaw config) takes 1-2 hours if everything goes smoothly. However, Meta Business verification can take 2 days to 6 weeks depending on your documentation. The total timeline from starting to having a working WhatsApp agent is typically 1-3 weeks, with most of that time spent waiting for Meta.

Can I use WhatsApp without Meta Business verification?

You can start testing with the Cloud API before full verification, but your number will be in test mode (limited to pre-approved phone numbers only). Full verification is required before you can message real users. There is no shortcut around this requirement.

What happens when the 24-hour messaging window closes?

Your agent can no longer send free-form messages to that user. To re-initiate contact, you must send a pre-approved message template. If the user replies to the template, a new 24-hour session opens and free-form messaging resumes. This is a Meta requirement, not an OpenClaw limitation.

How much does WhatsApp Business API cost?

The Cloud API itself is free. Conversations are billed per 24-hour session: the first 1,000 service conversations per month are free. After that, pricing varies by country (roughly $0.005-$0.08 per conversation). Marketing conversations cost more than utility conversations. Check Meta's current pricing for your specific markets.

Can my agent send images, PDFs, and other files on WhatsApp?

Yes. WhatsApp supports images (JPEG, PNG up to 5 MB), documents (PDF, DOC, XLS up to 100 MB), audio (MP3, OGG up to 16 MB), and video (MP4 up to 16 MB). Your agent can both receive and send all supported media types. OpenClaw's WhatsApp plugin handles the upload and delivery process.

Is WhatsApp Business API GDPR compliant?

Meta provides a Data Processing Agreement (DPA) for WhatsApp Business API users, which covers some GDPR requirements. However, full compliance depends on your overall data handling practices: having a privacy policy that discloses AI usage, honoring data deletion requests, and managing data transfer considerations if your server is outside the EU. Consult your legal team for a complete assessment.

Can I use the same WhatsApp number for the regular app and the Business API?

No. Once a phone number is registered with the WhatsApp Business API, it cannot simultaneously be used with the regular WhatsApp app or WhatsApp Business app. Use a dedicated number for your AI agent.

What is the maximum number of messages my agent can send per day?

New numbers start at 250 messages per 24 hours. As you maintain good quality ratings, Meta automatically upgrades your tier: 1,000, then 10,000, then 100,000 messages per 24 hours. Tier progression depends on consistent message quality and user engagement, not just volume. If quality drops, Meta can reduce your tier.

---

Chris DiYanni is the founder of ClawTrust. Previously at Palo Alto Networks, SentinelOne, and PagerDuty. He builds security infrastructure so businesses can trust their AI agents with real work.