ShipClawShipClaw
Channel · WhatsApp

OpenClaw on WhatsApp — Managed Bot Hosting

ShipClaw routes to WhatsApp via OpenClaw’s WhatsApp Business adapter — you bring Meta-approved Business API access (directly or through a BSP), we run the managed Claude agent that responds on the other end. WhatsApp’s policy surface (24-hour window, templates, opt-in) applies as Meta defines it.

$15 starter credit pack.~$0.01 per credit · No ShipClaw monthly fee · Meta/BSP fees separate
Bring access

WhatsApp Business API

You hold the Meta or BSP relationship — phone number, verified business, message templates. ShipClaw doesn't resell WhatsApp access.

We host

Managed OpenClaw + Claude

The agent runtime, sandbox, stealth browser, and Anthropic billing live on our pool nodes. You never operate the OpenClaw process.

Honest scope

Telegram leads, WhatsApp follows

Telegram has the deepest integration; WhatsApp is for users who already operate inside the Business API and want Claude wired in.

What you get on the WhatsApp channel

  • Adapter via OpenClaw

    WhatsApp Business webhooks consumed by the OpenClaw upstream adapter. Inbound messages route to your agent's runtime on the pool node.

  • 24-hour window respected

    Within the WhatsApp customer-service window, replies go out as plain messages. Outside it, you'll need a pre-approved Meta template.

  • Managed Anthropic Claude

    Same Tier 4 Anthropic relationship. Credits debit per call regardless of channel — Telegram, Discord, or WhatsApp share the same balance.

  • Sandbox isolation

    Your WhatsApp bot's process namespace is isolated from other tenants on the pool node. Bot tokens encrypted at rest.

  • Stealth browser actions

    Ask the bot to fetch live data — it can browse, search, and act on the web through the bundled stealth engine, then reply over WhatsApp.

WhatsApp FAQ

  • Do I need a WhatsApp Business API account?

    Yes. WhatsApp does not allow user-account bots; you need a WhatsApp Business API access point — either through Meta directly or through a Business Solution Provider (BSP) like Twilio, 360dialog, or MessageBird. ShipClaw doesn't sell that access; you bring it. Meta's verification can take days to weeks, so plan ahead.

  • What does ShipClaw provide vs. what do I bring?

    We provide the managed OpenClaw runtime, the Anthropic Claude relationship, the sandbox, the stealth browser, the credit meter, and the adapter that consumes WhatsApp Business webhooks. You provide the Meta-approved phone number, the BSP credentials (or Cloud API token), and any pre-approved message templates WhatsApp requires for outbound messaging.

  • Will it respect WhatsApp's 24-hour customer service window?

    Yes. Inside the 24-hour window after a user messages your bot, OpenClaw can reply freely. Outside the window, WhatsApp requires a pre-approved template message — that's a Meta policy, not a ShipClaw choice. The adapter respects it; you have to register templates with Meta yourself.

  • Is WhatsApp parity with Telegram?

    No. Telegram is the most polished channel and gets feature work first; WhatsApp routes through the OpenClaw adapter and is best for users who already have a WhatsApp Business presence and want a Claude-powered agent inside it. If WhatsApp is the only channel you care about, ping us before signing up so we can confirm fit.

Other channels: Telegram hosting · Discord hosting.

Your OpenClaw Instance.
Live in Telegram. Under 60 Seconds.

Every instance comes with a stealth browser engine, CAPTCHA bypass, and autonomous web actions built in. Your agent doesn't just talk — it browses, searches, and gets things done.

Get Started

No credit card required. No servers to manage. Ever.