WhatsApp "Message Type Not Supported": Why Some Customer Messages Don't Reach Your API Inbox
A customer says they sent you a poll, a photo or an edited message, and your team sees only "not supported". Here is which WhatsApp messages the Cloud API does not deliver, what the error codes mean, and a simple routine for your agents.
MonoChat Team Updated: 6 min read
On this page
A customer writes to a shop on WhatsApp, then sends a poll to choose between two colours. Another one edits her last message to correct the delivery address. A third one sends a photo of a damaged parcel as view-once media. On their phones, everything looks normal. In the business’s team inbox, the agent sees something else: a message without content, marked as not supported.
This is not a bug in your inbox. Some WhatsApp features simply do not travel through Meta’s Cloud API, the API every business messaging platform uses. This guide explains which messages are affected, what the error codes mean, what MonoChat shows your team, and a short routine so these messages never cost you a customer.
What happens when a customer sends an unsupported message
When a WhatsApp user sends a message type that the Cloud API does not support, Meta still notifies the business, but without the content. In Meta’s words, the unsupported message webhook is triggered when “a WhatsApp user sends a message type not supported by Cloud API”.
The notification carries:
- the type
unsupported, with the actual type that could not be delivered (for examplepoll_creationoredit); - an error with the code 131051, the title “Message type unknown” and a detail such as “Message type is currently not supported.”;
- the sender, the message ID and the time.
So your system knows that the customer sent something and what kind of thing it was, but not what it said.
Which message types are affected
Meta’s reference lists the values the unsupported.type field can take. Among them:
| Type in Meta’s reference | What the customer did |
|---|---|
poll_creation, poll_update | Created a poll, or voted in one |
edit | Edited a message they had already sent |
pin, keep_in_chat | Pinned a message, or kept a disappearing message in the chat |
group_invite | Sent a WhatsApp group invite |
link_preview | Sent a link shown with a preview |
media_placeholder | Sent media that WhatsApp delivered as a placeholder |
Meta’s list also includes values such as button, image, location, order, product and reaction, which are normally supported: they appear on the list for the cases where WhatsApp could not deliver that particular message through the API. The list changes as WhatsApp adds features, so read it as a guide, not as a fixed rule.
MonoChat’s help center adds a common example from real conversations: view-once media sent by a customer also reaches the inbox without its content.
A second code: 131060
Meta documents one more case. The code 131060, “The message is currently unavailable”, usually appears on a user’s first message to a business whose number was onboarded from the WhatsApp Business app, which is the case with coexistence. If a first message from a new customer arrives empty, this is the likely reason.
What MonoChat shows your team
Since MonoChat 3.8.43, released on 2 November 2026, a message that WhatsApp delivers without its content shows in the chat as:
This message type is not supported. followed by WhatsApp’s own error title and details
Behind it, MonoChat stores the error code and the real type, such as a poll or view-once media, so you can see what the customer tried to send. Conversation exports show readable text for these messages. The MonoChat mobile app, from version 3.4.0, shows the same explanation under “This message type is unsupported.”
Before 3.8.43, the same messages showed as “This message cannot be displayed at the moment.” with no reason, which left agents guessing.
A routine for your agents
The fix is not technical. It is a short, friendly habit.
1. Read the type. The explanation under the message tells the agent what the customer tried to send. A poll needs a different answer than a damaged-parcel photo.
2. Answer within the customer service window. The customer has just written, so you are inside WhatsApp’s 24-hour window and can reply with a normal message.
3. Ask for the same information in a supported form. Keep a saved reply ready for each common case:
| Customer sent | Saved reply |
|---|---|
| A poll | ”Thanks! Polls don’t reach our support inbox. Could you type your choice here, for example ‘blue, size M’?” |
| An edited message | ”We received your first message, but edits don’t reach us. Could you send the corrected details as a new message?” |
| View-once photo | ”Thanks for the photo! View-once photos don’t reach our team. Could you send it again as a normal photo, so we can keep it with your order?” |
| Something we can’t see | ”Sorry, your last message didn’t reach us. Could you send it again as text, a photo or a document?” |
In MonoChat, saved replies are a click away in the message box, so the agent answers in seconds. Our saved replies guide shows how to set them up.
4. Don’t blame the customer. From their side, the message went through. A reply such as “your message didn’t reach us” works better than “you sent an unsupported message”.
5. Look at the pattern. If many customers send polls or view-once photos to your number, tell them up front, for example in your welcome message: “For damage claims, please send normal photos, not view-once.”
Edits deserve special care
An edited message is the riskiest case for orders and bookings. The customer corrects an address, a date or a size, and believes the business saw the correction. Your inbox still shows the original message.
For anything that changes an order, ask customers to confirm the final details in a new message, and repeat the details back before you act:
Just to confirm: delivery to 14 Harbour Road, flat 3B, on Friday between 2 and 6 pm. Is that right? [Yes, correct] [Change it]
A confirmation with buttons turns an invisible edit into a clear answer.
What about the other channels?
The same idea applies across channels: a channel can deliver a message without its content when its own API does not support that type. MonoChat’s help center describes the rule generally: such messages show as “This message type is not supported.” followed by the channel’s own explanation when it gives one. In a unified team inbox, the routine above works the same whether the customer wrote on WhatsApp, Instagram or Messenger.
Checklist
- Agents know what “This message type is not supported.” means, and where to read the reason.
- Saved replies exist for polls, edits, view-once photos and unknown messages.
- Order and booking changes are confirmed in a new message, with buttons.
- Your welcome message mentions normal photos if you rely on them.
- New coexistence numbers: first messages that arrive empty are followed up.
Start with a clearer inbox
MonoChat is business messaging software and an official Meta Business Partner. It connects your own WhatsApp number to Meta’s Cloud API, shows your team why a message could not be delivered, and gives them saved replies, flows and a shared inbox to answer every customer. The help article on message types covers the rest.
You can start free at app.monochat.ai.
Sources
- Meta for Developers: Unsupported messages webhook reference (opened 3 Nov 2026)
- MonoChat help center: Message types, messages that cannot be shown (opened 3 Nov 2026)
- MonoChat release notes 3.8.43 (opened 3 Nov 2026)
- MonoChat mobile app release notes 3.4.0 (opened 3 Nov 2026)
Put this into practice with MonoChat