> For the complete documentation index, see [llms.txt](https://distance.gitbook.io/distance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://distance.gitbook.io/distance/getting-started/inbox.md).
# Inbox
### **Introduction**
The **Inbox** is your team’s central workspace for managing customer conversations in Distance. It brings together messages from chat, SMS, email, social channels, campaigns, and automations into a single chronological view, allowing you to monitor activity and respond without switching tools.
Each interaction is grouped into a conversation thread by contact, ensuring inbound messages, campaign replies, and automation messages remain part of the same communication history while keeping all customer context in one place.
***
### **Why the Inbox matters**
**Centralize communication**. View and manage all inbound and outbound conversations in one place, regardless of source.
**Maintain visibility and context**. Access full conversation history, customer profiles, and related tickets while responding.
**Support efficient collaboration**. Assign conversations, mark items unread, and organize messages into folders to match team workflows.
**Balance automation and control**. Allow AI agents to handle responses while giving your team the ability to take over instantly when needed.
**Prevent missed follow-ups**. Keep conversations organized and accessible so no inquiry is overlooked or forgotten.
***
### **How the Inbox fits together**
The **Inbox** brings all your customer conversations into a single workspace, keeping context close at hand.
Use [**Inbox navigation and folders**](/distance/getting-started/inbox/inbox-navigation-and-folders.md) to organize messages and keep less relevant conversations out of your main view.
[**Managing conversations with bulk actions**](/distance/getting-started/inbox/managing-conversations-with-bulk-actions.md) lets you quickly assign, move, or update multiple conversations at once, streamlining your workflow.
When a conversation requires a human response, [**taking over conversations from AI agents**](/distance/getting-started/inbox/taking-over-conversations-from-ai-agents.md) pauses automated replies so your team can step in directly.
Each conversation is grouped by contact, ensuring inbound messages, campaign replies, and automation responses remain part of the same communication history.
You can also [**view contacts and tickets from the Inbox**](/distance/getting-started/inbox/viewing-contacts-and-tickets-from-the-inbox.md) to access customer details and related requests without leaving the conversation.
Together, these tools help your team stay organized, responsive, and in control as conversations move between AI and human handling.
---
# 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://distance.gitbook.io/distance/getting-started/inbox.md?ask=&goal=
```
`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.