> 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-message.md).

# Create Your First Message

## Quick & Practical Guide

**Goal:** Build and send your first automated message in under 10 minutes.

***

### ⏱️ What You’ll Do

1. **Create a Bot** — name it and pick a template (or start blank). This is the beginning of the experience.
2. **Connect a Channel** — SMS/RCS, Web Chat, or Facebook Messenger.
3. **Add Interactions** — the messages and rules your bot will follow.
4. **Test It** — run the in-app tester until it feels right.
5. **Publish** — go live.
6. *(Optional)* **Send a Blast** — message multiple users at once.

***

### 🤖 Step 1: Create a Bot

* Go to **Bots → Create New Bot**.
* Give it a **name** (e.g., “Welcome Flow”).
* Choose a **template** or start blank.
* Click **Save**.

> 💡 *Pro Tip:* Start small — one welcome message is enough to get live fast.

***

### 🔗 Step 2: Connect a Channel

* Open your new bot → click **Add Channel**.
* Choose where you’ll send from:
  * **SMS/RCS** for phone messaging
  * **Web Chat** for your site
  * **Facebook Messenger** for social
* Enter the required credentials → **Connect.**

✅ You’ll see your channel listed with an icon when connected.

***

### 💬 Step 3: Add Interactions

* On your bot canvas, click **+ Add Interaction.**
* Name it (e.g., “Welcome Message”).
* Inside that interaction, add **Actions**:
  * Message: text to send (“Hi {first\_name}, welcome to nativeMsg!”)
  * Wait for: pauses until user responds
  * Assign Tag / Update Attribute: save user data for personalization

> ⚙️ *Start simple: one message + one reply path.*

***

### 🧪 Step 4: Test Your Bot

* Click **Test Bot** in the editor.
* Type like a user — check flow, replies, and links.
* Make sure STOP and HELP work properly.
* Adjust interactions if needed.

✅ Repeat until it feels natural and correct.

***

### 🚀 Step 5: Publish

* Click **Publish.**
* Your bot is now live on the selected channel.
* Watch early results on your **Dashboard** → Bots panel.

> 📊 *Metrics like New Humans, Conversations, and Messages will update in real time.*

***

### 📢 Optional: Send a Blast

* Go to **Blasts → Create New Blast.**
* Choose your **bot**, **channel**, and **audience (tags)**.
* Write a short message (under 160 chars).
* Add a branded link (no bit.ly).
* Schedule or send immediately.

> 💡 *Always target Blasts to specific Tags — never send to everyone.*

***

### ✅ You’re Live!

You’ve just:

* Created a bot
* Connected a channel
* Built your first flow
* Tested and published
* (Optionally) sent your first broadcast

You’re now running your first automated nativeMsg experience!


---

# 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-message.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.