Blog

Shared inbox vs Google Group

A Google Group is an address with a membership list. A shared inbox is an address with a queue. How to tell which one yours is, and who should keep the group.

You have one address to give out and two ways to run it: a Google Group or a shared inbox. Use the group when the message is for an audience, and a shared inbox when a message means somebody owes a reply.

The test is what happens after delivery. A group takes one message and delivers a copy to every member, in the form that member chose. A shared inbox takes the same message and puts it in one list the team works from, where it can be assigned, answered from the shared address and found again later. Neither arrangement is an upgrade of the other, and the test below decides it.

Google Groups deliver a copy to each member

Google’s own description starts with the use case: email everyone in a group with a single email address (Learn about Google Groups). One address, a membership list, and a message that fans out to the list.

How it arrives is each member’s decision. In Google Groups, your subscription setting determines whether and how you receive email from a group: each message as it is posted, a daily digest of up to 25 messages, an abridged summary of up to 150, or no email at all (Manage your subscriptions and global settings). One teammate can read every message as it lands, and another can take one summary a day.

Membership is also the permission model. A group has owners, managers and members, and its settings decide who can join, who can read and who can post (Create a group and choose group settings).

What a shared inbox does with the same message

A shared inbox puts the same message in one place instead of several. Everyone with access sees the same list, which conversations are assigned and which are waiting, and the replies that have gone out.

Replies leave from the shared address rather than from a personal account, and the connected mailbox stays as the record of the conversation. Access is set per inbox, so the people who cover support@ are not automatically the people who read billing@.

A shared inbox does not add response-time targets or reporting, and that line is where it stops. Shared inbox vs help desk covers what a ticket queue adds and the signals that mean a small team needs it.

The two arrangements side by side

Google Group Shared inbox
What the address is An address with a membership list An address with a queue
Who receives a message Every member, in the form their subscription chooses Everyone with access to that inbox
Where the thread lives A copy in each member’s mailbox The team’s list, with the mailbox as the record
Taking a message A member takes it in the group’s web view when the group is a Collaborative Inbox Assigned in the place the team reads the mail
Access rules Group roles and membership Per-inbox roles
Fits An audience A request

The arrangements differ in where the work lives: in a set of personal mailboxes, or in one list the team shares. Google Groups can add assignment through its Collaborative Inbox type, and what a collaborative inbox is covers what that adds and where it stops being enough.

The question that decides it

Ask who the message is for. A message for an audience has many readers and no single owner: a release note to the team, an alert, a discussion list. A message that is a request has one reader who owes an answer and one person waiting for it.

The signals are easy to spot:

The address is a list if The address is a queue if
A reply from any member answers everyone One person has to write back to one person
The members are the audience The members are covering for each other
The message tells people something The message asks for something
Delivery on its own is the job Each message needs a state: open, waiting or done

If two rows on the right describe your address, it is a queue. If two rows on the left describe it, keep the group.

Who should keep the group

Keep the group when the address is an audience rather than a queue. That covers more addresses than the pages selling a replacement usually admit:

  • An announcement or alert address. announcements@ and alerts@ exist to reach people, and a copy per member is the right delivery.
  • A discussion list. The conversation is what the members came for, and every reply belongs to the whole list.
  • An address that includes people outside your team: a contractor, a vendor, a customer’s own staff. Membership is the simplest way to hold a mixed list together.
  • A low-volume alias where delivery is the whole job.

Any one of those is a reason to leave the address alone.

When the address is a queue

Move to a shared inbox when a message arriving means somebody owes a reply. Customer email is the common case, and the address is usually the one published on the site.

The signs that an address is a queue: more than one person covers it, the reply has to leave from the address rather than from a personal account, or billing@ and security@ should be readable by different groups of people.

A shared inbox is the lighter of the two working shapes: one place to read, assign and answer, without the targets and reports of a help desk.

Where Chirp fits

Chirp is a shared inbox for small software teams that track their work in Linear, at $9 per user per month. It connects a Google or IMAP mailbox and keeps it as the record, so replies leave from the shared address.

Press i in a thread to link, create or search a Linear issue. Snooze until done, and when every linked issue is Done or Canceled the thread reopens with a drafted reply that names it. The Issues view (g i) ranks linked issues by how many customers are waiting.

Rules can close, tag, assign and snooze threads, and write drafts. No rule can send email: a reply leaves when a person sends it, or when a script you gave API access to sends one. Access is checked per inbox on every read, with the roles Admin, Agent and Viewer.

FAQ

Is a Google Group the same as a shared inbox? No, though the address looks the same from outside. A group is an address with a membership list and delivery per member. A shared inbox is an address with a queue, one list the team reads from.

When should a team use a group instead of a shared inbox? When the message is for an audience: an announcement, an alert, a discussion list, or a mixed list that includes people outside the team. If nobody has ever asked who is answering a message, the group is doing its job.

Are Google Groups still available? Yes. Google still documents Groups for personal accounts and for organizations, including the Collaborative Inbox type (Learn about Google Groups).

Can a team run both? Yes, and the two do not compete. An alert group for internal notifications and a shared inbox for the addresses customers write to.

Next step

If the address is a queue, the decision left is which shared inbox to run it in. Google Groups alternatives works through the options and what each costs. If the address is a list, nothing here says you should change it.