Running ecommerce support from a Gmail shared inbox

The three ways to share a Gmail inbox

• Shared password. Everyone logs into support@. Do not do this: no audit trail, no per-person 2FA, and offboarding means a password rotation.
• Delegation (Google Workspace). The support@ account delegates access to each person's own login. Everyone works from their own account, replies go out as support@, and access is revoked per person. This is the right default for two to five people.
• Group with a collaborative inbox. A Google Group with conversation assignment and status. Heavier, and closer to a lightweight ticket system.

Delegation is what most small teams should use. It takes about ten minutes to set up and solves the security problem outright.

Labels that earn their place

Resist building a taxonomy. Three or four labels that drive an action beat twenty that describe a feeling:

• Waiting on carrier — you have opened an enquiry and cannot progress
• Waiting on customer — you asked a question and are blocked
• Escalated — needs the owner
• Refund pending — money is owed and has not moved

Every one of those has a follow-up attached. Labels like "shipping" or "returns" describe the ticket without changing what anyone does, and they quietly become clutter.

Handling collisions

Two people answering the same email is the classic shared-inbox failure. Without a ticket system you have three practical options:

• Split by time. Cleanest for a small team. One person owns mornings, one owns afternoons. No overlap, no collision.
• Split by label. One takes shipping, one takes returns, applied on arrival with a filter.
• Claim in a chat channel. Works at two people, breaks at four.

If you find yourself building a rota to prevent collisions, that is a real signal you are approaching the edge of what a shared inbox does well.

Templates without a macro system

Gmail has canned responses built in, under Settings → Advanced → Templates. They are basic: no variables, no sharing between accounts. Two things make them workable:

• Write templates as skeletons with obvious blanks, so an unfilled placeholder is visible before you send rather than after.
• Keep the master copies in one shared doc and paste them into each person's Gmail, so there is a single source when the returns policy changes.

Our free template libraries are structured for exactly this.

The part a shared inbox cannot fix

Delegation, labels and templates make the inbox work. None of them tell you which Shopify order the email is about. That answer lives in another tab, and you fetch it by hand for every order question — which for most stores is the majority of the queue.

That single gap is what makes people think they need a helpdesk, when what they actually need is the order data next to the email.

Signs you have outgrown Gmail

Being honest about this, because the answer is sometimes yes:

• Support arrives on channels other than email and you need one queue
• You need assignment and SLAs, not a rota
• More than about five people are answering
• You need reporting the business actually acts on
• Compliance requires a full audit trail per ticket

If two or more of those are true, price a helpdesk. If none are, a shared inbox with the order data attached will take you a long way. Our comparison pages cover both sides.