Blog

Shared mailbox rules

What is worth automating on a shared address in Outlook and Gmail, the two limits you will hit, and what to do about the thread that goes quiet on day three.

Two people are answering [email protected], and one of them just asked why nobody set up a rule for this. What a rule can do depends on where the mailbox lives: “a shared mailbox rule” means three different things in Outlook, Gmail and a shared inbox tool.

Set rules for routing, for keeping automated mail out of the queue, and for flagging what nobody picked up. Do not set one expecting it to answer a customer. In Gmail a filter has no reply action, in Outlook a shared mailbox can only send automatic replies with an admin’s help, and in Chirp no rule can send mail at all. Every one of them also runs on arrival, so the thread that goes quiet three days later is still your problem.

What a shared mailbox rule can do on each platform

Outlook shared mailbox Gmail filters Chirp rules
What a rule is An inbox rule on the mailbox A filter in whichever account holds the address A rule on the shared inbox
Trigger A message arrives and matches the conditions A message arrives and matches the search operators A message arrives and matches the conditions
Actions Move, categorize, flag, mark read, delete, forward, redirect, reply with a template Label, archive, delete, mark read, star, forward, never send to spam Close, tag, assign, snooze, write a draft
Assign to a person No No Yes
Send mail Reply with a template only, on a Microsoft 365 mailbox No. The vacation responder is not a filter No. No rule has a send action
Where it stops A client-only rule runs only while its creator has Outlook open A filter cannot reply, assign or escalate A rule cannot send

Three facts decide most of this. Outlook rules are applied to incoming messages in the order they appear in the list (Manage email messages by using rules). A Gmail filter matches the same operators as a search, so from:, to:, subject: and has:attachment all work as conditions (Refine searches in Gmail). And a filter’s action list is exactly: label, archive, delete, mark as read, star, forward, never send to spam (Create rules to filter your emails).

Where you create the rule matters as much as the rule. The three Google arrangements are how to set up a shared inbox in Gmail, and shared mailbox versus distribution list covers the address type you inherited.

Route by keyword or sender to a folder or a person

Two routing rules earn their place on nearly every support address.

A keyword lane. One condition for the mail that needs a different person or a different day: the words invoice, refund, cancel, security or your product’s own nouns. In Gmail that is a filter on subject:invoice OR subject:refund that labels and archives. In Outlook it is the same words as a rule condition that moves to a folder.

A named customer lane. One rule per account that pays you real money or writes often. The sender goes to a folder, and in Chirp to an assignee.

Keyword rules route by topic and sender rules route by account, and Gmail’s filter actions include no assign, so routing to a person needs a different tool. If you were heading for a personal folder, read Gmail delegation versus a shared inbox first: a delegate sees the thread without seeing an owner on it.

What is worth automating on a shared address

The useful question is not what can be automated but what should be. A rule that saves a click is a rule someone has to maintain.

Automate Do it by hand Why
Routing a keyword to a folder or a label Deciding what the message means A condition matches words, not intent
Sending receipts, notifications and no-reply mail out of the queue Answering anything a person wrote Automated mail is the largest source of queue noise
Applying a tag or category on arrival Assigning an owner Tags are deterministic, judgement is not
Keeping a copy for the record Deciding the reply Nothing a rule can say will be the reply

The noise rule is the one teams skip. Receipts, password resets and build notifications arrive at a support address in bulk, and each one looks like a customer until someone opens it. Route them to a folder on arrival rather than reading them and deleting them, and auto-generated email and do-not-reply addresses covers the class of mail to catch.

A starting set for [email protected], one rule each:

1. from:no-reply@ (plus your domain)   -> label Receipts, skip the inbox
2. subject:invoice OR subject:refund  -> label Billing
3. subject:security OR subject:breach -> label Security, assign a named agent
4. from:@acme.example, named account  -> label BigCustomer, assign an agent
5. has:attachment                     -> label Attachments, leave unread
6. to:billing@ (plus your domain)     -> label Billing
7. everything else                    -> leave in the inbox

Acknowledge receipt once per thread, not once per message

A Gmail filter cannot send an acknowledgement, because there is no reply action in the list. The auto reply is a separate feature: the vacation responder, turned on in Settings under General (Send an automatic reply when you’re out of office).

Turn it on once and leave it on. In most cases Google sends it only the first time a person messages you, and the exceptions are narrow: the same person writing again after four days while the responder is still on, or you editing the reply.

Per-message acknowledgement is the failure to avoid. An Outlook rule that answers every arrival turns a four-message thread into four copies of the same paragraph, and Microsoft’s own automatic replies send once to each person who emails you during your absence (Send automatic out of office replies from Outlook).

On a Microsoft 365 shared mailbox that switch belongs to an admin rather than to you (Open and use a shared mailbox in Outlook). The admin sets it on the shared mailbox in the admin center, or with Set-MailboxAutoReplyConfiguration (How to set automatic replies on a user’s mailbox).

The wording is a separate job once the trigger is agreed: out of office message examples has that part. An acknowledgement is not a first response, which is the distinction what first response time measures exists to make.

Flag anything unassigned after a set time

No rules engine has a time condition, so “flag anything unassigned after three days” is not a rule you can build. Not in Outlook, and not in Gmail. The trigger is always arrival.

What each platform gives you instead:

Want Outlook Gmail
A list of unowned threads A folder or a search on category A label, or label:unread -label:handled
Something that shouts on day three Nothing that runs at matching time A Google Apps Script on a time trigger, or a person
A delegate who sees mail sent to somebody else The “Email received for others” rule, in new Outlook Not available

On the Google side, “somebody else’s mail” means a Google group running as a collaborative inbox, where a member takes a conversation and assigns it to somebody.

The honest fallback for both platforms is the same habit: deliver into a folder, leave it unread, and open the oldest ten every morning before you open the new mail.

Rules run on arrival, and that is the whole trigger

This is the limit that matters most, and the one no rule fixes. Every engine above evaluates a message once, when it arrives. A thread answered at 09:00 and then left quiet, because the answer was “we will look into it”, is invisible to all of them three days later. That thread is usually what the reader came here for.

Three things to do about it.

Rotate a queue view. Someone reads the top of the unread list, oldest first, every working day. This works, and it costs ten minutes a day and one person who owns it.

Escalate in the second tool. Open an issue for anything that needs work, and let the issue’s own state be the reminder. The thread sits in the mailbox; the tracking happens where the work happens.

Put a layer in front of the mailbox that holds an owner and an age. This is the only one that scales past a few hundred messages a month, and it is the difference between a mailbox and a queue. Shared inbox versus help desk is the choice of layer, and it is worth making before you write a tenth rule.

Where a shared inbox changes the rule set

Chirp is a shared inbox for small software teams that track their work in Linear. Rules close, tag, assign, snooze and write drafts, and no rule has a send action, so the acknowledgement problem above disappears at the point of the rule: a draft only ever fills an empty reply box, and a person decides whether it goes.

The arrival-only trigger is a limit here too. What changes is the queue. Snooze a thread until done, and when every linked issue is Done or Canceled the thread comes back with a drafted reply that names the issue. The Issues view (g i) orders linked issues by how many customers are waiting, so the thread that went quiet is on a list with an owner and an age rather than in a folder nobody reopens.

Chirp connects to Gmail, Google Workspace or IMAP, keeps the mailbox as the source of record, and sets access per inbox with the roles Admin, Agent and Viewer. Which inbox each person sees is not something a rule decides.

Next step

A promise about reply time needs an owner and an age, and rules supply neither. What a support SLA is works through what to commit to and what to measure instead.

FAQ

What are the rules for a shared mailbox?

There are no default rules. A shared mailbox starts empty, and the rules worth adding are routing by keyword or sender, keeping automated mail out of the queue, and a way to surface anything nobody picked up.

Can I set an automatic reply on a shared mailbox?

On a Microsoft 365 shared mailbox, only an administrator can set it up (Open and use a shared mailbox in Outlook). In Gmail there is no automatic reply attached to a filter, so the vacation responder is the only option, and it belongs to the account that holds the address.

Why are my shared mailbox rules not working?

Check the scope first. A rule marked client-only runs only while its creator has Outlook open, and Microsoft’s guidance is to create it again under Settings, Mail, Rules while the shared mailbox is open, which produces a server-side rule (Microsoft Q&A, Manage email messages by using rules). In Gmail, a filter you created just now has not touched anything that already arrived.

Do Gmail filters work on a shared mailbox?

Yes, in the account that holds the address. A filter can label, archive, delete, mark read, star, forward or never send to spam, and it cannot reply, assign or escalate.