> For the complete documentation index, see [llms.txt](https://themochi-app.gitbook.io/mochi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://themochi-app.gitbook.io/mochi-docs/mochi-sops/mochi-quick-start-cheat-sheet.md).

# Mochi Quick-Start Cheat Sheet

#### Get live in 60 minutes. Follow this order.

### Step 1 — Access Your Account

* Go to [use.themochi.app](http://use.themochi.app)
* Enter your email → check inbox for magic link (expires in 15 min)
* Click the link → you're in

💡 Didn't get the email? Check spam. Still nothing? Email <hey@themochi.app><br>

### Step 2 — Set Up Your Organisation

* Add your organisation name
* Upload your logo
* Enter your access code (sent in your welcome email + Slack invite)

### Step 3 — Connect Instagram

* Settings → Socials → Connect Instagram
* Must be a Business or Creator account (not Personal)
* Accept all permissions — Mochi needs full message access
* Add close friends / personal contacts to Excluded Contacts so they never appear in your setter's inbox

⚠️ After connecting: wait 2–4 days before putting your setters live. This lets messages accumulate so there's no confusion from legacy conversations.<br>

### Step 4 — Invite Your Team

* Settings → Team → Add team member
* Assign roles: Creator / Manager / Setter / Closer
* Set commission % per setter
* Set lead distribution (must total 100%)

### Step 5 — Connect Calendly *(if applicable)*

* Settings → Integrations → Connect Calendly
* Select which event types your setters can send
* When a setter sends a link from inside Mochi → lead auto-updates to Qualified
* When lead books → auto-updates to Call Booked

### Step 6 — Set Up Your First AI Tags

Build at least these 4 before going live:\ <br>

| <p>Tag<br></p>                            | <p>What it catches<br></p>                                  |
| ----------------------------------------- | ----------------------------------------------------------- |
| <p><code>Hot Lead</code><br></p>          | <p>Lead showing strong buying intent or urgency<br></p>     |
| <p><code>Qualified</code><br></p>         | <p>Lead has revealed budget, timeline, real problem<br></p> |
| <p><code>Booking Link Sent</code><br></p> | <p>Setter has sent the Calendly link<br></p>                |
| <p><code>Objection — Price</code><br></p> | <p>Lead mentions cost after a CTA has been issued<br></p>   |

***

### Step 7 — Configure Spam Filter

* Settings → Intelligence → Spam Filter
* See the Spam Filter Prompt Guide (pinned below) for how to build your prompt

### You're 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://themochi-app.gitbook.io/mochi-docs/mochi-sops/mochi-quick-start-cheat-sheet.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.