> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/reply.md).

# All Conversations

A guide to the All Conversations page, including finding conversations by channel, tab, and filter; replying, toggling automatic replies for individual conversations, taking over and returning convers

<mark style="color:blue;">All Conversations</mark> brings together customer conversations from all channels (web, internal, LINE, Microsoft Teams, and more). Support agents can review Agent replies and reply or take over when needed; supervisors can filter and manage conversations in bulk.

* **Access**: In the left menu, select <mark style="color:blue;">Customer Conversations</mark> → <mark style="color:blue;">All Conversations</mark>.
* **Permissions**: Requires <mark style="color:blue;">Customer Conversation Permissions</mark> and the nested <mark style="color:blue;">All Conversations Permissions</mark>. See [Role and Permission Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/roles/role-permission.md) for details.

## Page Layout <a href="#page-layout" id="page-layout"></a>

| Area                             | Contents                                                                                                                                                                                                                                                                                                         |
| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Left column: channels            | <mark style="color:blue;">All Conversations</mark> appears at the top, followed by a <mark style="color:blue;">Channels</mark> list. Select a channel to view only its conversations. Use the search box above to find a channel, or <mark style="color:blue;">Connect a Channel</mark> at the bottom to add one |
| Middle column: conversation list | Search box, filter button, <mark style="color:blue;">Mine</mark> / <mark style="color:blue;">Unassigned</mark> / <mark style="color:blue;">All</mark> tabs, and the handling status of each conversation                                                                                                         |
| Right side: conversation content | Contact name, channel, <mark style="color:blue;">Details</mark>, and Copilot icon at the top; status bar, messages, and input box below                                                                                                                                                                          |

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-82d89e21687954de8df72b872cc78f51a6c6f357%2Fconversations-page-layout.png?alt=media" alt="All Conversations page: channel list on the left, conversations and tabs for the selected channel in the middle, and the open conversation and status bar on the right"><figcaption><p>All Conversations with a specific channel selected: the list heading shows the channel name and ID, and the open conversation appears on the right</p></figcaption></figure>

When you select a specific channel, the list heading shows its name and channel ID. Click the adjacent button to copy the ID.

## Find Conversations to Handle <a href="#find-conversations" id="find-conversations"></a>

### Tabs <a href="#tabs" id="tabs"></a>

| Tab                                         | Conversations shown                                                                                |
| ------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| <mark style="color:blue;">Mine</mark>       | Conversations assigned to you                                                                      |
| <mark style="color:blue;">Unassigned</mark> | Conversations without an assigned support agent, including those receiving automatic Agent replies |
| <mark style="color:blue;">All</mark>        | All conversations within the current channel scope (default tab)                                   |

The number beside each tab name is its conversation count. Each conversation in the list indicates who is handling it: an “AI” badge means the Agent is replying automatically, a person icon means a human support agent is handling it, a clock icon means it is queued for human support, and a red icon for conversations awaiting support means AI will not reply and a support agent must take over (for example, outside [AI automatic reply hours](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/web-chat/website.md#outside-auto-reply-hours); hover over the icon to see the reason). The assigned support agent's name appears on the right.

### Search and Filter <a href="#search-and-filter" id="search-and-filter"></a>

* **Search**: Enter keywords in <mark style="color:blue;">Search Messages in Conversations</mark>. See [Inbox Search](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/reply/inbox-search.md) for the search scope.
* **Filter**: Click the filter button beside the search box to combine the conditions below. Active conditions appear as tags above the list. Click × on a tag to remove it, or <mark style="color:blue;">Clear Filters</mark> to remove them all.

| Filter                                                       | Description                                                                                                                                                |
| ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="color:blue;">Filter by Status</mark>            | Select one or more of <mark style="color:blue;">In Progress</mark>, <mark style="color:blue;">Resolved</mark>, and <mark style="color:blue;">Queued</mark> |
| <mark style="color:blue;">Filter by Contact</mark>           | Show only a specific contact's conversations; search by name                                                                                               |
| <mark style="color:blue;">Filter by Contact Tags</mark>      | Filter by tags on contacts; supports multiple selections                                                                                                   |
| <mark style="color:blue;">Filter by Conversation Tags</mark> | Filter by tags on conversations; supports multiple selections                                                                                              |

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-b7da470a0c2fb82a881833f7d3293c2e02f69031%2Fconversations-filter-panel.png?alt=media" alt="Filter panel: In Progress, Resolved, and Queued status options, plus dropdowns for contact, contact tags, and conversation tags"><figcaption><p>Filter panel: combine four groups of conditions</p></figcaption></figure>

### Rename and Delete Conversations <a href="#rename-and-delete" id="rename-and-delete"></a>

Hover over a conversation in the list to reveal the “⋯” menu on the right:

* <mark style="color:blue;">Update Status</mark>: Set the conversation directly to In Progress or Resolved (shown when you have assignment permissions).
* <mark style="color:blue;">Rename</mark>: Change the conversation name shown in the list so support agents can identify it easily (for example, “Order #1234 Return”). This does not affect what the contact sees.
* <mark style="color:blue;">Delete Conversation</mark>: Delete it after confirming “Are you sure you want to delete this conversation?” Deletion cannot be undone, and the conversation will no longer appear in search, analytics, or exports. If handling is simply complete, use the “Resolved” status instead.

### Update Status in Bulk <a href="#batch-update" id="batch-update"></a>

Select conversations (or <mark style="color:blue;">Select All</mark> above the list) to display <mark style="color:blue;">Bulk Update Conversations</mark> below. Choose the target status (<mark style="color:blue;">In Progress</mark> or <mark style="color:blue;">Resolved</mark>), then click <mark style="color:blue;">Apply to N Conversations</mark>. The numbers of successful and failed updates appear when the operation finishes.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-77f2e24b1238e4f6b498796fbd71df02decd777b%2Fconversations-batch-update.png?alt=media" alt="After selecting two conversations, the list shows 2 selected and a Bulk Update Conversations button below; the status panel offers In Progress, Resolved, and Apply to 2 Conversations"><figcaption><p>Bulk status update: select conversations, click “Bulk Update Conversations,” choose a status, and apply</p></figcaption></figure>

## Reply and Manage Automatic Replies <a href="#reply-and-auto-reply" id="reply-and-auto-reply"></a>

Open a conversation and reply directly in the input box below. Messages are sent through the customer's original channel (web chat, LINE, Teams, and so on).

The robot icon toggle above the right side of the input box controls <mark style="color:blue;">Automatic Replies</mark> for this conversation:

* **On**: The Agent automatically replies to new customer messages. Channels default to automatic replies all day, every day. If the channel's automatic reply hours have been changed, replies are sent only during those hours. See [Website: Automatic Reply Settings](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/web-chat/website.md#auto-reply-settings) for scheduling.
* **Off**: The Agent stops replying to this conversation, and human support agents reply manually.

{% hint style="warning" %}
Sending a message alone does not turn off automatic replies. If automatic replies are on, the Agent will still answer the customer's next message, potentially overlapping with your reply. When you send a message in a conversation that no human has taken over, a <mark style="color:blue;">Before Sending</mark> reminder appears first. Choose <mark style="color:blue;">Take Over and Send</mark> (recommended) or <mark style="color:blue;">Send Directly</mark>. See [Human Support Handoff and Replies](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/human-handoff-operations.md#unclaimed-send-guard).
{% endhint %}

### Undelivered Messages <a href="#delivery-failed" id="delivery-failed"></a>

In LINE, Messenger, and Instagram conversations, if the platform rejects a message sent by you or the Agent, <mark style="color:blue;">Not Delivered: Reason</mark> appears in red below the message bubble and remains after refreshing. Successfully sent messages have no indicator. Common reasons:

| Display                                                            | What to do                                                                                                                                                                                                                                                                                                                            |
| ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| LINE monthly message quota exhausted                               | Check the [Monthly Message Quota](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel/line.md#line-monthly-quota) on the LINE channel's settings page, then upgrade your plan in LINE Official Account Manager or wait for next month's reset. Neither AI nor human replies can be sent while the quota is exhausted |
| Too many LINE messages sent in a short time; try again later       | Send again later                                                                                                                                                                                                                                                                                                                      |
| Meta's 24-hour reply window has expired                            | Messenger/Instagram only allow replies within 24 hours of the customer's last message. Wait for the customer to message again                                                                                                                                                                                                         |
| Recipient has blocked you or cannot currently receive messages     | The Messenger/Instagram customer has blocked the page or cannot currently receive messages, so delivery is unavailable                                                                                                                                                                                                                |
| Message content or format not accepted by the platform             | Check the content (for example, excessive length or unsupported formatting), then send again                                                                                                                                                                                                                                          |
| Platform temporarily unable to process the message; sending failed | A temporary platform error occurred; send again later                                                                                                                                                                                                                                                                                 |
| Sending failed (original message)                                  | The parentheses contain the platform's original error. Use the reason to decide whether to revise the content before sending again                                                                                                                                                                                                    |

There is currently no “Resend” button. Re-enter and send the message when needed.

For example, a support agent replies on Monday morning to a customer who messaged on Messenger on Friday evening. “Not Delivered: Meta's 24-hour reply window has expired” appears below the message. Knowing the customer will not receive it, the support agent contacts them by phone or Email, or waits for another customer message before replying.

In group conversations (such as LINE groups), a mention icon toggle also appears above the input box. Hovering over it shows “Respond only when @mentioned in the group.” When enabled, the Agent only responds when @mentioned in the group; when disabled, it responds to all group messages.

## Take Over, Transfer, and Return to AI <a href="#handoff-actions" id="handoff-actions"></a>

The status bar above the conversation content shows who is currently handling the conversation and provides actions based on its status:

| Status bar display                                                                                                                                                                                                                                                                                              | Available actions                                                                                                                                                                                                                           |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| <mark style="color:blue;">AI Agent Handling</mark>, <mark style="color:blue;">Outside AI Reply Hours · Awaiting Support</mark>, <mark style="color:blue;">No AI Assistant Linked to Channel · Awaiting Support</mark>, <mark style="color:blue;">No Support Agent Assigned</mark>, or waiting for human support | Click <mark style="color:blue;">Take Over</mark> to assign the conversation to yourself and stop AI automatic replies, or <mark style="color:blue;">Assign Support Agent</mark> to assign it to a specific colleague                        |
| <mark style="color:blue;">You Are Handling This Conversation</mark>                                                                                                                                                                                                                                             | Click <mark style="color:blue;">Resolve</mark> to close it, or <mark style="color:blue;">Transfer</mark> to a colleague. In the <mark style="color:blue;">Mine</mark> tab, you can also <mark style="color:blue;">Return to AI Agent</mark> |
| Another colleague is handling it                                                                                                                                                                                                                                                                                | <mark style="color:blue;">Transfer</mark> to another support agent                                                                                                                                                                          |
| <mark style="color:blue;">This Conversation Is Resolved</mark>                                                                                                                                                                                                                                                  | Click <mark style="color:blue;">Reopen</mark>                                                                                                                                                                                               |

In the <mark style="color:blue;">Unassigned</mark> tab, you can also hover over a conversation and click the assignment icon to assign it to a specific support agent. The selection dialog shows each colleague's online status, availability, and number of conversations in progress. See [Human Support Handoff and Replies: Transfer and Return to AI](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/human-handoff-operations.md#transfer-and-return).

If a customer sends another message in a resolved conversation, it automatically reopens and returns to AI automatic replies, and the previous support agent assignment is cleared.

For replying after takeover, availability and time off, transfer rules, and customer-facing notices, see [Human Support Handoff and Replies](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/human-handoff-operations.md). For handoff conditions and assignment rules, see [Human Support Handoff Settings](https://docs.maiagent.ai/maiagent-user-guide/en/build/conversation-settings/human-handoff.md).

## Conversation Details <a href="#conversation-details" id="conversation-details"></a>

Click <mark style="color:blue;">Details</mark> above the conversation to expand its information on the right:

* <mark style="color:blue;">Handoff Reason</mark> (if provided), <mark style="color:blue;">Contact Tags</mark> (created in [Contacts](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/contact.md#contact-tags)), and <mark style="color:blue;">Conversation Tags</mark> (created in the channel's [Conversation Tag Management](https://docs.maiagent.ai/maiagent-user-guide/en/build/conversation-settings/conversation-tags.md))
* <mark style="color:blue;">Conversation Summary</mark>: If [Conversation Analysis](https://docs.maiagent.ai/maiagent-user-guide/en/build/conversation-settings/conversation-analysis.md) is enabled for the channel, click <mark style="color:blue;">Analyze Conversation</mark> beside the conversation tags to generate one. You can edit the summary manually; see below
* <mark style="color:blue;">Location Information</mark>: IP address, recorded time, and a copyable <mark style="color:blue;">Conversation ID</mark>
* <mark style="color:blue;">Conversation Satisfaction</mark>, <mark style="color:blue;">Credit Usage Summary</mark> (see below), <mark style="color:blue;">Conversation Timeline</mark> (handoff, takeover, return, and other events), and <mark style="color:blue;">Contact Information</mark> (Email, phone, and the contact's [Custom Properties](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/contact.md#custom-properties))

The robot icon in the title bar opens <mark style="color:blue;">Conversation Copilot</mark>. See [Support Copilot](https://docs.maiagent.ai/maiagent-user-guide/en/serve/copilot.md).

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-2a960c9ffe1d5a9e98cf54b9ddd6e6d1f16c711d%2Fconversations-details-panel.png?alt=media" alt="Conversation details panel: handoff reason, contact tags, conversation tags, location information (IP address, recorded time, conversation ID), and conversation satisfaction"><figcaption><p>Conversation details: handoff reason, tags, location information, and conversation ID; scroll down for conversation satisfaction, Credit Usage Summary, and the conversation timeline</p></figcaption></figure>

### Edit the Conversation Summary <a href="#edit-summary" id="edit-summary"></a>

AI-generated summaries may be incomplete. Support agents can correct them directly:

* Click <mark style="color:blue;">Edit Summary</mark>, make changes, and save. Colleagues who take over later will see the updated version.
* Click <mark style="color:blue;">Edit History</mark> to expand all versions. The first version is labeled <mark style="color:blue;">AI Analysis</mark> (the original AI draft), and the displayed version is labeled <mark style="color:blue;">Current</mark>. Click <mark style="color:blue;">Restore</mark> on another version to switch back to it. If no edits have been made, “No edit history yet” appears.
* Clicking <mark style="color:blue;">Analyze Conversation</mark> again generates a new AI version. Previous versions remain in the edit history.

### Credit Usage Summary <a href="#credit-summary" id="credit-summary"></a>

<mark style="color:blue;">Credit Usage Summary</mark> adds up the Credits used by each AI reply turn in the conversation, helping you assess costs per conversation:

| Item                                                                                                                                     | Description                                                                                                                 |
| ---------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Total                                                                                                                                    | Total Credits used across all turns in this conversation                                                                    |
| <mark style="color:blue;">Turns</mark>                                                                                                   | Number of completed AI reply turns                                                                                          |
| <mark style="color:blue;">Average</mark> / <mark style="color:blue;">Median</mark> / <mark style="color:blue;">Standard Deviation</mark> | Mean, median, and spread of usage per turn; a high standard deviation indicates that some turns were particularly expensive |
| <mark style="color:blue;">Highest</mark> / <mark style="color:blue;">Lowest</mark>                                                       | Highest and lowest usage in a single turn; **click to jump to that turn's message**                                         |
| Category bar                                                                                                                             | Proportions by category, including embeddings, LLM input, LLM output, Cache reads, Cache creation, and tools                |

Expand <mark style="color:blue;">Advanced Analysis</mark> for:

* <mark style="color:blue;">Top 3 Most Expensive Turns</mark>: Lists the three most expensive turns; click to jump to the message.
* <mark style="color:blue;">Cumulative Credit Usage</mark>: A curve of usage accumulated over turns, showing whether usage is evenly distributed or concentrated in a few turns.
* <mark style="color:blue;">vs. Organization Average (30 Days)</mark>: Compares average usage per turn in this conversation with the organization's average across all conversations with at least 3 turns in the past 30 days. “No organization baseline data yet” appears if this conversation has fewer than 3 turns or the organization lacks sufficient data.
* <mark style="color:blue;">Export CSV</mark>: Download Credit usage details for each turn in this conversation.

For Tokens, processing time, and execution steps for a single reply turn, open the conversation details page in AgentOps. See [Automated Evaluation and Agent Monitoring](https://docs.maiagent.ai/maiagent-user-guide/en/build/agent-ops/evaluations.md#monitoring-field-descriptions). For Credit pricing, see [Credits](https://docs.maiagent.ai/maiagent-user-guide/en/others/credits.md).

## Related Pages <a href="#related-pages" id="related-pages"></a>

| Page                                                                                                                                    | When to use it                                                                                                       |
| --------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| [Conversation Viewer](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/reply/conversation-viewer.md)              | Review conversation content, tool usage, and cited sources message by message for quality checks or troubleshooting  |
| [Inbox Search](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/reply/inbox-search.md)                            | Find specific conversations by keyword                                                                               |
| [Channel Analysis](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/reply/inbox-analysis.md)                      | Use AI to summarize topics, resolution rates, and improvement suggestions for a single channel over a period of time |
| [Human Support Handoff and Replies](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/human-handoff-operations.md) | Daily takeover, transfer, and return to AI for support agents                                                        |
| [Support Agent Handbook](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/agent-handbook.md)                      | First-day onboarding, daily workflows, and scenario-based procedures for new support agents                          |
| [Contacts](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/contact.md)                                           | Manage contact information and tags                                                                                  |

## FAQ <a href="#faq" id="faq"></a>

### The list is empty and says “There don't seem to be any customer messages in your channels”? <a href="#faq-empty" id="faq-empty"></a>

There are no conversations within the current scope. Check that you selected the correct channel, or complete setup in [Connect a Channel](https://docs.maiagent.ai/maiagent-user-guide/en/build/choose-channel.md).

### I replied to the customer, but the Agent keeps answering? <a href="#faq-ai-still-replying" id="faq-ai-still-replying"></a>

<mark style="color:blue;">Automatic Replies</mark> is still enabled for this conversation. Click <mark style="color:blue;">Take Over</mark> in the status bar, or turn off the automatic reply toggle above the input box. For other takeover and resolution scenarios, see [Support Agent Handbook: Scenarios](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/agent-handbook.md#scenarios).


---

# 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.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/reply.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.
