From c1036cace7ce0236abc26935535588bc9599a2a7 Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Wed, 7 Jan 2026 16:54:37 +0100 Subject: [PATCH] docs: explain why Twilio is unsupported --- docs/providers/whatsapp.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/providers/whatsapp.md b/docs/providers/whatsapp.md index c8f3dcd8b..42dfb0572 100644 --- a/docs/providers/whatsapp.md +++ b/docs/providers/whatsapp.md @@ -5,7 +5,7 @@ read_when: --- # WhatsApp (web provider) -Updated: 2025-12-23 +Updated: 2026-01-07 Status: WhatsApp Web via Baileys only. Gateway owns the session(s). @@ -35,6 +35,13 @@ WhatsApp requires a real mobile number for verification. VoIP and virtual number **WhatsApp Business:** You can use WhatsApp Business on the same phone with a different number. This is a great option if you want to keep your personal WhatsApp separate — just install WhatsApp Business and register it with Clawdbot's dedicated number. +## Why Not Twilio? +- Early Clawdbot builds supported Twilio’s WhatsApp Business integration. +- WhatsApp Business numbers are a poor fit for a personal assistant. +- Meta enforces a 24‑hour reply window; if you haven’t responded in the last 24 hours, the business number can’t initiate new messages. +- High-volume or “chatty” usage triggers aggressive blocking, because business accounts aren’t meant to send dozens of personal assistant messages. +- Result: unreliable delivery and frequent blocks, so support was removed. + ## Login + credentials - Login command: `clawdbot login` (QR via Linked Devices). - Multi-account login: `clawdbot login --account ` (`` = `accountId`).