You have delegated support@ to three people. Each opens it from their own Gmail, reads and replies, and the mailbox keeps the whole record. That part works, and it costs nothing beyond the accounts you already pay for.
Delegation is access, not workflow. It lets several people read and send from one account and adds nothing else: no assignment, no shared state, no sign that a colleague has started a reply. It holds up for one or two people and breaks down at about three.
What Gmail delegation does well
A delegate can read, send and delete messages in the account, and the mailbox stays the single record of what the team told a customer (Gmail Help).
The delegate signs in with their own Google Account, so there is no second licence for the shared address, and a Google Group can be added as one delegate so a whole team inherits access at once (Google Workspace Help).
What delegates cannot do
Google is explicit about the scope. Delegation hands over the email and nothing that touches other Google services or account settings. Delegates cannot add a Drive attachment, pull from Google Photos, or use Smart Reply, Smart Compose or the spelling and grammar checks (Gmail Help). The Drive attachment is the one a support team notices first.
The same page lists what is missing in the mobile app, where a delegate can never be added.
| A delegate can | A delegate cannot |
|---|---|
| Read, send and delete messages | Change the account password |
| Apply labels, filters and archiving | Chat from the account |
| Send from the address | Add a Drive attachment or use Smart Reply |
| Switch accounts from the profile menu | Add or remove other delegates from a phone |
Delegates see the mailbox in their own client, with no shared state
A delegate opens the mailbox from the account switcher in their own Gmail, and the owner’s Inbox appears in a new browser tab (Gmail Help).
It has nothing the team shares. Two delegates looking at support@ at once see the same unread list and no sign that the other is typing. The tab is a view of a mailbox, not a workspace.
There is no assignment and no line between handled and untouched
You cannot give a thread to a person. There is no owner field, no status beyond read and unread, and no view that separates what someone is working on from what nobody has opened.
So the team builds one by hand: a pinned doc, a Slack message that says “I have the Acme one”, a habit of starring anything in progress. That stops holding the week two people answer the same customer.
Every delegate also sees the whole mailbox. There are no permissions per folder, thread or sender, so access to support@ is access to all of it. You cannot give a contractor the billing threads alone, or give a new teammate read-only access for their first week.
What a licence costs and what it does not cover
Delegation is free, and that is a real advantage. The arithmetic worth doing is what the free option costs in coordination.
Chirp is $9 per user per month, one plan, every feature included. The numbers below assume a five-person team that already pays for five Google Workspace accounts, because delegation runs between accounts in the same domain.
| Delegation | Chirp at $9 per user per month | |
|---|---|---|
Extra licence for support@ |
None | None, the mailbox stays where it is |
| Five people able to answer | Yes | Yes |
| Cost for the team | $0 | $45 per month |
| Who owns a thread | Nobody | An assignee |
| Handled versus untouched | Read and unread | Status, plus a view of who is on what |
| Access per inbox | All of it, for every delegate | Per inbox, with Admin, Agent and Viewer roles |
| Adding someone on a phone | No | No, the app is the app |
Google’s limits are generous at the top and narrow at the practical end. A personal account takes 10 delegates; a work or school account takes up to 1,000, with about 40 able to use it at once (Gmail Help). Three people answering support will not hit the cap, which is why the cap is not the reason teams move.
The reason is the column on the right. If delegation is the access model you want, shared mailbox versus distribution list covers the other ways to get several people onto one address.
Send-as is not a shared identity
A delegate sends from the delegated address, and Google’s documentation says plainly that the delegate’s own address appears on the message. Whether the recipient sees both addresses or only the mailbox owner’s is an admin setting (Google Workspace Help).
That setting decides whether the customer sees [email protected] alone, or [email protected] on behalf of [email protected]. If your support address is meant to read as one identity, set it before five people start sending from it. A customer who replies to the wrong address takes the thread out of the mailbox.
Two details matter before you rely on delegation for cover. The invitation expires after a week, and access can take up to 24 hours to work, so when the person who runs support is ill on a Monday, delegation is not a same-morning fix.
Where delegation stops and a shared inbox starts
Delegation gives a mailbox to more people. It does not give the team a queue, and the queue fails first. The moment two people can answer the same thread and neither can see the other, the team needs ownership and a line between what has been handled and what has not.
Chirp connects to the same Gmail or Google Workspace mailbox and leaves it as the source of record. A thread then carries an assignee, single-key triage moves through j and k with e, s, a, t and b, and access is set per inbox with Admin, Agent and Viewer roles. A mailbox can hold several addresses, each open to a different group.
None of that is a reason to remove delegation on a two-person team with a quiet inbox. It is the answer for the team that has already outgrown it and is tracking the overflow in a spreadsheet.
Chirp is a shared inbox, which is a different thing from the phrase Google uses for delegated accounts: what a shared inbox is covers that definition, and shared inbox versus help desk covers whether you need a support tool at all.
FAQ
Is Gmail delegation the same as a shared inbox? Google’s admin documentation says that in Gmail the two names refer to the same feature (Google Workspace Help). A shared inbox in the wider sense is a mailbox plus the workflow around it: an owner per thread, a status, and views that separate handled from untouched.
Can a delegate reply so the customer does not see them? Only if your admin sets it that way. By default the delegate’s address appears on what they send, and the Admin console can show both addresses or only the mailbox owner’s (Google Workspace Help).
What can a delegate not do in Gmail? Change the password, chat from the account, add a Drive attachment, use Google Photos or Tasks, or use Smart Reply, Smart Compose and the spelling and grammar checks (Gmail Help).
How many delegates can one Gmail account have?
Ten on a personal @gmail.com account and up to 1,000 on a work or school account, with roughly 40 able to access it at once (Gmail Help).
Next step
If the limits above are the ones you are hitting, what a shared inbox is shows what the layer on top of the mailbox contains. If you are still choosing how several people get onto one address, what a collaborative inbox is covers the four ways teams build one and how each fails.
