# Inbox organization

Rules for keeping inboxes clean and conversations grouped.

## Auto-label by customer domain

**Rule type:** Incoming message

Apply labels automatically so your team can filter and track customer conversations.

<div data-with-frame="true"><figure><img src="/files/hJlmg3A29YMMzsDyvlHn" alt="Customer auto-labeling" width="563"><figcaption></figcaption></figure></div>

| Component | Value                           |
| --------- | ------------------------------- |
| Condition | **From** ends with "disney.com" |
| Action    | **Add label(s)** → "Disney"     |

Create one rule per customer.

## Archive on close

**Rule type:** User actions → Conversation closed

Remove closed conversations from everyone's inbox automatically.

<div data-with-frame="true"><figure><img src="/files/pdU1PXm2aVasWOzr3KAg" alt="Auto-archive on close" width="563"><figcaption></figcaption></figure></div>

| Component | Value         |
| --------- | ------------- |
| Condition | (none needed) |
| Action    | **Archive**   |

## Keep specific users out of the loop

**Rule type:** Incoming message

If someone owns a shared account but doesn't work it daily, archive and mark read for them.

| Component | Value                                                                                |
| --------- | ------------------------------------------------------------------------------------ |
| Condition | **Email account** is <help@mycompany.com>                                            |
| Actions   | **Archive for** Phil, **Remove from Team Inbox for** Phil, **Mark as read for** Phil |

Phil won't be bothered by help@ emails even though he owns the account.

## Merge outgoing messages by customer

**Rule type:** Outgoing message

Combine all messages to a customer into one conversation thread.

<div data-with-frame="true"><figure><img src="/files/53sJERKbIVy0n3vJtSgC" alt="Auto-merge conversations" width="563"><figcaption></figcaption></figure></div>

| Component | Value                              |
| --------- | ---------------------------------- |
| Condition | **To** ends with "bigcustomer.com" |
| Action    | **Merge conversation**             |

All future emails to that domain end up in the same thread.

## Notify manager of assignment changes

**Rule type:** User actions → Assignee changed

Keep managers informed when conversations change hands.

<div data-with-frame="true"><figure><img src="/files/I02Iw9QhzfikkQipAdcD" alt="Notify on assignee change" width="563"><figcaption></figcaption></figure></div>

| Component | Value                        |
| --------- | ---------------------------- |
| Condition | **Team** is "VIP Support"    |
| Action    | **Notify user(s)** → Manager |


---

# Agent Instructions: 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:

```
GET https://missiveapp.com/docs/advanced-features/rules/examples/inbox-organization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.