> For the complete documentation index, see [llms.txt](https://claimlane-docs.gitbook.io/claimlane-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/when-and-how-to-work-with-the-combined-inbox-view.md).
# When and How to Work with the Combined Inbox View
#### **Introduction**
The **Combined Inbox** makes it easier to manage claims that involve both consumers and suppliers, all from a single view.\
Instead of switching between two separate tickets, Claimlane combines them into one unified thread, giving you a **complete overview of the issue** and a **single overall status**.
In the example above:
* **Backpack** → A new claim raised by a consumer that hasn’t been forwarded to a supplier yet.
* **Rebel Shoe** and **Test** → Claims already forwarded to suppliers, which means both the consumer and supplier tickets are connected in one combined view.
#### **Why Use the Combined Inbox?**
The Combined Inbox is ideal for retailers who want to:
* Work with **one overall status per issue** instead of managing separate statuses for consumer and supplier sides.
* **Avoid switching** between tickets and see all communication in one place.
We recommend using this view if your workflow consistently handles **a single claim status across both parties**.\
However, keep in mind that when using the combined flow, **both the supplier and consumer tickets share the same status** — updating one will automatically reflect in the other.
#### **How It Works on the Ticket Itself**
Functionally, the individual tickets behave the same as in the split inbox.\
The key difference is the **simplified navigation** — you can easily **toggle between the consumer and supplier views** from the top navigation bar.
You can also quickly share information between the two. For example, if a customer sends additional photos of a product fault, you can **forward that message directly to the supplier chat**.\
Simply hover your mouse over the message and select the forward option.
#### **In Summary**
The Combined Inbox view gives you a cleaner, more efficient way to manage claims that involve both consumers and suppliers.\
By merging tickets into one view, you reduce manual navigation, keep statuses consistent, and maintain better context throughout your communication, all without leaving your Claimlane workspace.
---
# 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://claimlane-docs.gitbook.io/claimlane-docs/troubleshooting-and-faqs/when-and-how-to-work-with-the-combined-inbox-view.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.