> 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/getting-started/invite-your-team.md).

# Invite Your Team

**Time: 3 minutes**

Add your setters, closers, and managers so they can start working leads immediately.

## Team Roles

| Role        | What They Can Do                                                                        |
| ----------- | --------------------------------------------------------------------------------------- |
| **Creator** | Full access. Manage team, integrations, settings, and all leads. Only one per org.      |
| **Manager** | Manage team and integrations. View all leads and analytics. Cannot remove the creator.  |
| **Setter**  | See and respond to assigned leads. Can transfer leads to closers. Limited dashboard.    |
| **Closer**  | See assigned leads with full conversation history. Focused on booked calls and closing. |

## How to Invite

1. Go to **Settings → Team**
2. Click **Add Member**
3. Enter their email address
4. Select their role (Setter, Closer, or Manager)
5. Set their **commission percentage** — tracked automatically when deals are Won
6. Click **Add** — they'll receive an email invite

{% hint style="warning" %}
**Important:** Team members must accept their invite and complete their profile before they appear as active in Mochi. Check Settings → Team to see pending invites and resend if needed.
{% endhint %}

## What Team Members See

When a team member accepts their invite, they'll:

1. Click the invite link in their email
2. Set up their profile (name, photo)
3. Land in the app with access based on their role

**Setters** see their assigned conversations in the Inbox and their leads. **Closers** see leads assigned to them with full conversation context. **Managers** see everything the Creator sees, minus some admin settings.

## Commission Tracking

Each team member can have a commission percentage set. When a deal is marked as Won with a payment amount, Mochi calculates commissions automatically. You can adjust commission rates anytime in Settings → Team.

## Distribution Weights

For round-robin lead assignment, you can set distribution percentages per setter. A setter with 60% weight will receive roughly 60% of new leads. Adjust this in team settings as your team scales.

## You're All Set

Your Mochi workspace is ready:

* Account created
* Organization configured
* Instagram connected
* Team invited

Your team can now start responding to leads from the **Inbox**, tracking them through **Leads**, and monitoring performance on the **Dashboard**.

### Recommended Next Steps

* Connect Calendly for automatic booking tracking (see **Integrations**)
* Set up voice clone so setters can send voice notes in your voice (see **Voice Clone**)
* Configure tags to organize your leads (see **Tags**)
* Explore AI Setter for automated conversation handling (see **AI Setter**)


---

# 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/getting-started/invite-your-team.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.