> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/appendix/brokerage-set-up/transaction-management-deals/setting-up-deals/creating-checklists/required-vs.-optional-and-inbox-routing.md).
# Required vs. Optional & Inbox Routing
Every checklist item can be flagged as **Required** or **Optional**, giving Admins control over compliance expectations. In addition, each item routes to a specific **Inbox**, which determines which admin or team is responsible for reviewing it when an agent submits it for approval. This setup ensures both **compliance clarity** and **workflow efficiency**.
### **Marking Items as Required or Optional**
**Step 1:** Navigate to **Deals Settings > Checklists** and open your checklist.
**Step 2:** In the **Required?** column, check the box to mark an item as **Required**.
* ✅ Required → Must be submitted by agents before the deal can progress.
* ⬜ Optional → Not mandatory, but available if applicable.
{% hint style="warning" %}
Marking items correctly ensures that agents cannot skip documents critical for compliance, while keeping flexibility for deal-specific variations.
{% endhint %}
### Routing Checklist Items to Inboxes
Locate the **Inbox** field beside each checklist item.
By default:
* Listing checklist items route to the **Listing Inbox**.
* Contract checklist items route to the **Contract Inbox**.
To override, click the **Inbox dropdown** and select or create a custom inbox.
* Example:
* MLS Printout → MLS Compliance Inbox
* Termination Notice(s) → Escrow Release Inbox
{% hint style="warning" %}
Inboxes act like **review queues**. Each can be monitored by a dedicated admin or team (e.g., Compliance, Escrow, Accounting), ensuring tasks are handled by the right people.
{% endhint %}
---
# 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://help.rechat.com/appendix/brokerage-set-up/transaction-management-deals/setting-up-deals/creating-checklists/required-vs.-optional-and-inbox-routing.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.