Email triaging with rules
Create dynamic rules to triage the inbound emails received by your aliases. Add custom keyword conditions and actions.
By default, aliases have a rule to catch all inbound emails.
Custom rules requires a premium account.
Example uses
- Bypass the digest to get important emails straight away
- Forward support requests to the relevant team
- Ignore certain emails altogether
Rule conditions
Every rule must have a condition. You can add as many rules to an inbox alias as you require to build your workflow.
Choose from the following properties of your inbound email in order to build a rule.
- Subject line
- From address
Available comparisons
| Option | The property of the inbound email must |
|---|---|
| Contains | Contain the value |
| Does not contain | Does not contain the value |
| Ends with | End with value exactly |
| Equals | Match exactly |
| Does not equal | Does not match exactly |
| Is blank | Be blank |
| Matches | Match the provided regex |
| Starts with | Start with value exactly |
Catch all
Alternatively, match all inbound emails by using the catch all option.
Actions
When your alias receives an inbound email, it is checked against your rules. When the condition is met, one of the following actions are taken.
| Action | The inbound email |
|---|---|
| Bypass | Skips the alias default digest and is sent to you immediately |
| Forward to | Is immediately forwarded to the provided email address |
| Ignore | Skips the alias default digest completely and is ignored |
| Use default pace | Is stored and sent to you in the next digest |
Stop cascade
Rules are evaluated in order and can be drag and dropped into the workflow required.
When a rule passes (evaluates as true), you have the option to "stop" any subsequent rules.
