Customers with a WhatsApp username (no phone number)
WhatsApp lets people use a username instead of showing their phone number.
- Plan
- Depends on your plan · Which plan do I need?
- Who can use this
- Account owner, Manager
WhatsApp lets people use a username instead of showing their phone number.
WhatsApp lets people use a username instead of showing their phone number. When such a customer messages you, Meta does not share their number: the chat has a WhatsApp user ID instead (for example KE.1471…). Everything in the inbox and your bot works, but anything that needs the phone number gets an empty value for them.
STAT_PHONE and STAT_WHATSAPP_USER_ID (see Variables and custom fields).A. Ask for the number when it's missing (recommended)
STAT_PHONE Is setThe item's edge (true: the phone is there) goes on to your webhook or lookup.
The block only sends the request; the bot moves on without waiting. When the customer taps the button, the number is saved on the contact and STAT_PHONE is filled from then on.
B. Use the WhatsApp user ID as the identifier
{{STAT_WHATSAPP_USER_ID}} as well as {{STAT_PHONE}}. For username customers the user ID is their only stable identifier; for everyone else it is empty. Your own system can then match customers by either value.{{STAT_PHONE}} without quotes, an empty value makes the body invalid JSON: always quote variables in JSON bodies ("{{STAT_PHONE}}").Do it with Copilot
| What you see | Why | What to do |
|---|---|---|
| A webhook keyed on phone fails (400/404) for some customers only | Those customers use a WhatsApp username, so the phone is empty. | Add the Condition + Request Contact step (A), or send STAT_WHATSAPP_USER_ID (B). |
| "The webhook body is not valid JSON… an empty variable in an unquoted place" | {{STAT_PHONE}} was empty and not in quotes. | Put quotes around variables in the JSON body. |
| The contact has no phone in the inbox | Username customer. | Ask with Request Contact; the number appears after they share it. |