OpenClaw WhatsApp Setup With a Dedicated Number

OpenClaw can run on your personal WhatsApp, but its own documentation recommends giving the bot a separate number, and its Signal channel says the same more firmly. The number you pick decides how long the setup lasts: WhatsApp checks the number again when the session moves, so the bot needs a number that stays yours, not one borrowed for a single code. In practice that means a dedicated monthly number, registered once in the WhatsApp Business app and linked to OpenClaw by QR code.

Why OpenClaw wants its own WhatsApp number

The OpenClaw WhatsApp docs list two deployment patterns and mark one as recommended: a dedicated number, for three reasons they give directly.

• A separate WhatsApp identity for the bot. Messages to the bot and messages to you never share an inbox.
• Clearer access rules. allowFrom lists the numbers allowed to talk to the bot, and your personal number becomes one entry on it rather than the account itself.
• No self-chat confusion. On your own number, OpenClaw has to run in self-chat mode and filter its own messages. Some features need two numbers anyway: the experimental call action cannot call the number it runs on.

The personal-number mode exists and works. It is the fallback, not the design target.

Which number type holds up

WhatsApp sends its registration code by SMS, with a voice call as fallback, and asks for a code again when the account is reinstalled or moves to a new device. Account recovery goes through the same number. That rules out anything temporary.

A dedicated number on VoidMob is a non-VoIP carrier number that receives SMS from any sender for as long as you keep it, with auto-renew so it never lapses under the bot. It is offered per country, so the bot can have a number in the country its contacts expect. The WhatsApp verification page covers the one-time and rental tiers for accounts that are not meant to last.

Set up OpenClaw on the new number

WhatsApp registration happens in an official WhatsApp app, then OpenClaw joins as a linked device. The WhatsApp Business app runs alongside WhatsApp on the same phone as long as each uses its own number, so a second handset is optional.

1. Get the number. Buy a dedicated monthly number in the country you want and switch on auto-renew.
2. Register it. Install WhatsApp Business, enter the new number and choose SMS when it offers a code. The code shows up in the number's messages in the VoidMob dashboard.
3. Set who may talk to the bot. In the OpenClaw config, put your personal number on the allowlist:

1{2  channels: {3    whatsapp: {4      dmPolicy: "allowlist",5      allowFrom: ["+15551234567"],6    },7  },8}

4. Link OpenClaw. On the gateway host, start the QR login, then scan it from WhatsApp Business under Linked devices:

1openclaw channels login --channel whatsapp2openclaw gateway

The QR expires quickly. On a headless VPS, show it somewhere you can scan right away rather than sending a screenshot.

5. Say hello. Message the bot's number from your personal WhatsApp. With dmPolicy: "pairing" instead of an allowlist, approve the first request with openclaw pairing approve whatsapp <CODE>.

The risk to know before you link it

OpenClaw's WhatsApp channel connects through WhatsApp Web using Baileys, an open-source library, not one of WhatsApp's own apps. WhatsApp's help center says that linking an account to unofficial apps breaks its terms and can lead to a temporary or permanent ban. Running the bot on its own number means that risk sits on the bot's number and its chats, not on your personal account and contacts.

Signal: the setup without a phone

Signal is the simpler route if you are open to it. The OpenClaw Signal docs are blunt about the number: on your personal account the bot ignores your own messages, so "I text the bot and it replies" needs a separate bot number. Registering a number with signal-cli can also sign out the Signal app already using it.

With a dedicated number the whole registration runs on the server, no handset involved, using signal-cli:

1signal-cli -a +<BOT_NUMBER> register2signal-cli -a +<BOT_NUMBER> register --captcha '<SIGNALCAPTCHA_URL>'3signal-cli -a +<BOT_NUMBER> verify <CODE>4signal-cli -a +<BOT_NUMBER> setPin <PIN>

The second line is only needed when Signal asks for a captcha: you complete it in a browser at Signal's captcha page and paste the link it gives you. The code for verify arrives on the dedicated number. setPin turns on Registration Lock, so nobody else can register the bot's number without the PIN. Then put the number in channels.signal.account and check the channel with openclaw channels status --probe.

Let OpenClaw fetch the number itself

With the VoidMob MCP server or skill installed, OpenClaw can quote and buy the dedicated number for you and read the registration code from it, so the only steps left for you are the captcha and the QR scan. The OpenClaw setup guide has the install lines.