> 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 showing your customer interactions according to their status

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

The[Inbox](https://app.fullwhere.com/inbox) Fullwhere is the nerve center of the Fullwhere application from which you can manage your customer interactions.

## Views

On the left, different default views let you access your customer interactions according to their state.

In the different views, use the filter **Status** at the top of your screen to display interactions according to their status: 

* **To be processed** (default)
* **Handled**
* **All** (To be handled and Handled)

### **My Inbox**

This is the main, default view. By default, here you find the interactions **To be processed** you are assigned to. So, in this view, with one click you can find the customer interactions that are potentially waiting for action from you: it is your "ToDo" in Fullwhere.

This view is therefore different for each user, based on your [assignment logic](/documentation/documentation-en/automations/workflows.md#assigner-des-utilisateurs), so that everyone can focus on their own scope.

### **Unassigned**

The view **Unassigned** centralizes all interactions that do not yet have an assigned user.

It lets you identify at a glance the interactions that need to be assigned to a user and can help you identify missing assignment logic in your Fullwhere workspace.

### **Scheduled**

The view **Scheduled** displays the interactions for which sending a response is planned.

This view is useful for reviewing messages before sending and carrying out one final check if necessary. It is particularly useful when responses have been prepared with the help of AI.

### **All**

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

### **Pinned**

This view groups the customer interactions you have pinned.

### **Archived**

The view **Archived** groups the interactions you have archived. 

{% 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 of your Inbox (My Inbox, etc.).\
So, if you cannot find a customer interaction in your Inbox, remember to check the Archived view.

Note that archived interactions **are taken into account** in Reports and Analytics.
{% endhint %}

### **Trash**

The Trash view groups 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 cannot find a customer interaction in your Inbox, remember to check the Trash view.

Note that interactions marked as deleted **are not taken into account** in Reports and Analytics.
{% endhint %}

## The tabs

Whatever the Inbox view you are in, your customer interactions are structured around tabs that you find at the top of your screen.\
These tabs structure your customer interactions according to the family they belong to, namely:

* **All** : groups all customer interaction families.
* **Review** : groups your customer reviews (Google, TripAdvisor, TrustPilot, Booking, etc.)
* **Survey** : groups your satisfaction surveys
* **Emails** : groups emails received at addresses connected to Fullwhere
* **Forms** : groups requests received via your Forms connected to Fullwhere
* **Messages** : groups messages received on Instagram, Facebook and WhatsApp Business


---

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