Rules are a powerful way to automate your team workflows.
They can be executed when a message (email, SMS, tweet, DM, Facebook message, WhatsApp or Missive Live Chat) comes in or out of an inbox. They can also be defined on some user actions like applying/removing a label, changing the status of a conversation (assigned/closed/reopened) or by posting a new comment.
Missive rules work exactly like Outlook 365 rules and Gmail filters. When all or any of the rule conditions are met, the automated actions defined on the rule are triggered. What's more impressive is you can create complex conditions by nesting them in sub-groups.
To help you understand the potential of this feature, here are a few scenarios:
Label your customer conversations with a dedicated label
Using one label per customer is a nice way to get your team more organized, but doing so manually is error-prone. With a rule, it’s quick and easy. Create a rule like this one for each customer:
Description | ACME auto-labeling |
Conditions | To / Cc ends with “acme.com” |
Actions | Apply label(s) “ACME” |

Make sure all emails get replied to on time
Respect your Service-level agreements (SLA) with time-based rules. You can create as many rules as you need to respect all of your customer's specificities.

Archive and mark conversations as read for specific team member(s)
Sometimes the person importing shared accounts in Missive is not the one that will work with them most of the time. For that person, it can be annoying to receive notifications and see emails from all these accounts. Rules can help by automatically archiving and marking as read these emails for the account owner.
Description | Auto-archive for IT guy |
Conditions | Email account is “help@mycompany.com” |
Actions | Archive (Remove from Inbox) for Phil Remove from Team Inbox for Phil Mark as read for Phil |
Actions | Trash |
With that rule in place, Phil the IT guy won’t get annoyed by emails sent to help@mycompany.com even though he remains the owner of that account.
Automatically add notes to a conversation
Let’s say your staff processes customer orders and that some customers have specific requirements. Using a rule, you can automatically add a note based and who sent the message. This can help your staff deal with that customer’s requirements.
Name | ACME warning note |
Conditions | From ends with “acme.com” |
Actions | Create post “⚠️ ACME will not accept any driver with past felonies at its factory. Make sure to book a driver with no felony.” |

Automatically assign sent emails to authors
If many employees send cold emails to customers using a common shared email account, you might want to auto assign those to the email author. This way, if the recipient replies, only the author will have the reply in their inbox. This can be achieved using an outgoing message rule with the Assign sender action. The conversation will be assigned to the message sender.
Description | Auto-assign sent emails |
Conditions | Email account is sales@mycompany.com” |
Actions | Assign sender |
Here's a list of all the conditions and actions possible for outgoing and incoming messages:
Incoming messages options
Conditions
From | |
To | |
To / Cc | |
Cc | |
Reply to | |
Subject | |
Attachment name | |
Message content | |
Reception time | |
![]() | |
Email account | |
Conversation assignee | |
Watching user | |
Label | |
Conversation state | |
Unreplied and open after | ![]() |
Unassigned and open after | ![]() |
Actions
Apply label(s) | |
Assign user(s) | ![]() |
Add to user Inbox | |
Move to Team Inbox | ![]() |
Share with teammates | |
Notify | Who should be notified? |
Silence notifications | ![]() |
Set conversation color | ![]() |
Create post | |
Archive (Remove from Inbox) | |
Trash | This will trash the conversation for everyone and remove all assignees, snooze times and pins. |
Remove label(s) | |
Remove from Team Inbox | |
Remove to Team | |
Close | This will close the conversation for everyone. |
Mark as read | |
Snooze | ![]() |
Unsnooze | |
Create draft | ![]() |
Send response | ![]() |
Forward message | ![]() |
Merge conversation | ![]() |
Webhook - Learn more |
Outgoing messages options
Conditions
From | |
To | |
To / Cc | |
Cc | |
Subject | |
Attachment name | |
Message content | |
Delivery time | |
![]() | |
Email account | |
Conversation assignee | |
Watching user | |
Label | |
Conversation state |
Actions
Add recipient(s) | |
Assign sender | Conversation will be assigned to the message sender. |
Apply label(s) | |
Assign user(s) | ![]() |
Add to user Inbox | |
Move to Team Inbox | ![]() |
Share with teammates | |
Notify | Who should be notified? |
Silence notifications | ![]() |
Set conversation color | ![]() |
Create post | |
Archive (Remove from Inbox) | |
Trash | This will trash the conversation for everyone and remove all assignees, snooze times and pins. |
Remove label(s) | |
Remove from Team Inbox | |
Remove to Team | |
Close | This will close the conversation for everyone. |
Mark as read | |
Snooze | ![]() |
Unsnooze | |
Merge conversation | ![]() |
Webhook - Learn more |
Here's a list of all the conditions and actions possible for user actions:
On label changes, conversation assigned, closed, reopened and new comments.
Conditions
Added label name | |
Added label name (or parent name) | |
Removed label name | |
Removed label name (or parent name) | |
Added assignee | |
Removed assignee | |
Text | |
Mention | |
Attachment name | |
Comment type | |
Action initiator | |
Conversation assignee | |
Watching user | |
Label | |
Conversation state |
Actions
Apply label(s) | |
Assign user(s) | ![]() |
Add to user Inbox | |
Move to Team Inbox | ![]() |
Share with teammates | |
Notify | Who should be notified? |
Silence notifications | ![]() |
Set conversation color | ![]() |
Create post | |
Archive (Remove from Inbox) | |
Trash | This will trash the conversation for everyone and remove all assignees, snooze times and pins. |
Remove label(s) | |
Remove from Team Inbox | |
Remove to Team | |
Close | This will close the conversation for everyone. |
Mark as read | |
Snooze | ![]() |
Unsnooze | |
Create draft | ![]() |
Send response | ![]() |
Forward message | ![]() |
Merge conversation | ![]() |
Webhook - Learn more |
Last updated on June 23, 2020