# Quickstart Guide

***

### 🛠️ Quick Setup Checklist

Before you activate Operator AI, make sure you’ve completed these essentials:

| Task                             | Why It’s Important                                                                          |
| -------------------------------- | ------------------------------------------------------------------------------------------- |
| **Connect at least one channel** | Enable conversations via Web Chat, SMS, WhatsApp, Instagram, Facebook, Email, etc.          |
| **Build a Starter Flow**         | Guide users through key journeys like lead capture, support triage, or appointment booking. |
| **Train your Knowledge Base**    | Upload FAQs, website content, and documents to answer common questions automatically.       |
| **Set Hours & Offline Mode**     | Define how Operator AI behaves outside working hours (e.g., capture leads, notify users).   |
| **Configure Fallbacks**          | Ensure smooth recovery if Operator AI doesn’t understand a question.                        |
| **Prepare Automation Rules**     | Set up welcome messages, lead capture triggers, or proactive engagement flows.              |

✅ These basics give you a strong, professional Operator AI foundation.

***

### 🏗️ How to Launch Your First Operator AI Experience

1. **Log into your Operator AI Dashboard**.
2. **Go to Settings**.
3. **Connect your first communication channel** (e.g., Web Chat, SMS, WhatsApp).
4. **Create your first Flow** under the Flows section.
5. **Upload key FAQs or import website content** to populate the Knowledge Base.
6. **Set Hours and Offline Mode**.
7. **Enable Fallback and Default Replies**.
8. **Activate your Operator** in **Settings → Artificial Intelligence → Chatbot**.

✅ You’re now ready to automate conversations and capture leads 24/7.

***

### 📋 Quick Example Launch Timeline

| Day     | Action                                                            |
| ------- | ----------------------------------------------------------------- |
| Day 1   | Connect Web Chat or WhatsApp. Build Starter Flow. Add basic FAQs. |
| Day 2   | Test Flows, Knowledge Base responses, and Fallbacks.              |
| Day 3   | Launch Operator AI. Monitor conversations via Unified Inbox.      |
| Week 1+ | Add Automations, expand Knowledge Base, optimize Flows.           |

✅ Small setup = big customer impact.

***

### 🧠 Pro Tips for Your First Week

| Tip                                  | Why It Matters                               |
| ------------------------------------ | -------------------------------------------- |
| Test conversations yourself          | Feel the user journey firsthand.             |
| Simulate wrong answers               | Check how good your fallbacks feel.          |
| Collect early customer feedback      | Small tweaks make a big difference early.    |
| Add tags to users based on behaviors | Improves future segmentation and automation. |

✅ Operator AI improves fastest when you observe and adjust early.

***

### 🛟 Need Help?

* View full setup guides in this documentation.
* Contact Support at <support@heyoperator.ai>.
* Ask your Operator AI Success Manager for a quick 1:1 onboarding session.

✅ We’re committed to your success from day one.

***

## 🎯 Next Step

Once connected, build even smarter customer experiences by setting up all your messaging channels:

👉 [Continue to Connect Your Channels →](/start/setup/connect-channels.md)


---

# Agent Instructions: 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:

```
GET https://operator-ai.gitbook.io/start/setup/quickstart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.