You open a WhatsApp conversation in Bedones and see “Unsupported message” where a customer’s message should be. The conversation is there, but the content is missing. That label means Meta told Bedones a message arrived without providing content Bedones can display. It does not mean the AI read the message and chose to ignore it. The safest next step is to ask the customer what they sent, then investigate whether the cause is a message format or the way your number is connected.
What the label actually means
WhatsApp Cloud API delivers incoming messages to connected tools through webhooks. For an unsupported message, the webhook can contain the sender, message ID and timestamp, but no readable text or downloadable media. Meta’s webhook reference documents error 131051, “Unsupported message type,” for this situation. Bedones keeps a visible marker in the conversation so your team knows something arrived without inventing its contents.
The marker cannot be opened to reveal the missing message later. If Meta did not deliver the text or media to the API, Bedones has no copy to recover. Seeing the content in the WhatsApp Business app on a phone does not grant a connected platform access to that phone’s local conversation data.
Why it happens, including coexistence
One cause is the format itself. A customer may send a poll, a view-once item, an ephemeral message, or a newer WhatsApp format that Cloud API cannot pass through in a usable form. These cases can occur even when your number already uses Cloud API alone.
Coexistence is another source of gaps. It lets the same number run in the WhatsApp Business mobile app and Cloud API during a transition. That is convenient when staff still need the phone, but the mobile app and the connected platform do not always receive equivalent content. For example, some shared posts or ads, edited messages and other app-side interactions may be visible on the phone while the API delivers only an unsupported marker. The marker by itself does not prove which cause applies: check the message type and any Meta error recorded with it.
What to do when a customer sends one
First, open the conversation and check whether the customer sent a follow-up that explains the request. If the content is still missing, ask them to resend it as ordinary text, a standard photo or a document. For a product request, ask for the product name or reference. Do not claim to have seen the original message or guess which item they meant.
If the problem repeats, note when it happens and what the customer attempted to send. Your team can then compare those examples with the errors supplied by Meta and determine whether the pattern points to a specific format or to coexistence. Treat an unsupported marker as a case for human review: Bedones records it, but the marker alone does not give the AI enough content to answer and does not automatically create a human-attention notification.
Why move fully to WhatsApp Cloud API
If your number is in coexistence and these gaps affect customer conversations, move it to Cloud API-only operation. A single operational inbox removes the parallel mobile-app path and reduces the missing-message cases linked to coexistence. Your team can then handle WhatsApp conversations in Bedones, with the AI answering the routine requests it can understand.
This move is not a cure for every “Unsupported message.” A format Meta does not expose through Cloud API will remain unavailable after migration, and previously missing content will not reappear. Keep the resend procedure above for those cases.
The mobile app has real advantages, especially the immediate sense of control from checking a phone and stepping into a conversation yourself. You can preserve that human oversight with selective notifications in Bedones: configure notifications for the team members and WhatsApp account that should receive requests needing attention. When the agent cannot answer confidently and asks for a human decision, an enabled notification can point the community manager to that conversation. Device alerts also require the relevant notification permission. With those preferences set, managers can focus on the conversations that need them instead of watching every routine exchange; they should still review unsupported markers in the inbox because those markers do not trigger an alert on their own.
Prepare the switch carefully
Before leaving the mobile app, save any contacts or conversation information stored only on the phone, confirm access to your Meta business portfolio and number, and agree on who will answer from Bedones. Coordinate the reconnection with the Bedones team and keep access to the number for verification. Deleting the mobile account can erase local history and backups, so review the migration steps before taking action.
After the switch, test incoming and outgoing text, images and documents, then check that the intended team members receive attention alerts. Confirm that everyone knows where to find conversations, how to take over from the AI, and how to ask a customer to resend an unsupported item. That gives community managers a clear intervention path while the agent handles ordinary messages.