Lede: If a WhatsApp number is greyed out in Zoho CRM's "Add New Number" and outbound messages fail with crm.bm.msg.failed.undefined, the issue often shows as inbound working while replies and templates never reach Meta; our team outlines what to check and what to escalate next. Beam Help — independent expert support for Zoho, not official Zoho support.[1]
Why this matters
When inbound WhatsApp messages arrive but every outbound attempt fails, business messaging stops and sales or support queues back up, harming customer response times and revenue.[1] A registered number that cannot be re-selected or is greyed out prevents you from switching numbers or restoring service from the Zoho CRM side, prolonging downtime.[1]
Step-by-step
- Step 1. Confirm inbound messages are still arriving in the CRM Messages module so you know the integration is partially working and the problem is outbound-only.[1]
- Step 2. In CRM Business Messaging, check whether the number shows as connected on your WhatsApp Business Account; document its displayed state (CONNECTED or otherwise).[1]
- Step 3. Verify the same phone number’s status on Meta (Cloud API) and note whether account health shows cansendmessage as AVAILABLE; capture screenshots for support.[1]
- Step 4. Reproduce an outbound message from CRM and record the exact error shown (crm.bm.msg.failed.undefined) and the timestamp, so support can correlate CRM logs with Meta logs.[1]
- Step 5. Attempt to add the other registered number from "Add New Number" and record that it is greyed out and not selectable; note that you confirmed the number is not in use by any other app or Zoho service.[1]
- Step 6. Open or update a support case with Zoho including: screenshots of CRM Messages, CRM Business Messaging, Meta Cloud API account health, the greyed-out Add New Number state, timestamps, and the crm.bm.msg.failed.undefined replies.[1]
- Step 7. If you already have open tickets, include their IDs and request escalation; the community thread shows multiple tickets and agent handoffs before developer escalation occurs.[1]
- Step 8. While waiting on support, avoid creating new templates in CRM that might be rejected or stall; template issues can further complicate number health and message delivery.[2]
Common pitfalls
- Submitting partial evidence: cases that lack screenshots of Meta account health and CRM outbound errors slow developer triage; include both sides in your case.[1]
- Creating new templates during an outage: sending or creating templates from CRM while the outbound channel is failing can show as "Failed" and may obscure root-cause signals.[1][2]
What to check
- Confirm inbound messages still arrive in CRM Messages and note timestamps for failed outbound attempts.[1]
- Verify the number’s CONNECTED state in CRM Business Messaging and cansendmessage = AVAILABLE on Meta’s Cloud API.[1]
- Ensure your support case includes screenshots, timestamps, and any existing ticket numbers so developers can correlate CRM and Meta logs quickly.[1]