← ClaudeAtlas

whatsapp-number-onboardinglisted

Load when connecting a client's or your own phone number to the WhatsApp Business Platform (Cloud API) inside Meta Business, or when a connected number "is green but nothing arrives", messages arrive twice, templates fail, or Meta blocks a step. Gives the safe order (portfolio → WhatsApp account → number → app → token → webhook → register with PIN → test), the read-back checks after each step, and a troubleshooting table of real blocks with their official error codes and fixes, each marked as official or field-tested. Triggers on "connect WhatsApp to my app", "onboard client number", "WhatsApp Cloud API setup", "number already registered", "No se pudo asignar el socio", "display name in review", "131042", "133010", "133016", "messages not arriving", "conectar el WhatsApp del cliente", "dar de alta el número", "el bot no recibe mensajes", "Meta no me deja". Not an API reference for sending messages or templates (use a WhatsApp Cloud API reference skill) and not sales copy for the bot (use whatsapp-closer).
RabbitDesigns22/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill RabbitDesigns22/claude-skills
# WhatsApp number onboarding (Meta Cloud API) Connecting a number looks like 10 clicks. In practice it fails on the order of steps, on which portfolio owns what, and on Meta screens that say "connected" when nothing is delivered. This skill is the safe order plus the blocks that actually happened, with their fixes. **Confidence tags used below:** `[official]` = stated on developers.facebook.com (URL in the table); `[field]` = happened in real onboardings and the fix was confirmed live; `[unconfirmed]` = seen, cause or fix never proven. Never present `[field]` or `[unconfirmed]` as Meta policy. ## Words: never mix these four - **Business portfolio** (Business Manager): the company in Meta. - **WhatsApp Business Account (WABA)**: lives inside a portfolio. In the UI, use the **Messaging account** ID, not the "WhatsApp account/presence" ID (the latter returns "This API is not supported") `[field]`. - **Phone number**: lives inside a WABA. Its **Phone number ID** is not the phone number. - **Meta app**: lives in a developer account and is linked to a portfolio; it holds the token, app secret and webhook. When you state a limit, say which of the four it is about. ## Limits that decide the plan `[official]` - A new portfolio can register **2 phone numbers**; the cap rises to **20** when the business is verified or reaches the 2,000 messaging limit. - Messaging limits are **per portfolio, shared by all its numbers**: 250 → 2,000 → 10,000 → 100,000 → unlimited. One busy number ca