A team manages a shared email inbox well when every thread has one owner, one status, and a reply-by time that both of you can see. That’s the whole method. A thread with a name on it doesn’t get answered twice. A thread with a status doesn’t get forgotten. A reply-by time tells you which one to open first. The tools come second, and for two or three people the ones you already pay for usually cover it.
This guide is the operating model for that address, from ownership through to security. If you haven’t built the shared address yet, team email when the team is two or three people lays out the four ways to do it on Gmail and Microsoft 365. Mechanics below were checked against Google’s and Microsoft’s own help pages on October 4, 2026.
How a team should manage a shared email inbox
Here’s the model in four parts. Each gets its own section below.
- One owner per thread. The first person to pick up a thread says so, in a place the other person can see. From then on it’s theirs until they hand it over.
- A status on everything. Four are enough: new, mine, waiting on them, done.
- A reply-by time for each kind of mail. Agreed in advance, written down, and short enough to keep.
- A triage pass at set times. One person sorts the new mail twice a day, so nobody else has to watch the inbox.
Underneath sit two things that don’t change with the tool. Each person signs in as themselves, and AI does the reading while a person decides what goes out.
Most of the trouble in a shared inbox comes from one gap. Two people can see the same message, but neither can see what the other intends to do about it. Everything here is a way of making intent visible.
One owner for every thread
Ownership means one name per thread, and it’s settled before anyone starts writing. The order matters. Two people drafting the same reply is the most common collision in a shared inbox, and it happens in the minutes between reading and claiming.
Pick one rule for who owns what. Small firms tend to use one of three:
| Rule | How it works | Suits |
|---|---|---|
| By client | Each client has a named person. Their mail goes to that person. | Firms where clients expect the same face every time |
| By kind of mail | One person takes billing and scheduling, the other takes the work itself. | Firms with a clear split between running the office and doing the work |
| By turn | Whoever does the triage pass assigns as they go. | Very small volume, or two partners who both do everything |
Write the rule down in one or two lines. A new hire, or a temp covering a busy month, should be able to follow it on their first morning.
Three habits keep ownership honest:
- Claim before you draft. Take the thread, then write. On a Google Collaborative Inbox that’s the Take action. On an Outlook shared mailbox it’s moving the thread into your folder.
- Hand over out loud. If a thread changes owner, the new owner should see a note saying why. “Over to you, she’s asking about the invoice” saves the new owner reading twenty messages.
- The owner replies. Both of you will read most threads. Only the owner answers, unless they ask for help.
When someone is away, their open threads need a temporary owner. How cover works across a week off is its own subject, covered in covering the inbox during leave.
A triage pass twice a day
Triage is the sort that happens before anyone replies. One person reads the new mail, gives each thread an owner and a status, and moves on. It takes ten or fifteen minutes for a small firm. Doing it at set times, say 9:00 and 2:00, means the other person can stay in their own work without watching the inbox.
The pass is also where the five D’s come in. They’re the classic way to decide what to do with one email, and versions of the list vary. The common set is:
- Delete what nobody needs.
- Do it now, if it takes a couple of minutes.
- Delegate it to the right person.
- Defer it to a set time.
- Designate it, which means filing it where it belongs.
In a team, each D changes a little. Delegate becomes assign, and it’s the D you’ll use most. Defer needs a date the other person can see, or it reads as forgotten. Delete needs a shared rule, since one person’s junk is the other’s client reply.
| The D | Working alone | Working as a team |
|---|---|---|
| Delete | Your call | A shared rule for what can go, so nothing a colleague needed disappears |
| Do | Answer it now | Only if it’s yours, or quick and unclaimed. Then mark it done. |
| Delegate | Forward it | Assign it to an owner in the inbox, with a line of context |
| Defer | Snooze it | Set a status with a date both people can see |
| Designate | File it | File it in the shared folders or labels, never your personal ones |
That last point catches a lot of teams. A thread moved into one person’s private folder vanishes for the other. Keep the shared mailbox’s filing inside the shared mailbox.
Four statuses are enough
A status tells the other person where a thread stands without them opening it. Teams that invent ten statuses stop using them by the end of the month. Four cover almost everything a small firm handles:
| Status | Means | Next move |
|---|---|---|
| New | Nobody has looked yet | The triage pass gives it an owner |
| Mine | Someone owns it and is working on it | The owner replies, or hands it over |
| Waiting on them | The owner replied and the next move is the client’s | The owner checks back on a set date |
| Done | Nothing more is needed | Archive it, so the inbox only shows live work |
“Waiting on them” is the one most teams skip, and it’s the one that loses work. A thread where you asked a client for a document looks finished. It isn’t, and in a shared inbox nobody else knows you’re waiting.
How you show a status depends on what you built the address with.
On Google Workspace, a Collaborative Inbox in Google Groups has some of this built in. Google’s help page says members can take a conversation, assign it to another member, and mark it complete. Members can also search for conversations assigned to them. A conversation can also be marked as a duplicate or as no action needed. These actions live in Google Groups rather than in Gmail, and each needs a group permission set by whoever runs the group. “Waiting on them” has no built-in status, so most teams use a label or a short reply note for it.
On Microsoft 365, a shared mailbox has folders and categories but no assignment or status of its own. The usual answer is a folder per status, plus one folder per person for “mine”. It works when both of you keep to it, and it’s invisible when one of you forgets. That gap is a fair test of whether a plain shared mailbox still fits, and where a shared mailbox starts to strain sets out the rest of its limits.
Reply-by times you can keep
A reply-by time is a promise about how fast someone hears back. Support teams call it an SLA. In a two-person firm it’s simpler: a line you both agree to and can keep on a busy week.
Set it per kind of mail, not one number for everything. Here’s a starting point most small firms can hold:
| Kind of mail | Reply by | Notes |
|---|---|---|
| A client with a deadline in the message | Same business day | Even if the reply is “I have it, answer by Thursday” |
| A new inquiry | Within one business day | A fast first reply wins more work than a perfect late one |
| A routine client question | Within two business days | Acknowledge sooner if the answer will take longer |
| Vendors, invoices, admin | Within a week | Batch these in one sitting |
Three details make it hold:
- The clock starts when the mail lands, not when somebody notices it. The triage pass is what keeps those two close.
- A first reply counts. “Got it, I’ll come back to you by Friday” meets the promise and sets the next one.
- The owner owns the time. If they can’t meet it, they hand the thread over or tell the client, before the time runs out.
Keep these internal at first. Once you’ve held them for a month, you can put them in an engagement letter or on your website.
Stopping the double reply
Two people answering the same client is the collision everyone fears. It’s usually avoidable with three habits.
- Claim before you write. It’s the ownership rule again, and it’s most of the fix.
- Talk inside the thread, not beside it. A note on the thread, or a reply-all to your colleague, keeps the context where the next reader will look. A side message in chat goes stale the moment the thread moves.
- Check the thread before you send. Two seconds to reopen it catches the reply that landed while you were writing.
It also helps to agree how replies are signed. When the client writes back, they should know who they’re dealing with. What the client sees in the From line depends on how you send:
| How you send | What the client sees | Source |
|---|---|---|
| Send As on a Microsoft 365 shared mailbox | Only the shared address, with no sign of who sent it | Microsoft Learn |
| Send on Behalf on a Microsoft 365 shared mailbox | “Your name on behalf of the shared address”, and replies go back to the shared address | Microsoft Learn |
| A Gmail delegate | The account’s address, with the delegate’s own address shown as sender | Gmail Help |
Microsoft notes that when someone holds both Send As and Send on Behalf, Send As is always used. If you send as the shared address, sign every reply with your first name. The client then knows who to ask for, and your colleague knows who answered.
Where AI helps a shared inbox
AI is good at the reading and slow parts of a shared inbox. It’s less suited to the decisions that make a shared inbox work. Split the job that way and it’s useful from the first week.
AI handles well:
- Summaries. A line on each thread tells the triage pass what it’s about without opening it.
- Sorting by urgency. The thread with a deadline rises above the newsletter.
- First drafts. The owner starts from a reply instead of a blank page.
- Spotting the ask. A request buried in the third paragraph becomes something on a list.
A person keeps:
- Who owns it. Ownership is a promise between colleagues, and it holds because a person made it.
- What goes out. A reply to a client carries the firm’s name. Most AI email tools start you on review, where nothing is sent until someone reads it and presses send.
- What gets deleted. The shared rule for what can go stays a human call.
People often ask whether ChatGPT can organize their email. A chatbot can sort and summarize mail you show it, and it can draft replies. Organizing a team inbox is a different job. It needs a record of who owns each thread and where it stands, kept where both people work. A chat window holds that for one person, for one session. Whatever AI you use, it should live where the mail lives.
For a firm that handles client financial or tax data, check what any AI tool does with the mail before connecting it. How AI tools handle your data goes through the questions to ask.
Keeping a shared address secure
A shared address is a bigger target than a personal one. More people can be fooled by the same message, and a team address often receives invoices and payment requests. The FBI’s 2024 Internet Crime Report recorded 21,442 business email compromise complaints in 2024, with $2,770,151,146 in reported losses. Those are schemes where someone poses as a client, vendor or colleague by email to redirect a payment.
Five habits cover most of the risk:
- Everyone signs in as themselves. Nobody shares a password to the team address. Microsoft 365 gives each person access to the shared mailbox from their own account. Gmail has delegation, and a Google Group gives each member their own seat.
- Every sign-in has a second factor. A stolen password alone then isn’t enough to get in. CISA’s page on multi-factor authentication explains how it works.
- Remove access the day someone leaves. With individual sign-ins, that’s one change for one person, and nobody else’s password has to move.
- Confirm payment changes by phone. A new bank account in an email gets a call to a number you already have on file, never one from the email.
- Treat urgency as a signal. “Pay this today, I’m in a meeting” from a partner’s address is a reason to check, not a reason to hurry.
On Microsoft 365, the shared mailbox’s own account should also have sign-in blocked. The team email guide covers why, with Microsoft’s own wording.
People ask which email provider is hacked most. Nobody publishes a fair comparison. The biggest providers draw the most attempts simply because they host the most accounts. What decides whether an account is taken over is mostly the account itself. A reused password with no second factor is the weak point on any provider.
When the habits stop holding
For two or three people, ownership, statuses and reply-by times can run on what Gmail or Microsoft 365 already gives you. Some signs say they’ve stopped holding:
- A client hears from both of you about the same thing more than once a month.
- Threads sit in “new” past the next triage pass because nobody had time.
- You’ve promised a client a response time in writing and can’t show whether you met it.
- Someone keeps a private spreadsheet of who owns what.
If those sound familiar, a shared inbox tool adds assignment, statuses and reporting on top of the address. Shared inbox software: what it is and how to choose compares the options and their prices. Many small firms never reach that point, and alternatives to a shared inbox tool makes that case.
What Point does for each person on the team
Point isn’t a shared mailbox. It connects each person’s own Gmail or Microsoft 365 account, and seats are per person. Where the right answer for your firm is a real shared mailbox or a Collaborative Inbox, set that up and run the model above on it.
What Point changes is each person’s own day inside the team. Your mail is ranked as it arrives, and today’s most pressing thread is the first one you see. Each thread has a short summary, so a triage pass over your own mail takes minutes. When a client asks you for something, it becomes a task on your list with its date, and a thread waiting on a client comes back to you when it’s worth chasing. When you reply, Point drafts it in your voice. By default you review each draft and press send yourself. You can raise that per kind of action once you trust it. Everything Point did is in an activity log you can review. See how it works.
Per-seat billing explains how seats are counted. What a second seat can see covers adding a colleague. If you’d like to start with the story of two people sharing one desk, one inbox for a two-person company tells it. Or start at Point’s home page.
Common questions
How should a team manage a shared email inbox?
Give every thread one owner, one status and a reply-by time both people can see. One person does a short triage pass at set times, such as 9:00 and 2:00, and assigns each new thread. Four statuses cover most small firms: new, mine, waiting on them, and done. Each person signs in as themselves rather than sharing a password.
What are the five D’s of email management?
The usual list is delete, do, delegate, defer and designate, where designate means filing. In a team, delegate becomes assigning the thread to an owner. Defer needs a date the other person can see, and delete needs a shared rule so nobody removes mail a colleague needed.
Can ChatGPT organize my email?
A chatbot can summarize mail you show it, sort it by urgency and draft replies. Organizing a team inbox also needs a lasting record of who owns each thread and where it stands. That record has to live where both people work, so an AI built into the mail does more for a team than a separate chat window.
What is the most hacked email provider?
Nobody publishes a fair comparison between providers. The largest, Gmail and Microsoft 365, draw the most attempts because they host the most accounts. Whether an account is taken over depends mostly on the account: a unique password, multi-factor sign-in, and staff who check payment requests by phone.
How do we stop two people replying to the same email?
Claim the thread before you start writing, so the other person can see it’s taken. Keep notes inside the thread rather than in a side chat. Reopen the thread just before you send, in case a reply has landed while you were writing.
What’s a reasonable response time for a shared inbox?
For a small professional firm, same business day for anything with a deadline, one business day for new inquiries, and two business days for routine client questions are targets most teams can keep. A short first reply that names when the full answer will come meets the promise.
Does a shared inbox need special software?
Not for two or three people. Gmail’s Collaborative Inbox and Microsoft 365’s shared mailbox handle shared access, and the habits in this guide supply ownership and status. Software earns its price when the habits stop holding, or when you’ve promised clients response times in writing.