Google Groups vs Collaborative Inbox, and When Your Support Address Needs a Help Desk Instead

A Collaborative Inbox is the same Google Group underneath, with a few extra features turned on. Nothing changes about the address or who is on it, and the copies landing in everybody’s Gmail look no different to the day before, so what gets added is only a page on groups.google.com where a conversation can have somebody’s name put against it and be marked finished. Teams who go a step further, to a help desk, nearly always go on account of the reply rather than the mail coming in, since neither of the two Google options keeps the answer anywhere the next person would think to look for it.

Which of the three suits you depends a good deal less on the size of your team than people expect. It turns on two small settings nobody looks at when they create a group, the delivery option against each member’s name and the address a reply goes out from, and most of this page is about those two. We make a help desk ourselves, so there is an interest on our side of the table, mind you, and further down we say plainly which teams ought to leave their group exactly as it is.

What actually changes when a group becomes a Collaborative Inbox

Less than the name suggests, to be honest with you. Switch it on of a Monday and look in your Gmail on the Tuesday and you would not know a thing had happened. The mail arrives the very same way and from the same address, subject prefix and all if you ever went and set one.

The change is all on the group’s own page. Each conversation there can now be taken by whoever means to answer it, or assigned by somebody to another member. It can be closed off as complete, or as needing no action, or marked a duplicate of some other conversation, and that last one locks it so nobody can do anything further with it. The list filters down to only what is still unresolved, and it searches by who has been given what.

Who may press each of those buttons comes down to permissions most owners never open. Taking and assigning a conversation, and marking it complete, need the one Google calls Who can moderate metadata. Google files the other two, no action needed and duplicate, under Who can moderate content, so a group where members were left on the basic set can end up with the buttons greyed out for the very people answering the mail. That takes a couple of minutes to fix. Somebody usually spots it in week two.

Conversation history has to be on before any of this works, and on a work account Groups for Business has to be switched on in the Admin console as well. We wrote the rest of it out step by step in our Collaborative Inbox setup piece, so we will leave the order of the tick boxes to that.

What none of it does is reach into Gmail. The name on a conversation and the word complete beside it are shown on the group’s page and nowhere else. So a member who reads from their own inbox all day, which is most members, funnily enough, sees a mail with nobody’s name on it and no way of telling whether it was dealt with an hour ago. The new features help whoever goes and opens the group. Whether anybody does is down to one setting.

Why each member’s delivery setting decides more than the product name does

Say six of you are on support@. Two have it set to send each email as it arrives. Another pair went for the daily digest and one gets the abridged version. The sixth is whoever created the group in the first place, who put their own delivery on no email so as not to be copied twice and has not given it a thought since.

A customer writes in at 10:40 on a Tuesday asking whether a Shopify order can still be changed. Two of the six have it inside the minute. Google holds it back for the digest pair and sends it later, in a bundle that goes out once a day holding up to 25 complete messages, and at 40 mails a day that comes as two bundles, near enough. Somewhere in a list of up to 150 the abridged member gets a single summary line for it. And the person who made the group sees nothing at all, not unless they go and open the page, and there is no reason in the world they would.

So for anything that wanted an answer before lunch, the group is really the two people on each email. Nobody in the other four did a single thing wrong, mind you. They are set up to hear about it later, which is what each of them chose, one at a time, for reasons to do with their own inbox rather than with the customer.

In practice that is most of what separates a group from a Collaborative Inbox. Leave everybody on each email and the group behaves like a distribution list, every mail in every inbox and one and all taking it that somebody else is on it. Turning Collaborative Inbox on changes that only for the people who look at the page instead of their copies. The opposite setting is no email for the lot of them, and that turns it into something much nearer a real queue, one list that everybody has to go and open, with names against the conversations. It also means nobody hears of a new mail at all unless they go looking for it their own selves.

Most groups sit in between, and the mixed state is the one that tends to go wrong. Nobody can tell who has seen what. The members page shows each person’s delivery setting beside their name, and it is worth going to look at before you choose anything else on this page.

Where does the answer end up when somebody replies from Gmail

Fair is fair, the incoming half of a Google Group works well enough, and plenty of teams never have a moment’s bother getting mail in. It goes wrong on the way back out.

A member reading their copy in Gmail and pressing reply is sending an ordinary email, from their own address, to the customer. The copy of that answer goes into their own Sent folder, which none of the rest of you can see into. The group’s page offers Reply to author as well, and that one simply opens whatever mail program you normally write in, so it leaves from your own address too. It is only offered to members holding the Who can reply to author permission in the first place.

There is a fix for the name on the reply, and it is a decent one as far as it goes. An owner or manager can give members the Who can post as group permission, and each member then adds support@ in Gmail under Send mail as. Gmail posts a confirmation code to the group for somebody to fish out and enter. From then on an answer can leave from the support address, and the customer writes back to support@ rather than to one colleague’s personal inbox, which is worth the bother on its own.

The copy of the reply is another matter, and the permission does nothing for it. Sending from an address puts nothing into that address, so the answer still sits in one person’s Sent folder, and anybody searching the group later finds the customer’s question with nothing at all underneath it.

The way to get the answer into the group is to copy the group in, with Reply all, and that works, mind you, only the cost of it lands on the people who get each email. Go back to the 40 mails a day. Answered with Reply all, every answer lands back in the group as a new message, so the two members on each email get something like 80 a day where they used to get 40. Half of those are their own colleagues’ replies. Teams who try it for a week tend to go and move their own delivery to the digest by the Friday, and the Tuesday problem comes straight back.

Is there a shared mailbox in Google Workspace at all

People coming across from Microsoft 365 ask this one most, since Outlook and Exchange have a thing called a shared mailbox and Google Workspace has nothing that goes by that name. Google’s own help pages answer it by pointing a support team at a group set up as a Collaborative Inbox, and at delegated accounts for anybody wanting more.

A delegated account is an ordinary user mailbox that other people are let into from their own sign-in, with no password handed round. On a work or school account it takes up to 1,000 delegates, of whom about 40 can be in it at the same time with typical use. It works, after a fashion. The trouble for support is the sending. Google’s documentation says that when a delegate sends from the account, their own address appears. And the account being shared is a full user in its self, which on Google Workspace means a licence paid every month for an account nobody signs in to directly.

The delegation limits have a page of their own. If you are weighing the Microsoft side of the same choice, our Microsoft 365 group comparison does it with Outlook, Exchange and Teams instead of Google’s furniture.

How do a Google Group, a Collaborative Inbox and a help desk compare

Across the whole comparison, it is the two differences about the reply that send people shopping, far more often than reporting does, truth be told, whatever they said at the start about wanting numbers.

Who should keep a plain group and never switch anything on

Open the list of groups in your Admin console some quiet afternoon and most of what is sat in there should be left exactly as it is. The all-staff list and the address the monthly newsletter goes out from are plain groups doing a plain job, a single mail out to many people. There is nothing to own in a mail that only ever travels the one direction.

The customer-facing case is narrower. If there are two of you answering, sat within shouting distance of each other and both on each email, and the mail is light enough that either of you could read every one of them, then a plain group is earning its keep and nobody has needed a spreadsheet in Google Drive to track who owes whom a reply. Plenty of small teams are exactly that. A Collaborative Inbox laid on top would add a page neither of them has any reason to go and open.

It starts to be worth switching the extra features on the first week two of you answer the same customer inside the same hour, since that means the copies in your inboxes have stopped telling you who has what. The step past that again, to a desk, tends to come later, often after a reply goes missing that mattered. We have gone at the signs of it properly in the piece on choosing a shared inbox or a ticketing system, rather than go over the whole of it a second time here.

What moving support@ over to a desk like ours looks like

Over here we build Maxdesk, a help desk whose middle is one shared inbox for the whole team, and the part of it that matters most against a Google Group is the reply.

Customers notice nothing. They carry on writing to the same support@ they always did. The address gets pointed at your workspace, which takes about 60 seconds at our end. At Google’s end your admin may have a setting or two to change first, since plenty of Workspace accounts are set up to stop mail leaving for addresses outside the company. Each mail that lands becomes a conversation with one owner on it, given by a person or by one of the routing rules you write, and the name sits on the conversation its self rather than on a separate page somebody has to remember to visit.

Replies leave from your support address. Whoever writes one, its copy stays in the conversation, under the customer’s own mail, so the next person to open it finds the question and the answer one above the other, which no amount of Reply all ever quite managed inside the group. Notes for the team go in the same place instead of into Slack, and none of them ever reaches the customer. The rest of it is on the free workspace as well, the templates for answers you give every week and the dashboard of what is open and what nobody has picked up, and so is the clock on each reply, which counts your business hours and nothing else.

Our bill is per workspace and heads never come into it, which counts for more on this subject than on most. The four in the Tuesday example who were on digest and abridged and no email are exactly the people a per-seat desk makes you choose between, the accounts person who knows about refunds, the owner who looks in now and then. On ours they can all sit in the queue for nothing extra. They see the very same conversations as the two who answer most of them.

The parts of the Google setup we would not try to beat

A group costs nothing beyond the Google Workspace you already pay for, and it is sitting in your Admin console this minute. Our free workspace comes with conditions a group does not have. The ads sit on the side your team works in, where a customer never sees them, and outgoing mail has our name in small print at the bottom. That is a real cost to some teams. It also puts a ceiling on the number of automation rules switched on at the one time, which a team moving off a group rarely meets in the first month. The paid workspaces take all of that away, and we would not call the free one free with no strings on it, not even to our own selves.

History is the part of it that deserves the most thought here. A group keeps its conversation history for as long as the group exists, unless your admin has set a retention rule of their own, for GDPR reasons or any other. Our free workspace holds a rolling 3 months, counted from each conversation’s latest activity, and the paid workspaces hold 12 and 24. A team leaving a group with five years of mail in it should plan on those old conversations staying where they are, and keep the group about for looking things up for a good long while.

Mail is the only way in, with us. The group is email only too, so nothing is lost against it there, though anybody hoping for chat on the website as well will not get it from either of us.

And for a fortnight or so after the move, somebody will answer a customer out of their own Gmail, on account of an old copy still sitting in their inbox, and the reply will go out the old way and miss the conversation. Nothing we build stops that fortnight. It wears off by its self once the old copies stop arriving and people get used to the one place.

One test mail, before anybody decides anything

The cheapest way of finding out which of the three you need costs one email and about 10 minutes. What we would do, if it were our group, is write to support@ from a personal address at a time we would remember, and word it the way a customer would.

Going round the members afterwards and asking who saw it, and when, tells you in a quarter of an hour what the delivery settings are doing that nobody chose on purpose. There is usually one name that surprises somebody.

The reply is the part to watch, so answer it from Gmail the way anybody on your team normally would, and afterwards go and open the group and search for it. If it is not in there, and on most groups it will not be, you have seen the whole of the problem your own self, and whether it is worth fixing is a question only you can weigh, since some teams have never once needed to go back and read an old answer and are right not to pay for the ability.

Common questions about Google Groups, Collaborative Inbox and help desks

Is a Collaborative Inbox the same thing as a Google Group?
Yes, underneath. A Collaborative Inbox is an ordinary Google Group with extra features turned on: members can take or assign conversations and mark them complete, no action needed or duplicate. The address, the members and the copies delivered to Gmail do not change.

Can Google Groups members reply from the group’s address?
They can, once an owner or manager gives them the Who can post as group permission and each member adds the group address in Gmail under Send mail as. Gmail sends a confirmation code to the group to verify it. The reply then shows the group address, but its copy stays in the sender’s own Sent folder unless the group is copied in.

Does Google Workspace have a shared mailbox?
Not under that name. Google points support teams at a group used as a Collaborative Inbox, or at a delegated account. A work or school Gmail account can have up to 1,000 delegates, about 40 at the same time with typical use, and a delegate’s own address appears when they send.

What are the size limits on a Google Group?
Google documents 25 MB per message, attachments included, and 300 inbound emails per 5 minutes per group, among other limits. A group that goes over a limit is restricted, typically for an hour and for up to 24 hours. Google’s policies and limits page was last updated on 24 September 2026.

Can a Collaborative Inbox show who is replying to a conversation?
It shows who a conversation is taken by or assigned to, on the group’s page at groups.google.com. That name is not shown on the copies in Gmail, and Google documents nothing that warns you when a colleague is writing a reply to the same message.

When should a team move from a Collaborative Inbox to a help desk?
Usually when replies need to be found again: a colleague is off and nobody can see what was promised, or the same customer gets two different answers. A help desk keeps the reply in the conversation and sends it from the support address, which neither Google option does on its own.

Google’s settings and limits reviewed on 29 September 2026 against Google’s own help pages; the six-person group and its 40 mails a day are made up for the example, and the Maxdesk details were checked on the live site the same day.