How to Set Up a Shared Inbox for Multiple Support Aliases
Set up a single shared inbox that gathers messages from every support alias your team uses. Follow these practical steps to avoid duplicate tickets and missed replies.
On this page
A shared inbox lets your support team see every customer message in one place, no matter which alias — support@, help@, billing@ — the customer used. Before you start, decide which platform will host the inbox and make sure you have admin access to each email alias you want to connect.
1. Choose a Platform
Pick a tool that supports a true shared inbox, automatic email‑to‑ticket conversion, and team collaboration without per‑agent fees. NeuraDesk offers all of those features free, including AI reply suggestions and ticket status tracking. If you prefer to stay in Google Workspace or Microsoft 365, you can build a shared inbox in Gmail or Outlook, but you will need to configure delegation and forwarding manually. The platform you choose determines how much ongoing maintenance you’ll face.
2. Create the Shared Inbox
In your chosen platform, create a new shared mailbox or team inbox. Give it a clear name such as "Support Team" so every agent recognises it. Add the members who will handle tickets and set their permission level (full access, send‑as, or read‑only). If you use Gmail, follow the steps in How to Set Up a Shared Inbox in Gmail for a Support Team. For Outlook, see How to Set Up a Shared Inbox in Outlook for a Support Team.
Why it matters: A properly provisioned inbox is the single source of truth. Without it, agents may reply from personal accounts, creating duplicate threads.
Common mistake: Forgetting to grant "send‑as" rights, which forces agents to reply from their own address and breaks the shared‑inbox view.
3. Add Each Support Alias as a Forwarding Address
Log into the admin console for each domain (e.g., Google Admin, Microsoft 365 Admin, or your DNS provider). Create a forward rule that sends every message received at support@, help@, billing@, etc., to the shared inbox address you just created. Keep a spreadsheet of alias → forward destination so you can audit later.
Why it matters: Forwarding consolidates all inbound mail before it reaches any agent. It also preserves the original sender address for reporting.
Common mistake: Setting up a forward that also keeps a copy in the alias mailbox. That creates two copies of every ticket and inflates storage.
4. Set Up Routing Rules Inside the Shared Inbox
Once mail lands in the shared inbox, use rules (or automations) to tag, assign, or move tickets based on the original alias, subject keywords, or sender domain. For example, route all billing@ mail to a "Billing" tag and assign it to the finance‑focused agent. Detailed rule creation is covered in How to Set Up Email Routing Rules in a Shared Inbox.
Why it matters: Routing reduces manual triage and ensures the right specialist sees the ticket first.
Common mistake: Over‑complicating rules with too many conditions, which makes them fragile and hard to debug.
5. Define Roles, Permissions, and Collaboration Norms
Decide who can close tickets, who can reopen, and who can add internal notes. Document a short run‑book: how to @mention a colleague, when to escalate, and how to use AI reply suggestions if your platform provides them.
Why it matters: Clear roles prevent duplicate work and keep response times predictable.
Common mistake: Giving every agent full admin rights; a single mis‑click can delete a rule or change a forwarding address.
6. Test the End‑to‑End Flow
Send a test email to each alias from an external address. Verify that:
- The message appears in the shared inbox.
- The correct tag or assignment is applied.
- The assigned agent receives a notification.
- A reply sent from the shared inbox reaches the customer with the correct "from" address.
Fix any forwarding loops, missing tags, or permission errors before you go live.
Why it matters: A quick test catches configuration gaps that would otherwise cause missed tickets on day one.
Common mistake: Testing only one alias and assuming the rest behave identically.
7. Monitor and Iterate
After launch, review ticket volume per alias, average first‑response time, and any tickets that fall through the cracks. Adjust routing rules, add new aliases, or refine permissions as the team grows. A free shared inbox can handle multiple domains without extra cost, so scaling is a matter of configuration, not budget.
Try NeuraDesk free to get a shared inbox with automatic email‑to‑ticket conversion and AI reply suggestions in minutes.
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free