> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/ai-text-agents/inbox.md).

# Inbox

Find, take over, assign, answer, note and close Text Agent conversations in Inbox.

Inbox is where your team works the chats your text agents have with customers. For each chat you see who is answering it, the AI agent, a teammate or nobody, and from there you take it over, reply, leave notes for your team and close it. It is the operating view, not an export of all activity: use [history and exports](https://docs.dapta.ai/ai-text-agents/analytics-and-logs.md) for reporting.

Open **Text Agents → Inbox** in the correct workspace.

{% hint style="info" %}
**New in November 2026.** Inbox has a new desktop design, and each chat has one owner at a time: only that person can write in it. Anyone else clicks **Take over** first.
{% endhint %}

***

## The conversation list

The top of the list has three rows: the **Inbox** title with your availability (**Online** or **Offline**) and the alerts bell; search and the **New conversation** button; then the **Filters** button and the **All**, **Mine**, **Unassigned** and **Unread** views. To get a desktop alert when a chat is assigned to you or a customer replies on WhatsApp, see [Desktop alerts](https://docs.dapta.ai/ai-text-agents/inbox/desktop-alerts.md).

Each row shows the customer, the last message and who is answering: the AI agent's name, **You**, or a teammate. A chat from your website shows as **Web visitor** followed by four characters of its ID. When a customer is waiting for a person to answer, the row shows **Waiting** and for how long, highlighted after 15 minutes.

* **All** shows every chat that matches your filters.
* **Mine** shows the chats assigned to you.
* **Unassigned** shows open chats handed to people that no one has picked up yet. It is not a list of every chat the AI handles. While it is selected, it controls the **Status** filter.
* **Unread** combines with the other views: for example, **Mine** and **Unread** is your own queue.

The **Filters** button opens **Source**, **Assigned to**, **Status**, **Date range**, **AI agent** and **Tags**. **Status** takes several values at once, **Open**, **Started by you, no reply yet** and **Closed**, and starts on **Open**. Each active filter shows as a chip above the list; click its **×** to remove it. **Clear filters** removes them all, **Status** included, goes back to **All** and turns **Unread** off.

When no chat is open, the right side offers shortcuts with counters to **Unassigned**, **Unread** and **Mine**. Inside a chat, **Alt + ↑** and **Alt + ↓** open the previous and the next conversation.

Opening a conversation clears its unread mark. Unread is not a delivery, success or assignment status. What you see also depends on your access to the workspace.

***

## Conversation states

The state shows next to the customer's name at the top of the chat.

| State                            | What it means                                                                                                                                                                                                          |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Open**                         | An active chat. Who can write depends on its owner (see below).                                                                                                                                                        |
| **Started by you, no reply yet** | Your business wrote first, with a template, and the customer hasn't answered. The chat says **Conversation initiated by your business. Awaiting the contact's first reply.** and is read-only until the reply arrives. |
| **Closed**                       | A finished chat. It says **This conversation is closed.** Read its history; you can't reply in it.                                                                                                                     |

A template you sent doesn't prove the customer engaged. When the first reply arrives, the chat becomes **Open**. If no reply arrives before its waiting period ends, it closes, and history can show a failed outcome for that unanswered opening. That path doesn't run the normal post-conversation analysis. Don't read that "Failed" as a delivery failure. See [history and exports](https://docs.dapta.ai/ai-text-agents/analytics-and-logs.md) to find these records outside Inbox.

***

## Who answers a chat

An open chat has exactly one owner at a time: the AI agent, one teammate, or nobody. A bar at the bottom of the chat says which:

| The bar says                                | What it means                                  |
| ------------------------------------------- | ---------------------------------------------- |
| **Lucy (AI) is handling this conversation** | The AI agent, here Lucy, answers the customer. |
| **Ana is handling this conversation**       | A teammate, here Ana, owns the chat.           |
| **Nobody is handling this conversation**    | No person and no AI answers it.                |

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-a0b8d959b135eaf3123507b7d7e7f4ac2c380ed3%2Finbox-ai-handling.png?alt=media" alt="An open website chat in Inbox: the header with Assign and Close, the customer&#x27;s question and the AI&#x27;s answer, and the bar Lucy (AI) is handling this conversation with the Take over button"><figcaption></figcaption></figure>

Only the owner gets the message box. To answer yourself, click **Take over** on that bar: the chat is assigned to you and the AI stops answering it, so the customer never gets two replies. Writing doesn't assign a chat to you on its own: take it over first.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-3fa905e5f9bd11d00f979562c64059af57b4a08e%2Finbox-taken-over.png?alt=media" alt="The same chat after Take over: the header shows You as the owner, and the message box has the Reply and Internal note tabs, Reply on Web chat… and Send"><figcaption></figcaption></figure>

### Assign a chat or hand it back to the AI

**Step 1:** Click **Assign** at the top of the chat.

**Step 2:** Search for a teammate and click their name. You are on the list as **You**. Assigning a person turns the AI off for this chat.

**Step 3:** To hand the chat back to the AI, open **Assign** again and click **Unassign conversation**. The AI agent answers the customer again. This is not the same as closing the chat.

If the list says **No teammates to assign yet**, [add your team](https://docs.dapta.ai/my-account/account/add-team-members.md) to the workspace first. A chat whose owner left the workspace shows **Owner left**: assign it to someone else.

Next to the **Inbox** title, the **Online** / **Offline** switch sets your availability in every human-handover pool you belong to at once. It reads **Online** only when you're online in all of them. If you aren't in any pool it's greyed out; ask an admin to add you. Availability doesn't replace assigning a particular conversation.

***

## Reply with text or media

In a chat you own, the message box has two tabs: **Reply** and **Internal note**. On **Reply**, the box says where your message goes, for example **Reply on WhatsApp…** or **Reply on Web chat…**. **Enter** sends; **Shift + Enter** or **Alt + Enter** adds a line break.

On WhatsApp, a reply can have up to 4,096 characters, and a counter appears above the message box once the message gets long. A long reply shows a hint such as **Will be sent as 2 messages**: it arrives as consecutive messages, in order, with no numbering such as (1/3). The AI's long replies arrive the same way. Over the limit, the box shows **Over the 4096-character limit. Shorten it to send.** and won't send it.

To add an **Image**, a **File** or an **Audio** recording, use the attachment button next to the message box. It only shows on channels that accept files. Allow the microphone when you record, stop and review the recording, then send. Remove an attachment you don't want before sending, and follow the type and size limits shown.

On WhatsApp chats, **Send template** sits in the message box. Once the 24-hour reply window has closed, only a template reaches the customer: see the [template guide](https://docs.dapta.ai/ai-text-agents/channels/message-templates.md). Its customer-service-window rules apply to people as well as to the AI.

Under each message you send, its status reads **Sent**, **Delivered**, **Read** or **Not delivered**. Hover **Not delivered** to see why: see [When you cannot send](#when-you-cannot-send). If an attachment fails, read its error before retrying, and don't resend text or attachments that already went through.

In the timeline you can review:

* The customer's messages, the AI's (marked **AI assistant**) and your team's.
* Images, downloadable files and audio, with a transcription when available.
* Tool cards for each action the agent ran, with its state (**Running…**, **Done** or **Failed**), its inputs and its answer.
* Messages and media synced from a WhatsApp Business App line that keeps working on the phone.

A synced Business App message is not an extra AI reply. An action marked **Done** doesn't by itself prove a business outcome: read its answer. When messages arrive below where you are reading, **New messages** marks them and **Jump to latest** takes you to the end.

***

## Internal notes

Click **Internal note** in the message box to write to your team instead of the customer. The box reads **Only visible to your team — never sent to the customer**; click **Save note**. The note shows in the timeline as **Internal note**. Attachments aren't part of a note: they stay queued for your next reply. As with replies, you need to own the chat.

For something that should follow the customer to every chat, use the **Contact note** in the contact details instead.

***

## Contact details

The button next to **Close** opens **Customer**: the contact's name and phone or email (a website chat shows its visitor ID), the chat's **Owner** and status, the **AI agent**, **Tags**, the **Variables** the agent captured, and **Previous conversations** with this contact.

The **Contact note** there sticks to the contact, not to this conversation, and the AI agent can read it: the panel says, for example, **Lucy (AI) can read this note**.

***

## Close a conversation

Click **Close** at the top of the chat, review the confirmation and confirm only when the work is done. Closing can't be undone, and it isn't the same as handing the chat back to the AI.

The agent's configured closure and analysis behavior decides what happens next. Review the history afterwards when you need the final outcome rather than assuming it is immediately available.

The **⋯** menu (**Conversation actions**) has **Block user**: after you confirm, that contact can't message this channel anymore. **Unblock user** undoes it.

***

## When you cannot send

| Situation                        | What to check                                                                                                                                                           |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| No message box                   | You don't own the chat: click **Take over**. Also check the conversation state and that your role can write in Inbox.                                                   |
| **Message too long**             | The reply is over 4,096 characters. Shorten it and send it again; your draft is kept.                                                                                   |
| **Started by you, no reply yet** | Read-only by design. Wait for the customer's reply instead of sending more opening templates.                                                                           |
| The line is paused or blocked    | Dapta or Meta stopped the line from sending: see [When a WhatsApp line is paused or blocked](https://docs.dapta.ai/ai-text-agents/channels/paused-or-blocked-lines.md). |
| Conversation missing             | Workspace, access, filters and the **Started by you, no reply yet** status; then check history.                                                                         |

When a message shows **Not delivered**, hovering it gives one of these reasons:

| Reason shown                                                                                     | What to do                                                                                                              |
| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| The 24-hour reply window closed.                                                                 | Send a template to reach this customer.                                                                                 |
| This contact can't receive messages on this channel (for example, the number isn't on WhatsApp). | Reach the customer another way.                                                                                         |
| The customer opted out or blocked this business.                                                 | Don't retry.                                                                                                            |
| WhatsApp held back this marketing message to limit how many the customer gets.                   | Try again later.                                                                                                        |
| Too many messages were sent too quickly.                                                         | Wait a moment, then retry.                                                                                              |
| The business account has a problem (locked, payment or policy).                                  | An admin fixes it in Meta Business.                                                                                     |
| The template is missing, paused, or its variables don't match.                                   | Check the template in [WhatsApp message templates](https://docs.dapta.ai/ai-text-agents/channels/message-templates.md). |
| The attachment couldn't be sent: its format or size isn't supported.                             | Send another format or a smaller file.                                                                                  |
| The customer's phone couldn't be reached.                                                        | Try again later.                                                                                                        |
| The messaging provider had a temporary problem.                                                  | Try again in a few minutes.                                                                                             |
| The provider rejected this message (code …).                                                     | Note the code and contact support if it repeats.                                                                        |

When a retry can't help, the reason ends with **Retrying won't fix this.**

*Source review: November 17, 2026. Available actions depend on the channel, the conversation state and your permissions.*

{% content-ref url="/pages/RyyjwoDIy0fMQZ7hWc7V" %}
[Desktop alerts](https://docs.dapta.ai/ai-text-agents/inbox/desktop-alerts.md)
{% endcontent-ref %}

{% content-ref url="/pages/LT6vPXywEfXjmz1MwdWI" %}
[WhatsApp message templates](https://docs.dapta.ai/ai-text-agents/channels/message-templates.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/ai-text-agents/inbox.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
