> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/understand-matching-rules-and-sender-types.md).

# Understand matching rules and sender types

Matching rules decide which configuration should process an email.

Customer matching rules decide which relation, address, or object should be linked to the new work order.

### Sender types

Use a sender type to decide what part of the email should match:

* **Sender** — match one exact email address
* **SenderDomain** — match a full email domain
* **TitleContains** — match text in the subject
* **TitleEquals** — match an exact subject
* **MessageContains** — match text in the message body
* **Any** — match every email

### When to use each type

Use **Sender** for one known contact.

Use **SenderDomain** for all emails from the same company.

Use **TitleContains** or **TitleEquals** when request emails follow a fixed subject pattern.

Use **Any** only as a controlled fallback.

### Customer and object matching rules

After the email matches a configuration, Mail to WorkOrder can search for the right record.

Common rules include:

* find or add a relation by email or domain
* find or add a relation by phone, street, or debtor number
* find or add an address
* search by object

You can combine multiple rules and let OutSmart try them in order.

### Tips for reliable matching

* start with the most specific rule
* avoid broad catch-all rules too early
* use object search when object references exist in the email

### Frequently asked questions

<details>

<summary>Which sender type is best for company-wide requests?</summary>

Use **SenderDomain** if all requests come from one company domain.

</details>

<details>

<summary>Can I use multiple customer matching rules?</summary>

Yes.

OutSmart can try them in sequence.

</details>

<details>

<summary>What does Any do?</summary>

It matches every email.

Use it only as a last fallback.

</details>

### Related topics

* [**Create and manage mail configurations**](/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/create-and-manage-mail-configurations.md)
* [**Configure forced values and parameters**](/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/configure-forced-values-and-parameters.md)
* [**View logs and monitor limits**](/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/view-logs-and-monitor-limits.md)


---

# 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://knowledge.out-smart.com/marketplace-packages-and-power-ups/power-ups/mail-to-workorder/understand-matching-rules-and-sender-types.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.