> ## Documentation Index
> Fetch the complete documentation index at: https://docs.digifist.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Message Composition

> Campaign message formats in Galantis — from standard rich cards to single and multi-product messages and whole catalog browsing.

The message format of a campaign is determined by the template you select. Galantis supports five distinct formats — from simple promotional cards to interactive product carousels and full catalog browsing. Each format serves a different purpose and has different structural requirements, some of which depend on a synced Meta Catalog.

## What this covers

* All five campaign message formats and their use cases
* Structural components of each format
* Which formats require a Meta Catalog
* Guidance on choosing the right format

## Message formats

<Tabs>
  <Tab title="Single Rich Card">
    **Single Rich Card** (`SINGLE_RICH_CARD`) is a promotional message format combining a header, body text, footer, and up to three action buttons into a single visual card.

    **Structure:**

    * `HEADER` — Text with optional variable
    * `BODY` — Rich text with dynamic variables
    * `FOOTER` — Static short text (e.g., "Reply STOP to unsubscribe")
    * `BUTTONS` — Up to 3 buttons: Quick Reply, URL, Phone Number, or Copy Code

    **Best for:** Single-focus promotional messages where one clear CTA drives the customer toward a product page, discount redemption, or direct response.

    **Meta Catalog required:** No

    <Tip>
      Single Rich Cards work well for time-limited offers. Use a `COPY_CODE` button for discount codes and a `URL` button linking directly to the product or collection page.
    </Tip>
  </Tab>

  <Tab title="Multi Rich Card">
    **Multi Rich Card** (`MULTI_RICH_CARD`) presents multiple cards in a horizontally swipeable carousel. Each card in the carousel has its own image, body text, and buttons.

    **Structure:**

    * `BODY` — Carousel-level introductory text
    * `CAROUSEL` — Multiple individual cards, each with image, body, and buttons

    **Best for:** Showcasing several products, collections, or offer options in a single message where the customer can swipe through and choose what interests them. More engaging than sending multiple separate messages.

    **Meta Catalog required:** No — card content is defined at the template level, not pulled from a live catalog sync.

    <Note>
      Carousel card content is fixed in the template at creation time. If product details or offers change frequently, a catalog-based format (SPM or MPM) may be easier to maintain since it pulls live product data.
    </Note>
  </Tab>

  <Tab title="Single Product Message">
    **Single Product Message** (`SINGLE_PRODUCT_MESSAGE`, SPM) showcases one specific product from your synced catalog, including variants, pricing, and a buy button that opens the product in WhatsApp's native commerce UI.

    **Structure:**

    * `HEADER` — Product pulled from catalog (`PRODUCT` header type)
    * `BODY` — Supporting text with dynamic variables
    * `FOOTER` — Static text
    * `BUTTONS` — Action buttons
    * `PRODUCT_SECTIONS` — Product and variant selection data from catalog

    **Best for:** Targeted product promotions where a specific item is the focus — such as a best-seller highlight, a back-in-stock broadcast, or a personalized recommendation based on purchase history.

    **Meta Catalog required:** Yes — the product displayed is pulled from your synced Meta Catalog. The catalog must be connected and the product must have `SYNCED` status before this format can be used.
  </Tab>

  <Tab title="Multi-Product Message">
    **Multi-Product Message** (`MULTI_PRODUCT_MESSAGE`, MPM) displays up to 30 products from your synced catalog in a scrollable list, allowing customers to browse and select from multiple items in a single message.

    **Structure:**

    * `HEADER` — Text with optional variable
    * `BODY` — Introductory message text
    * `FOOTER` — Static text
    * `BUTTONS` — Action buttons
    * `PRODUCT_SECTIONS` — Multiple product entries from catalog, organized into sections

    **Best for:** Collection-based campaigns, curated product selections, or "shop the look" style sends where the goal is to drive browsing rather than focus on a single item.

    **Meta Catalog required:** Yes — products are pulled from your synced Meta Catalog. All products included must have `SYNCED` status.
  </Tab>

  <Tab title="Whole Catalog">
    **Whole Catalog** (`WHOLE_CATALOG`) sends a message with a catalog browse button that opens your entire WhatsApp catalog, allowing customers to browse all available products without the merchant pre-selecting items.

    **Structure:**

    * `BODY` — Introductory message text
    * `FOOTER` — Static text
    * `CATALOG` button — Opens the full catalog browser in WhatsApp

    **Best for:** High-intent audiences who are likely to browse broadly — such as a segment of frequent purchasers, customers who have visited your store multiple times, or a VIP list. Also useful for stores with large catalogs where pre-selecting products for MPM is impractical.

    **Meta Catalog required:** Yes — the entire catalog must be synced and connected to Meta.
  </Tab>
</Tabs>

## Format selection guide

| Format           | Catalog required | Products shown        | Best use case                         |
| ---------------- | ---------------- | --------------------- | ------------------------------------- |
| Single Rich Card | No               | 0 (image only)        | Single-focus promotion or offer       |
| Multi Rich Card  | No               | Up to \~10 (carousel) | Multi-product showcase, fixed content |
| SPM              | Yes              | 1 specific product    | Targeted product promotion            |
| MPM              | Yes              | Up to 30 products     | Collection or curated product send    |
| Whole Catalog    | Yes              | Full catalog          | Browse-driven, high-intent audiences  |

## Meta Catalog requirements

SPM, MPM, and Whole Catalog formats all require:

1. A Meta Catalog connected to your Galantis workspace — see [Catalog — Meta Catalog](/whatsapp/catalog/meta-catalog)
2. Products with `SYNCED` status in your catalog — see [Catalog — Health](/whatsapp/catalog/catalog-health)

If a product referenced in an SPM or MPM template has not been successfully synced to Meta, that template cannot be used in a campaign until the sync issue is resolved.

## Related guides

* [Campaign Types](./campaign-types) — How message format determines campaign type
* [Personalization](./personalization) — Populating dynamic variables in message body and header
* [Catalog](/whatsapp/catalog/index) — Full catalog sync and Meta connection reference
* [Templates — Formats](/whatsapp/templates/template-formats) — Template structure components in detail