> For the complete documentation index, see [llms.txt](https://playbook.nativemsg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.nativemsg.com/get-started/quickstart/create-your-first-carousel.md).

# Create Your First Carousel

## End-to-End Guide

**Goal:** Build and send your first interactive Carousel message — both inside a bot flow (1:1) and as a broadcast (1-to-many).\
**Estimated Time:** 15–20 minutes

***

### 🧭 Overview

Carousels let you show multiple cards in a single message — each with images, titles, buttons, and quick replies.\
They’re perfect for:

* Product menus
* Multi-option surveys
* Support or service choices
* Content showcases

You can use Carousels:

* **Inside a Bot** (for ongoing 1:1 conversations), or
* **As a Blast** (to broadcast to many users at once).

***

### Part A — Build It in a Bot (for 1:1 and ongoing flows)

#### 1️⃣ Create or Open a Bot

* Go to **Bots → Create New Bot**, name it (e.g., “Product Carousel”).
* Or open an **existing bot** to add the carousel to an existing flow.

***

#### 2️⃣ Connect a Channel

* Click **Add Channel** → choose your target channel:
  * Web Chat
  * Facebook Messenger
  * SMS/RCS
* Enter required credentials → click **Connect.**

✅ Once connected, you’ll see your channel icon listed under that bot.

***

#### 3️⃣ Add an Interaction

* On your bot canvas, click **+ Add Interaction**.
* Name it something clear like **“Product Carousel.”**

> 💡 *Each interaction can contain one or more actions. The Carousel lives inside one of these.*

***

#### 4️⃣ Add a Rich Card (Carousel) Action

* Open your new interaction.
* Click **Add Action → Rich Card.**
* In the action panel, choose **Carousel.**

***

#### 5️⃣ Configure the Carousel

**Overall Title (optional):**\
Used on some channels to introduce the Carousel.

**Bubbles / Cards:**\
For each card you add:

* **Title (required)** — short, clear text (e.g., “New Arrivals”).
* **Subtitle (optional)** — add context (e.g., “Explore our newest products”).
* **Media File:** click *Media file* to upload or link an image/video.
* **Media Height:** pick what fits your design (auto, short, tall).
* **Card Width (if available):** choose how wide each card should appear.
* **Default Action (optional):** choose what happens when the card is tapped.

Click **+ Add Bubble/Card** to include more cards.

> 🖼️ *Pro Tip:* Use consistent image sizes across cards for clean scrolling.

***

#### 6️⃣ Add Buttons & Quick Replies (Optional but Recommended)

**Buttons on each card:**\
You can add one or more of these:

* URL — open a webpage
* Postback — trigger another interaction
* Phone — initiate a call
* View Location — show a map
* Calendar — open scheduling

**Quick Replies (under the carousel):**\
Add shortcuts for users, like:

* Postback
* Location
* View Location
* Calendar

You can also enable:

* **Multi-select** — allow multiple choices
* **Submit title** + **Execute target** — define what happens after submission.

***

#### 7️⃣ Save → Test → Publish

* Click **Test Bot** to preview the Carousel flow.
* Review layout, buttons, and media behavior across devices.
* Adjust copy, image size, or actions if needed.
* Click **Publish** when ready.

✅ Your Carousel is now live in your bot’s 1:1 flow.

***

### Part B — Send a Carousel as a Blast (One-to-Many)

#### 1️⃣ Create a New Blast

* Go to **Blasts → Create New Blast.**
* Enter a **title**, select a **Bot**, and choose:
  * **Channel(s)** (e.g., SMS, Web Chat)
  * **Tags** (audience segment)

***

#### 2️⃣ Build the Carousel

* In the **Create Message** screen → click the **Carousel tab.**
* For each card:
  * Title, Subtitle
  * Media file (upload or link)
  * Default Action (optional: URL, Postback, or advanced Web default)

**Buttons on each card:**

* URL, Postback, Phone, Location, Calendar

**Quick Replies (below the carousel):**

* Postback
* Location
* View Location
* Calendar

***

#### 3️⃣ (Optional) Add RCS Fallback

If sending via RCS:

* Add a **Fallback Message** — combine an MMS image + SMS text.
* Ensures users without RCS still receive your message.

***

#### 4️⃣ Send or Schedule

* Click **Send Blast** to send now, or **Schedule** for later.
* View upcoming sends under **Dashboard → Scheduled Messages.**

✅ Once sent, performance metrics appear in the **Dashboard → Blasts** section.

***

### ⚙️ Smart Defaults & Tips

| Best Practice           | Why It Matters                                  |
| ----------------------- | ----------------------------------------------- |
| **Image Aspect Ratio**  | Keep all cards consistent for smooth scrolling. |
| **Buttons (1–2 max)**   | Too many options cause decision fatigue.        |
| **Branded Links Only**  | Use your domain — avoid public shorteners.      |
| **Short Copy**          | Put key info in the first 60–90 characters.     |
| **Preview on Channels** | Rendering varies by channel — test each.        |

> 💡 *Previewing on Web and SMS ensures consistent look before launch.*

***

### ✅ Mini Compliance Check (Before Go-Live)

* [ ] Brand is clear on the carousel and first message.
* [ ] Required disclosures (STOP/HELP/frequency/rates) appear in your flow or confirmation.
* [ ] Links use branded domains and are live.
* [ ] Policy links (Privacy + Terms) are accessible.
* [ ] Opt-in documentation is stored.

***

### 🧭 Related Articles

* Create Your First Message
* Sending Your First Blast
* Launching Your 10DLC Campaign with Confidence
* Opt-In / Opt-Out Language


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://playbook.nativemsg.com/get-started/quickstart/create-your-first-carousel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.