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

# Navigate in the Inbox

{% hint style="success" icon="list-check" %}
**IN BRIEF**

The Fullwhere Inbox is organized into Views that display your customer interactions based on their status

Each view is organized into tabs by interaction type.
{% endhint %}

The [Inbox](https://app.fullwhere.com/inbox) Fullwhere is the central hub of the Fullwhere application, where you can manage your customer interactions.

## Views

On the left, several default views let you access your customer interactions based on their status.

In the different views, use the  **Status**  filter at the top of your screen to display interactions based on their status:&#x20;

* **To do** (default)
* **In progress**
* **Done**
* **All** (To do and Done)

### **My Inbox**

This is the main, default view. By default, it shows the interactions  **To do** that are assigned to you. This view lets you find, with one click, the customer interactions that may require action from you: it serves as your Fullwhere “To-Do” list.

This view is different for each user, depending on your  [assignment rules](https://docs.fullwhere.com/documentation/documentation-en/automations/workflows.md#assigner-des-utilisateurs), so everyone can focus on their own scope.

### **Unassigned**

The  **Unassigned**  view brings together all interactions that have not yet been assigned to a user.

It lets you quickly identify interactions that need to be assigned to a user and can help you spot missing assignment rules in your Fullwhere workspace.

### **Scheduled**

The  **Scheduled**  view displays interactions for which a reply is scheduled to be sent.

This view is useful for reviewing messages before they are sent and performing a final check if needed. It is especially useful when replies have been drafted with the help of AI.

### **All**

The  **All**  view brings together all the interactions you have access to.

### **Pinned**

This view groups the customer interactions you have pinned.

### **Archived**

The  **Archived**  view groups the interactions you have archived.&#x20;

{% hint style="warning" %}
It is important to note that when an interaction is  **archived**, it is only accessible from the Archived view and is no longer visible in the other views in your Inbox (My Inbox, etc.).\
So, if you can’t find a customer interaction in your Inbox, remember to check the Archived view.

Note that archived interactions  **are included**  in Reports and Analytics.
{% endhint %}

### **Trash**

The Trash view groups together interactions that have been marked as deleted, either automatically by our systems or by one of your users.<br>

{% hint style="warning" %}
It is important to note that when an interaction is marked as **deleted**, it is only accessible from the Trash view and is no longer visible in the other views of your Inbox (My Inbox, etc.).\
So, if you can't find a customer interaction in your Inbox, remember to check the Trash view.

Please note that interactions marked as deleted **are not included** in Reports and Analytics.
{% endhint %}

## Tabs

Regardless of which Inbox view you're in, your customer interactions are organized into tabs at the top of your screen.\
These tabs organize your customer interactions by category:

* **All** : groups all customer interaction categories.
* **Reviews** : groups your customer reviews (Google, TripAdvisor, Trustpilot, Booking, etc.).
* **Surveys** : groups your satisfaction surveys.
* **Emails** : groups emails received at the addresses connected to Fullwhere.
* **Forms** : groups requests received through your forms connected to Fullwhere.
* **Messages** : groups messages received on Instagram, Facebook, and WhatsApp Business.
* **Missed calls** : groups conversations started after a missed call.


---

# 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.fullwhere.com/documentation/documentation-en/inbox/navigate-in-the-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.
