> 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/functional-overview.md).

# Functional Overview

**Goal:** Understand how nativeMsg works — the key tools, sections, and workflows you’ll use daily.

***

### 💡 Big Picture

nativeMsg connects your brand to your customers through automated, intelligent conversations.\
\
You can build, send, and monitor messages across multiple channels — all in one place.

> 🧭 *If you’ve ever used an email marketing tool, think of this as your conversational version of it with automation, personalization, and live reporting built in.*

***

### 🧩 Core Components

| Feature          | Description                                                                               | Quick Link                                                                                            |
| ---------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Dashboard**    | Your control center — see activity, metrics, trends, and scheduled messages.              | [Dashboard](https://support.nativemsg.com/support/solutions/articles/67000462751-about-dashboard)     |
| **Bots**         | The brains of your automation. They send messages, follow logic, and interact with users. | [Bots](https://support.nativemsg.com/support/solutions/articles/67000462786-about-bots)               |
| **Channels**     | Where your bots live — SMS/RCS, Web Chat, Facebook Messenger, and more.                   | [Channels](https://support.nativemsg.com/support/solutions/articles/67000463842-about-channels)       |
| **Interactions** | Message flows — rules and actions inside each bot that define how conversations work.     | [Interactions](https://support.nativemsg.com/support/solutions/folders/67000410151)                   |
| **Blasts**       | One-to-many messages to your audience (like announcements or promotions).                 | [Blasts](https://support.nativemsg.com/support/solutions/articles/67000465186-about-blasts)           |
| **Humans**       | Your customer list — all users who’ve ever interacted with you.                           | [Humans](https://support.nativemsg.com/support/solutions/articles/67000465196-about-humans)           |
| **Tags**         | Segmenting your list                                                                      | [Tags](https://support.nativemsg.com/support/solutions/articles/67000465198-managing-tags-for-humans) |
| **Intents**      | What's the human asking to do?                                                            | [Intents](https://support.nativemsg.com/support/solutions/articles/67000462866-about-intents)         |

***

### 🧠 How It All Fits Together

1. **Create a Bot** → define your message flow.
2. **Connect a Channel** → choose where your bot runs (SMS, Web Chat, etc.).
3. **Add Interactions** → design the conversation steps.
4. **Test** → make sure it feels natural and compliant.
5. **Publish** → go live.
6. **Monitor via Dashboard** → track performance and iterate.

> 🚀 *Once your bot works well, you can expand it to new channels or send Blasts to larger audiences.*

***

### 🧭 Quick Start Next Steps

Ready to see it in action? Go to "Create Your First Message," a 10-minute guided walkthrough to get your first bot live.


---

# 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/functional-overview.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.