Shared Inbox vs Helpdesk for a 1-3 Person Store

For a store with one to three people answering email, a shared Gmail or Outlook inbox is usually enough. A helpdesk starts to pay off when more than three people reply every day and you need assignment, internal notes and reporting, or when customers contact you outside email. If your real problem is a pile of repetitive order-status emails, neither one fixes that on its own.

Below is what breaks first in a shared inbox, rough thresholds I use for small stores, and a middle option.

What breaks first in a shared Gmail or Outlook inbox?

Two people replying to the same customer is the first thing that goes wrong. A plain shared inbox has no owner field, so nothing tells you who has an email. Everything else is manageable at small scale.

Here is what the platforms themselves say, as of October 2026.

Gmail delegation:

• A personal @gmail.com account can have up to 10 delegates. A Google Workspace account (a work address on your own domain, which most stores use) can have up to 1,000.
• On Workspace, about 40 delegates can access the account at the same time. Heavier or automated use, such as APIs or browser extensions, can lower that. For a 1-3 person store, this ceiling is irrelevant.
• A delegate can read, send, and delete emails in your account for you.
• A delegate can’t chat with anyone or change your password.
• When a delegate sends a message, their email address appears. Your customer can see that a second person replied.

Google Groups Collaborative Inbox (a Groups feature, not plain Gmail):

• You can assign conversations to group members and mark them complete.
• Only members with the “Who can moderate metadata” permission can take or assign conversations. An Owner or Manager sets that permission.

Microsoft 365 shared mailbox:

• It needs no license of its own for up to 50 GB, but every person using it needs their own licensed Exchange Online mailbox.
• It requires a plan that includes email. Microsoft 365 Apps for business doesn’t, and Business Standard does.
• You can’t give people outside your business, such as people with a Gmail account, access. That rules it out for most freelance VAs.
• It supports a maximum of 25 users. Too many people at once can cause connection failures or duplicated messages. That is far above a 1-3 person team.
• You can’t prevent users from deleting messages in it.

If your VA uses their own Gmail address, a Microsoft 365 shared mailbox is the wrong tool. Gmail delegation or forwarding fits better.

Will I hit sending limits?

Almost certainly not at this size. Paid Google Workspace accounts can send 2,000 messages per day, and trial accounts 500. Going over means you can’t send for up to 24 hours, though you can still receive.

A small store answering support email won’t get near those numbers. The limit that matters is people, not volume.

What about giving a VA access to Shopify orders?

This is where small stores get stuck, and the generic comparison posts skip it. A VA who answers “where is my order?” needs to see order status, and the plan you are on decides how.

• The user limits by plan are: Starter 0, Basic 0, Grow 5, Advanced 15, Plus unlimited.
• Collaborator accounts and POS-only staff don’t count toward that limit, and the store owner is exempt.

Sharing your own admin login is the tempting workaround. Paraphrasing Shopify’s Terms of Service: each staff account must include a full legal name and a valid email account, and the store owner is responsible for breaches by their employees, agents or subcontractors. The Terms don’t explicitly ban sharing a login. Still, I would not share one, since a login in two hands makes it hard to say who did what.

When does a shared inbox stop being enough?

These are my own rules of thumb for 1-3 person stores, not industry data. Adjust them to your store. Three people replying daily is the borderline case: a shared inbox can still work if the handoff rule below is followed.

Situation	Shared inbox is fine	Look at a helpdesk
People replying	You, plus one or two others	More than three replying daily
Duplicate replies	Rare, fixed by a handoff rule	Happening weekly despite the rule
Channels	Email only	Chat, phone or social DMs
What you track	Nothing formal	Response times, ticket owners, reports
Email mix	Mixed questions	Complex cases that need history and assignment
Stores	One store, or one inbox per store	Many stores feeding one queue

A rough count helps. Look at a week of email and note what share is order status. If most of it is “where is my order?”, you have a repetition problem. Buying seats won’t solve that. The guide on auto-answering where-is-my-order emails covers that case.

If you run two stores, give each its own support address and inbox. Mixed queues are how replies go out under the wrong brand.

How do I stop double replies in a shared inbox?

Use a handoff rule that costs nothing. Here is the one I would paste into a shared doc or your VA’s onboarding notes:

Support handoff rule

1. Before replying, star the email or apply the label “[Your Name] working”.
2. If an email already has a label, don’t touch it.
3. Refunds, cancellations and anything over [$Amount] go to [Owner] with the label “Needs owner”.
4. When you reply, remove the “working” label and add “Done”.
5. If you’re unsure, draft the reply but don’t send. Label it “Needs review”.

Manual labels fail the day someone forgets. As a backup in Gmail, create filters that label automatically. For example, a filter on messages containing your order number prefix (such as ”[#1]”) can apply an “Order question” label, and another on words like “refund” or “cancel” can apply “Needs owner” so those never get answered by accident.

This takes a few minutes to set up and covers the one failure that hurts a small team. For a bigger set of ready-made replies, see these customer service email templates for ecommerce.

What is the middle option between a shared inbox and a helpdesk?

Keep your existing inbox and forward it to an AI drafting tool. You stay in Gmail or Outlook, and nobody moves to a new system.

LzyReply works this way. You forward your store’s support address, and for each email it looks up the customer’s Shopify order (status, tracking, items, shipping address) and drafts a reply in your brand voice. A human approves by default, with one click to send or edit first. It also has an optional autopilot for routine “where is my order?” replies, which is off by default and notifies you every time it sends. The plan is $29/month with a 7-day free trial, and you can try it from the Shopify App Store.

It has limits, and you should know them before choosing:

• No team seats. There are no multi-agent helpdesk features, so drafts are approved from one account and it won’t replace assignment and reporting for a bigger team.
• Email only. No live chat widget, no phone, no social DMs.
• Shopify data only. It doesn’t connect to print-on-demand suppliers, so it can’t change or cancel supplier orders.
• No refunds or cancellations. Those stay with you.

That makes it a fit when your pain is repetitive email volume, not team coordination. Your VA can keep answering from the shared inbox, but since there are no team seats, the AI’s drafts are approved from one account. For more on this setup, read how AI customer support works on Shopify.

What about the contact form on my store?

Shopify’s contact page sends to one place. Your contact form sends all submissions to your store’s sender email address, which you can change on the Notifications settings page. Point that address at the inbox you want to use before choosing any tool, or form messages will land somewhere you aren’t watching. The steps for forwarding contact form emails are in a separate guide.

So which one should I pick?

• Just you, or you plus a VA, one or two stores: shared inbox plus the handoff rule above.
• Mostly order-status email: keep the inbox and add AI drafting before paying for helpdesk seats.
• More than three people replying, or chat and phone support: time to compare helpdesks. Start with the best helpdesk for small Shopify stores and what a Shopify helpdesk actually is.

Don’t buy a helpdesk for problems you can solve with a label and a rule. Buy one when coordination, not volume, is what’s costing you time.