What you see
One number sends a template message to another number. The sender shows the message as delivered. But the receiving side never shows the text: no thread, no message in the inbox. In the receiver's webhook log there is a single warning instead, error 131051, "Message type unknown", with the message type unsupported and no content.
We hit exactly this when an automation sent a task alert from one AssistantLabs-connected number to our own support number.
Why it happens
Both numbers are connected to the WhatsApp Business API. When the API messages a number that is already in use with the API, WhatsApp does not deliver the message as normal text to that number's owner. It sends the owner an unsupported notification instead.
- The sender sees success. WhatsApp did accept and deliver something, so the status webhook says delivered.
- The receiver sees a stub. It gets an event with type
unsupportedand error code 131051, but not the words of the template. - Most systems drop it. With no content there is nothing to save, so usually no conversation is created at all.
What is documented, and what is not
Meta does not publish a page that says "templates between two business API numbers don't work." So here is exactly what we know, and where it comes from:
- Meta, documented: its unsupported-messages webhook reference lists "you use the API to message a number that is already in use with the API" as a case where the owner of the recipient number gets an
unsupportedwebhook. - Other platforms, documented: providers such as LeadConnector and HighLevel state in their help pages that API-to-API messaging between two business accounts is a Meta limitation, not a bug in their products.
- Our own test, observed: the sender showed delivered; the receiver's webhook carried type
unsupported, code 131051, and no text.
What we could not confirm: Whether a receiving number that runs only on the WhatsApp Business app (no API) would show the message normally. Other guides suggest it would, but that is not in Meta's documentation, so test it before you rely on it.
The same error code also covers a customer sending a type of message the API cannot represent, such as a poll. See error 131060 for another message that arrives empty.
What to do instead
Start from who or what needs to receive the message. The answer decides the route:
- A person needs to see it. Send the template to their own WhatsApp number, one that is not connected to the API. People receive templates normally, on a phone or on WhatsApp Web.
- A system needs to receive it. Skip WhatsApp for that hop. Send the data to the system's own API or webhook, or by email if it reads email. Machines talk to each other better than through a chat app.
- You are testing. Use a regular phone as the receiver. A test between two API numbers will show delivered and prove nothing.
Rule of thumb: If both ends of a WhatsApp message are API numbers, redesign the route. If you need a person to be alerted, aim at their phone. If you need a system to react, aim at the system.
