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

# Inbox Best Practices

Inbox works best when everyone agrees to some standard principles of operating:

* Defining a rough response time helps the author manage the right expectations without getting to the point of constant reminders, or escalations.
* If you think that you will not get to the review within a reasonable time frame, it's recommended to remove attention from yourself and inform the author.
* As an author who has the attention, if your change requires a bit of rework before it can be sent back for review, it's recommended to move the PR to a draft or remove the attention from the reviewers.
* As an author, if you assign an optional reviewer just as an FYI and you don't expect a proper review from the reviewer, you should remove attention from that reviewer.
* Likewise, as a reviewer, if you are assigned an optional review that you do not intend to get to, you should remove attention from yourself.
* Use the **snooze** feature for PRs that are blocked or not immediately actionable, rather than leaving them cluttering your active sections.
* Set up [**custom sections**](/inbox/custom-sections.md) for recurring workflows (e.g., tracking PRs from your team or PRs with specific labels) to reduce manual searching.
* Use **section filters** to exclude noisy authors (like bots) or labels from specific sections, keeping your Inbox focused on what matters.


---

# 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.aviator.co/inbox/best-practices.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.