How to Turn a Shared Gmail Inbox into a Hiver Helpdesk
Hiver turns a shared Gmail or Google Workspace inbox into a team helpdesk: emails become assignable conversations with status, notes and SLAs, and the customer still writes to support@yourco.com. Setup for a team of five takes about an hour — install from the Google Workspace Marketplace, add the shared mailbox, create three views, invite agents.
The appeal is that you keep the address you’ve published in ten places. The cost is that everything runs inside Gmail’s constraints, which matters more at scale than at the start.
What does Hiver add to a Gmail inbox?
Three things Gmail doesn’t have: assignment (one owner per conversation), status (open, pending, closed — not just read/unread), and collision detection (a warning when two agents open the same thread). Plus SLAs, templates and internal notes that don’t reach the customer.
That’s the whole delta. If your team’s problem is “we lose track of who’s replying to what”, this solves it. If your problem is reporting, Hiver has reports but they’re not a BI tool.
Step 1: install on the right Workspace account
From the Google Workspace Marketplace, install Hiver, then authorise with an account that is a Workspace super admin. Personal Gmail accounts cannot use Hiver shared mailboxes — a common surprise for small businesses that started personal.
Pricing sits around $15–$29/user/month depending on tier, billed annually, with the cheaper tiers limiting shared mailboxes per team.
Step 2: add the shared mailbox, not a forwarding rule
Use Admin → Shared Mailboxes → Add and pick or create support@. Two things to verify before inviting anyone:
- The mailbox is a Google Group with the right members, not a personal account that happens to be named support.
- Alias addresses (
help@,support-uk@) route into the same mailbox — Hiver follows Gmail aliases if they exist.
If you forward support@ to one person’s inbox and add Hiver there, you get assignment features on a single-user mailbox. It works until that person takes a holiday.
Step 3: create three views, then stop
Views are saved filters. Three is the right number to start:
| View | Filter | Who uses it |
|---|---|---|
| Unassigned | status open, no assignee | team lead |
| Mine open | assignee me, status open | everyone |
| Pending | status pending | team lead, daily sweep |
Resist the urge to build a view per customer segment. Views multiply and nobody switches between eleven of them.
Step 4: turn on collision detection and SLAs
Collision detection is on by default once the shared mailbox is active. Leave it. It’s the feature that prevents the double-reply that customers notice most.
SLAs live under Admin → SLA. Start with first response only — 4 hours for standard, 1 hour for anything tagged urgent. Resolution SLAs are attractive on paper and demoralising in practice when half your tickets are customer-waiting.
Does Hiver’s SLA clock pause when the customer replies last?
Yes, the SLA can be configured to pause on Pending. Use that. A resolution SLA that keeps counting while you wait for a customer’s screenshots produces false breaches and teaches the team to ignore the number.
Step 5: migrate the old threads, or archive them
Hiver imports existing Gmail labels into views, which is convenient and also the trap: a mailbox with 60 labels produces 60 views, most of them meaningless. Before you import, archive or delete labels that represent projects rather than support.
If you’re coming from a separate helpdesk, don’t migrate history. Export it to a searchable place and start the Hiver mailbox clean. Half-migrated history confuses SLAs and reporting for months.
Where Gmail-based support stops working
Around 8–12 agents, or roughly 1,500 tickets a month, the constraints start to bite:
- Reporting is per-mailbox, and cross-mailbox reporting on the lower tiers is thin.
- There is no real self-service portal — only a knowledge base or a form that creates an email.
- Automation is rule-based. Anything conditional beyond a few levels needs an external tool.
At that point Hiver still works as a front door while a proper helpdesk handles the back office. Teams often run both for a year during transition, which is ugly but survivable.
Who should pick Hiver
Teams of 2–10 that live in Gmail and want helpdesk discipline without a new tool to learn. Shared inboxes for sales, partnerships and ops teams — not just support — get the same value.
Who shouldn’t: companies needing a customer portal, multi-brand help centres, or heavy reporting. And any team on Outlook — Hiver’s Outlook product exists but the ecosystem is thinner and the feature gap shows.
Quick Summary
- Hiver adds assignment, status, collision detection and SLAs to a shared Gmail/Workspace inbox.
- Setup takes about an hour for five agents; needs a Workspace super admin and a Google Group mailbox.
- Three views — Unassigned, Mine open, Pending — beat a view per segment.
- First-response SLAs only at the start; pause on Pending or you’ll generate false breaches.
- Scales to roughly 8–12 agents; beyond that, no portal and thin reporting start to hurt.
Related guides
- Set up Zoho Desk ticketing in one afternoon — the full helpdesk path once a shared inbox stops scaling.
- Deploy Typewise for support reply drafting — drafting help inside the same compose window.
