A shared inbox workflow is the set of agreed rules that decides who owns each incoming message, how fast it gets an answer, and when it moves to someone else. The software matters less than those rules. For a service business, the rules also need to cover more than email: customers now call, text, message on WhatsApp and use web chat, and a queue that only sees email leaves most of that work outside the process. This guide covers the email basics, the rules worth writing down, and how to extend the same workflow to every channel.
WattleBring Every Customer Message Into ViewWattle brings calls, SMS, website chats, and WhatsApp into one inbox, with staff able to take over conversations when needed.VisitTL;DR
- A shared inbox answers “who handles this message?” A unified inbox answers “what should I look at first?” Most teams need the first one for team addresses like hello@ or accounts@.
- Every message needs one named owner, a visible status (New, Claimed, Waiting, Done) and an agreed response time.
- Set rules in a sensible order: filter spam, tag by topic, apply time goals, then assign. Write down escalation paths for complaints, payments and sensitive personal information.
- Phone calls, SMS and chat are part of the same workflow. Missing them is where most bookings and enquiries are lost.
- Our AI front desk, Wattle, brings calls, web chat, WhatsApp and SMS into one inbox and hands complex conversations to your staff.
Table of Contents
- What a shared inbox workflow actually is
- The five rules every shared inbox needs
- Setting up rules in the right order
- Escalation: what should never sit in the general queue
- Why email-only workflows miss the work
- Bringing calls, SMS, chat and WhatsApp into the same workflow
- A worked example: a small plumbing business
- Our perspective
- Put your workflow on every channel
- FAQ
- Sources
What a shared inbox workflow actually is
A shared inbox is a mailbox that several people work on together. In Microsoft 365 it is a shared mailbox, which lets a group monitor and send email from a common address such as info@. Google Workspace offers a similar collaborative inbox. Messages sit in one place and replies go out as the shared address, not from one person’s name.
That is the tool. The workflow is what the team does with it. An Australian IT provider notes that a shared inbox suits customer service, support, HR, finance and community teams but only works when there are clear processes for who checks when and how emails are flagged or closed. Without them, a shared inbox becomes a place where everyone assumes someone else replied.
Shared inbox versus unified inbox
The two terms get mixed up. A shared inbox is about a team working on one address. A unified inbox is one view for a single person who wants to see several accounts or channels together. A useful rule of thumb: count people and places. Many people on one address means a shared inbox. One person across many accounts means a unified inbox.
For a customer-facing business the more valuable idea is a combination: one team queue where every channel lands, with each conversation assigned to a person. That is the version of “unified” that reduces dropped enquiries, because the customer’s history follows them from a phone call to a follow-up text.
The five rules every shared inbox needs
Before adding labels, filters or automation, agree on these. They take an hour to write and prevent most of the problems teams complain about.
1. One named owner for the inbox, and one for each message
An Australian IT guide says every shared mailbox needs a named owner who monitors incoming messages, keeps rules and access current, and reviews whether the inbox still suits the business. Go one step further and give each message an owner too. “Forwarded to the team” leaves responsibility vague. A name and a next-review time does not.
2. Four visible statuses
One Australian team-mailbox guide recommends four states: New, Claimed, Waiting and Done. New means nobody has touched it. Claimed means someone is on it, so nobody else replies. Waiting means you are waiting on the customer or a colleague. Done means closed. The Claimed state is what prevents duplicate replies, the most embarrassing shared inbox failure.

3. A written speed agreement
The same guide suggests a simple agreement, such as urgent requests answered the same morning and general questions within a working day. Pick targets you can actually meet, write them per message type, and review them monthly. A target nobody can hit teaches the team to ignore targets.
4. A daily duty person
Rather than everyone checking constantly, name one person each day to sweep New messages at agreed times, for example first thing, after lunch and before close. The duty person assigns, answers quick ones and flags urgent ones. Everyone else works assigned items in focused blocks.
5. A backup and a handover routine
A triage playbook from a consultancy makes the point that a shared inbox needs a named owner per coverage period, a backup and a decision route. At handover, the incoming person should read back and accept unresolved items. That one habit closes the gap where leave, sick days and shift changes lose messages.
Setting up rules in the right order
People searching for shared inbox rules usually want to know whether automation is possible and what order to put it in. It is possible, and order matters because rules run top to bottom.
In Microsoft 365, users with Full Access to a shared mailbox can create inbox rules. One administrator guide recommends building them in Outlook on the web, because those rules run on the server around the clock, whereas desktop rules only run while the app is open. The same guide recommends using “stop processing more rules” and keeping the order deliberate to avoid conflicts.
A sensible starter sequence looks like this:
Order Rule Why it goes here 1 Move obvious spam and automated notices out of the main view Keeps the queue honest 2 Tag by topic: quotes, bookings, billing, complaints Lets the right person see the right work 3 Apply a response-time goal per tag Sets the clock before anyone opens it 4 Send an after-hours acknowledgement Tells the customer when to expect a reply 5 Assign what remains, for example by rotation Assigns last so tags and time goals already existAssigning last is the key. If you assign first, messages land on someone’s plate without a category or a deadline.
Assignment rules that stay fair
Rotation is simple, but it needs limits. Cap how many open conversations one person can hold, and skip people who are away. We cover this in more detail in our guide to conversation assignment rules, including round robin, limits and SLAs.
Escalation: what should never sit in the general queue
Some messages should leave the normal flow straight away. A practical list for most service businesses:
- Complaints and threats of legal action
- Requests to change payment or bank details
- Unusual pricing or contract changes
- Anything containing health, financial or identity information
- Safety issues or urgent faults
Define urgency by business impact, such as revenue at risk, a blocked customer or a legal exposure, not by how upset the sender sounds. Write down who receives each category and who backs them up.
Privacy comes with the territory
In Australia, the Privacy Act 1988 may require you to protect customers’ personal information from loss, misuse and unauthorised access. If it covers your business, you must follow the Australian Privacy Principles. In practice, that means limiting who can open sensitive messages, deciding which systems hold them and not forwarding them around informally. Build a restricted category for sensitive mail and name its owner.
Why email-only workflows miss the work
A tidy email queue can still lose business. Many service enquiries never arrive by email. They come as missed calls, texts and WhatsApp messages. When those sit in separate places, with different people checking them at different times, you get the same problems the shared inbox was meant to solve: no owner, no status, no history.
The biggest gains come when enquiries connect to the systems that act on them. An Australian IT consultancy makes the point that the tool matters less than the workflow: who owns quotes, bookings, payment queries and complaints, and when an enquiry is logged in the CRM or turned into a follow-up task. A lead that goes into your CRM, a booking that lands in the calendar and a billing question linked to the invoice keep their context from one stage to the next. If your enquiries end up in a CRM, a CRM built for the trade with scheduling, invoicing and client communication in one place shows what this connection looks like.
We have written separately about connecting phone calls to a CRM for Australian IT teams and about logging calls server-side so none go unmatched.

Measures worth tracking
Keep the dashboard small. Four numbers cover most needs:
- First response time by channel
- Time to resolution by category
- Open items older than your target, which is your backlog
- Share of conversations handed over to a person, which tells you whether your rules match reality
Review them weekly for the first month, then monthly. If one category keeps breaching its target, the fix is usually ownership or staffing for that category, not another filter.
Bringing calls, SMS, chat and WhatsApp into the same workflow
The rules above do not change when the channel changes. Every conversation still needs an owner, a status, a response time and an escalation path. What changes is who can handle the volume. Phone calls arrive when your team is on a job, in a meeting or off shift, which is why they are the hardest channel to put in a queue.
This is where an AI front desk fits. Wattle answers calls, asks the customer the relevant questions, books appointments and passes the conversation into one workspace alongside web chat, WhatsApp calling and SMS. Your team sees a single inbox with transcripts and recordings, not four separate tools. You choose how each agent behaves: conversational for flexible calls, or scripted for tightly controlled flows. You also set when a conversation is handed to a person.
Four practical ways to apply your inbox rules to the phone:
- Business hours. Decide what happens when you are open, closed and on holidays. Our guide to business hours routing walks through the setup, and the after-hours answering guide for Australia covers the evening and weekend gap.
- Escalation. Treat the same categories as email: complaints, payment changes and sensitive details go to a person.
- Calendar. Connect your calendar so bookings made on a call appear where your team already works. See how Outlook calendar integration keeps events current.
- Text follow-up. Use SMS for confirmations and quick questions. Our piece on running SMS customer support without extra headcount shows how.
For the wider picture, see our practical guide to support workflow automation for Australian teams.
A worked example: a small plumbing business
Imagine a four-person plumbing business with a hello@ address, a mobile number on the van and a website form. Before any workflow, the owner checks email at night, the office manager picks up calls when she can, and texts go to the owner’s phone.
After a simple workflow:
- All channels land in one queue, with tags: urgent fault, quote, booking, invoice.
- Urgent faults carry a same-morning target and go to the on-call plumber, with the office manager as backup.
- Quotes get a one-working-day target and an owner.
- Invoice queries go to the office manager, and anything involving changed bank details goes to the owner.
- After hours, the caller is greeted, questions are asked and bookings are made, with urgent faults flagged for a person.
- Every conversation shows New, Claimed, Waiting or Done.
Nothing here is complicated. What changes is that every enquiry has a name next to it.
Our perspective
Most shared inbox advice starts with software features. In our experience building for service businesses, it should start with a simple question: what happens to a customer who contacts you at the moment nobody is free?
We designed Wattle around that moment. Calls, web chat, WhatsApp and SMS arrive in one inbox, so your ownership and escalation rules apply to every channel, not just email. You decide how each agent talks, what it is allowed to do and when it hands over to your staff. Your people spend their time on the conversations that need judgement, and the routine ones, like booking a slot or answering an opening-hours question, are handled without them waiting in a queue.
A workflow is only as good as its coverage. If the phone is outside it, so is a large share of your enquiries. We think the right goal is not more inbox features but fewer missed jobs.
Christopher
Put your workflow on every channel
If you already have your ownership and escalation rules written, the next step is extending them to the phone. Wattle plans are Starter at A$99 per month, Pro at A$499 per month and Max at A$999 per month, with the details on the pricing page. You can also try an AI receptionist to hear how a call is handled.
Call handling, outbound calling, transfers and Australian mobile numbers are listed with no published price, so check the pricing page for what applies to you.
FAQ
Can you set up rules on a shared inbox?
Yes. In Microsoft 365, people with Full Access can create inbox rules, and server-side rules built in Outlook on the web keep running when nobody is logged in. Order them so spam filtering and tagging come first and assignment comes last.
What is the difference between a shared inbox and a unified inbox?
A shared inbox is one mailbox that a team works on together, with owners and statuses. A unified inbox is a single view that gathers several accounts or channels. A customer-facing team benefits most when all channels land in one shared queue.
What are the main benefits of a unified inbox for customer service?
The practical benefits are fewer dropped conversations, no switching between tools and a full history for every customer across channels. Those benefits only hold when each conversation also has an owner and a response target.
How do you stop two people replying to the same message?
Use a visible Claimed status and make claiming the first step before anyone replies. Add a daily duty person who assigns new messages so there is no free-for-all.
Sources
- Create a shared mailbox, Microsoft 365 admin
- Email aliases vs shared inboxes: what to use when
- How to Set Up Shared Mailboxes So Nothing Falls Through the Cracks
- Team Mailboxes Without the Confusion: Who Owns Which Email
- Shared Inbox Triage Playbook and Handover Template
- Create and Manage Inbox Rules for Shared Mailboxes
- Protect your customers’ information, business.gov.au
- Should Businesses Use Shared Inboxes? A Practical View
