> 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/feature-and-settings/inbox.md).

# Inbox

The Inbox is where your team spends most of their time. It's a shared workspace for all your Instagram DM conversations.

## Layout

The Inbox has three panels:

{% columns %}
{% column %}
**Conversation list** (left) — All active conversations, searchable and filterable
{% endcolumn %}

{% column %}
**Chat view** (center) — The active conversation with full message history
{% endcolumn %}

{% column %}
**Lead details** (right) — Lead info, funnel stage, tags, timeline, and actions
{% endcolumn %}
{% endcolumns %}

{% hint style="info" %}
On mobile, these panels stack into a single-column view.
{% endhint %}

## Working with Conversations

### Reading and Responding

Click any conversation from the list to open it. You'll see the full message history between your Instagram account and the lead. Type your reply at the bottom and send — it goes directly as an Instagram DM.

You can send:

* Text messages
* Media (images, videos)
* Voice notes (using voice clone — see **Voice Clone**)
* Calendly links (for booking tracking — see **Integrations**)

### AI Response Suggestions

When enabled, Mochi suggests replies based on your conversation context and sales playbook. Suggestions appear above the message input. Click one to use it, or ignore and write your own.

### Read Status

Conversations show read/unread status per team member. When you open a conversation, it's marked as read for you. Other team members will still see it as unread until they open it.

## Conversation List

### Filtering

Filter your conversation list to focus on what matters:

* **By assignment** — See only conversations assigned to you
* **By status** — Unread, all, or specific funnel stages
* **By search** — Find conversations by lead name or username

### Real-Time Updates

New messages appear instantly — no need to refresh. When a lead sends a DM, it appears in your conversation list immediately via real-time sync.

## Lead Panel

The right panel shows details about the lead you're chatting with:

* **Lead info** — Name, Instagram username, profile picture, follower count
* **Funnel stage** — Current stage with ability to change it
* **Assigned team** — Which setter and closer are assigned
* **Tags** — Custom tags applied to this lead
* **Timeline** — Activity history (stage changes, payments, notes)
* **Team** — Internal team notes for this specific conversation. Leave notes with @mentions so teammates get notified. Not visible to the lead.
* **Payments** — Payment records and deposits

## Away Mode

When you step away, enable Away Mode to let the AI Setter handle incoming messages. When you return, you'll see a summary of what happened while you were gone.

See **AI Setter** for details.


---

# 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/feature-and-settings/inbox.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.