let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: explain why Twilio is unsupported

Browse Source
This commit is contained in:
Peter Steinberger
2026-01-07 16:54:37 +01:00
parent 573fe74a9c
commit c1036cace7
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/providers/whatsapp.md
View File

@@ -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 <id>` (`<id>` = `accountId`).