WhatsApp: Unsupported Message Type

Troubleshooting Guide: WhatsApp Unsupported Message Type

This guide explains why some messages appear as "unsupported" in your CRM, details the error code 131051, and outlines which message types are and are not supported.

What is an Unsupported Message Type?

When using the WhatsApp integration, you may encounter messages that the system labels as "unsupported." This occurs because the underlying WhatsApp Business Platform, which powers the CRM's messaging, has a specific set of message types it can process. The consumer WhatsApp app allows users to send items like stickers, polls, and voice notes, but the Business Platform API does not support all of these formats. When a contact sends an unsupported message type, the CRM receives a notification but cannot display the actual content. This is a limitation set by the platform provider, Meta, and is not a bug within the CRM itself.

Understanding Error Code 131051

Error code 131051 is assigned by Meta's systems to indicate an unsupported message type. This error can appear in two primary scenarios:

  • Inbound Messages: A contact sends a message type that the API cannot process (e.g., a poll or GIF). The CRM receives a notification with an "unsupported" type and this error code instead of the message content.
  • Outbound Messages: Your attempt to send a message fails because the format or type used is not supported by the API, resulting in the message not being delivered and the error being returned.

Supported Message Types

The following message types are fully supported for sending and receiving through the CRM's WhatsApp integration:

  • Text: Standard text messages, including emojis and web links.
  • Image: JPEG and PNG files, with a maximum size of 5MB.
  • Video: MP4 and 3GPP files, with a maximum size of 16MB.
  • Audio: Files in AAC, MP4, MPEG, AMR, and OGG formats, up to 16MB.
  • Document: Files such as PDFs, Word documents, Excel spreadsheets, and PowerPoint presentations, with a maximum size of 100MB.
  • Sticker: Static WebP format for sending; animated WebP for receiving.
  • Location: Sharing or receiving map coordinates.
  • Template Messages: Pre-approved marketing, utility, and authentication templates for outbound use.
  • Interactive Messages: List messages, reply buttons, and call-to-action URL buttons.
  • Contacts: Structured contact cards sent via the API.
  • Reaction: Emoji reactions to messages.

Unsupported Message Types

The following message types are not supported by the WhatsApp Business Platform. If a contact sends one of these, it will appear as an unsupported message, and you will not be able to view its content.

  • Polls
  • Ephemeral (disappearing) messages
  • Deleted messages
  • Animated GIFs sent from the consumer app
  • Voice and video calls initiated from the consumer app
  • Messages sent from WhatsApp groups
  • Contact cards shared natively from a contact's phonebook
  • Messages between two WhatsApp Business API accounts

How Unsupported Messages Appear

When an unsupported message is received, the CRM displays a placeholder in the conversation thread. You might see a message bubble stating "Unsupported Message" or a similar notification. In some cases, such as with an unsupported file, it may be converted into a clickable URL. You will know a message was sent, but the actual content will be inaccessible. You can still reply to the contact as usual.

How to Resolve Unsupported Message Issues

If you encounter an unsupported message, follow these steps:

  1. Identify the Message Type: Check the conversation context to understand what the contact was likely trying to send.
  2. Request a Resend: Politely ask the contact to resend their message using a supported format, such as plain text, an image, an audio file, or a document.
  3. Check Outbound Messages: If you are sending a message and receive this error, verify that your message type and format match the supported list above.
  4. Review API Parameters: For persistent outbound errors, ensure your message payload does not contain any unsupported fields or incorrect parameters.

Please note that for inbound unsupported messages, there is no way to retrieve or view the original content. The resolution involves guiding the contact to use a supported message type.