Shared inbox: sort and route emails automatically
How to sort and route shared inbox emails automatically
You can sort and route a shared inbox such as info@ in five steps: set categories each with an owner, apply simple rules on sender, address and subject first, use AI only for what rules cannot place, produce reply drafts instead of sending automatically, and count misroutes every week. In Microsoft 365, a shared mailbox, inbox rules and Power Automate or Microsoft Graph are enough. In Google Workspace, it is filters, labels and a group used as a collaborative inbox.
This is for SMEs where one or two people empty info@ every morning and forward email to sales, accounts, service and management. For an industry that does this all day, see sorting tenant requests and damage reports.
- Categories
Eight to ten, each with an owner.
- Rules
Sender, address, subject. No AI.
- AI
Only for the rest, only from your list.
- Draft
A person sends.
- Measure
Count misroutes every week.
Step 1: categories that someone owns
A category only counts if a person owns it and it is clear what happens to the email.
Take one normal week of email. Sort it by hand into piles and name the piles. Many SMEs end up with eight to ten categories: order, quote request, supplier invoice, complaint, appointment request, question about an existing invoice, job application, advertising and newsletters, and other. For each category, note the owner and the action: reply, enter, forward or file.
“Other” catches whatever neither rules nor AI can place with confidence. Someone empties that folder every day. If it grows faster than the rest, the categories are wrong.
Decide which category wins in mixed cases. An email that contains both a complaint and a repeat order might always go to service first.
Job applications and medical certificates get their own rule. They go straight to the responsible person and never pass through the AI step. The data protection section explains why.
Step 2: simple rules first
A large share of email can be routed without AI, on sender, recipient address and subject alone.
Supplier invoices come from known addresses. Portal notifications have fixed subject lines. Newsletters share one sender. That needs readable rules, not AI. A second address often helps more than automation: invoices@ for suppliers, info@ for everything else.
In Microsoft 365, info@ is usually a shared mailbox. It needs no licence of its own up to 50 GB; Microsoft gives 25 as the maximum number of people accessing it at the same time. Inbox rules move email or assign categories. In Gmail, filters apply labels. For shared info@ in Google Workspace there are groups used as a collaborative inbox: assign conversations and mark them complete.
| Building block | Microsoft 365 | Google Workspace |
|---|---|---|
| Shared mailbox | Shared mailbox | Group as collaborative inbox |
| Simple rules | Inbox rules, categories | Filters, labels |
| AI step | Power Automate or Microsoft Graph | Apps Script with the Gmail service |
| Assigning | Folder, category or task | Assignment in the group |
Step 3: AI only where the rules fail
The AI only sees email after the rules and chooses from your category list.
What remains is usually mail from customers and prospects: a question that is also an order and a complaint, a quote request without the word “quote”, a forwarded message with three attachments. The AI reads subject and body, chooses a category and states confidence. Below your threshold, the email goes to “other”. In the same step it can attach customer number, order number or requested date as a note.
In Power Automate, the flow starts on new mail in a shared mailbox, calls the AI service, then moves or categorises. Through Microsoft Graph, a program reads shared mailboxes, assigns categories and creates rules. Graph takes more development and gives more control over errors. In Google Workspace, Apps Script with the Gmail service reads threads, manages labels and creates drafts.
Step 4: reply drafts, no automatic sending
At the start, the AI writes drafts. A person sends them.
The draft sits in the drafts folder, in the sender’s language, with the next step: receipt confirmed, question asked, appointment proposed. The owner corrects and sends. That is quicker than writing from scratch and stops a wrong promise reaching a customer.
Allow automatic sending later only in narrow cases, such as a plain acknowledgement with no substantive content. Never automatic: complaints, prices, delivery dates, cancellations, anything legal.
Step 5: route and count the misroutes
An email is routed once it sits with the right person. You only know how well that works after a few weeks.
Routing means moving to a department folder, assigning an Outlook category, assigning the conversation in the Google group, or creating a task. Use the route your people already use. A new ticketing system for twenty emails a day often costs more time than it saves.
Measuring works if you set it up on day one. Whoever moves a misrouted email also sets the category “misrouted”. Once a week count: emails per category, how many wrong, how many in “other”. Decide the acceptable error rate in advance. If a category’s rate has not dropped after a month, take that category out of the AI step.
A made-up example: info@ with orders and complaints
A made-up example: a trading business with around 25 staff, customers across German-speaking Switzerland, info@ on Microsoft 365 sorted by hand every morning until now.
Management sets nine categories with owners. Rules take supplier invoices, freight notifications and newsletters. Accounts gets invoices@, the address on the purchase orders. Customer mail remains.
A customer writes that a delivery was incomplete and asks to reorder in the same sentence. The AI assigns “complaint” (mixed cases go to service), extracts the order number and drafts: receipt confirmed, missing item being checked, answer by the next working day. Service checks the ERP, edits and sends. The reorder goes to sales.
After four weeks the count shows quote requests and orders are often confused. Management merges those two categories for now; sales separates them by hand.
Data protection: processor and data location
The AI service that reads your email processes personal data on your behalf. You remain responsible.
The FDPIC states that under Art. 9 of the Data Protection Act you must satisfy yourself, and secure by contract, that a processor guarantees data security and only subcontracts with your approval. For the AI step: a business account with a contract, no private account, and knowing which providers see the data.
Check three layers for location. Microsoft lists Switzerland as a region where Exchange Online data can be stored. Power Automate depends on the region of its environment. The AI service in the flow may process data elsewhere again.
Job applications and medical certificates stay out of the AI step. This is not legal advice. For health data, or if location is unclear, ask your data protection adviser.
When it is not worth it
If one person empties the inbox in fifteen minutes a day, rules and a second address are enough. If most email is personal conversation with regular customers, it belongs with that person, not in a category. If nobody wants to own the categories, automation just fills folders nobody opens.
Whether the shared inbox is the right first workflow is settled by the four questions in which process to automate first.
When the Process Check fits
If someone sorts info@ by hand every day, that is a typical Process Check case. In 30 minutes on Microsoft Teams we look at the inbox: categories, rules, where AI helps and where it does not. You do not have to show the emails themselves.
Afterwards you have a concrete case, a price range and a rough duration for implementation, in a short written summary. The Process Check is free. Choose a time: book the Process Check.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles
Sort tenant requests and damage reports automatically
Capture tenant requests and damage reports from email, phone and forms, recognise building and urgency, prepare the ticket and the contractor order.
Which process should an SME automate first?
Which process should an SME automate first? Four questions on frequency, pain, a clear end and data. The check is free.
What the Process Check is and what it is not
A free Process Check: a 30-minute call on one workflow, a concrete case and a package size. Not a workshop.