WhatsApp Carousel Template Reference

Review Meta specifications, agent and bot behavior, analytics, and considerations for WhatsApp carousel templates.

Meta-Defined Specifications

Carousel templates must comply with Meta's specifications:

Field Required Constraints
MESSAGE_BODY_TEXT Yes Max 1024 characters. Supports variables.
MESSAGE_BODY_TEXT_VARIABLE_EXAMPLE If variables used Must match the number of variable placeholders.
TEMPLATE_LANGUAGE Yes Language and locale code.
TEMPLATE_NAME Yes Max 512 characters.
URL_BUTTON_LABEL_TEXT If using URL button Max 25 characters.
URL_BUTTON_URL If using URL button Max 2000 characters. Supports 1 variable appended to end.
CARD_HEADER_ASSET_HANDLE Yes Uploaded media asset handle via Resumable Upload API.
CARD_HEADER_FORMAT Yes Image or video.
PHONE_NUMBER If using phone button Max 20 characters. Alphanumeric.
PHONE_NUMBER_BUTTON_LABEL_TEXT If using phone button Max 25 characters.
QUICK_REPLY_BUTTON_LABEL_TEXT If using quick reply Max 25 characters.

Agent and Bot Experience

  • Agents see carousel templates in the template selection wizard and can send them during messaging conversations.
  • In the conversation window, agents see a preview of the carousel cards.
  • Bots and Agentforce Service Agent send carousel templates through flows by selecting an approved template in the Send Conversation Messages flow action.

Analytics

Carousel templates capture the following engagement data:

  • Template name and button name for interactive actions (click/tap)
  • Time and date of delivery
  • Read receipt

Considerations

  • Carousel templates are available for the marketing template category only.
  • All cards in a carousel must have the same component structure. If any card includes body text, all cards must include body text.
  • Carousels require a minimum of 2 and maximum of 10 cards.
  • Carousels can't be created in the WABA interface. Use the Salesforce component builder.
  • For product card carousels, the Meta catalog must be set up and linked before creating the template.
  • Templates must be approved by Meta before use.
  • The component renders in the customer's preferred language based on the Messaging End User Language.