Three months ago, I watched a 4-person startup lose a $12,000 deal because their sales@ address was forwarding to a founder's personal inbox — and he was on vacation. Nobody else could see the inquiry. By the time he got back, the prospect had signed with a competitor.

Ouch.

That's a $12,000 lesson in why role-based email matters. (I've made similar mistakes. Not quite that expensive, but close enough that I don't want to talk about it.)

But here's the thing most email guides get wrong: they assume you want to pay $7/user/month for Google Workspace or $6/user/month for Microsoft 365 just to get basic shared mailbox functionality. You don't have to. A well-structured alias system costs nothing extra on most providers — including flat-fee hosts like JustEmails where you're already paying $49/year for unlimited mailboxes.

This guide covers how to set up role-based addresses (support@, sales@, billing@, and whatever else you need), when to use aliases versus actual shared mailboxes, how to route messages so the right people see them, and how to avoid the chaos that comes when three people reply to the same customer email without knowing about each other. If you haven't set up your custom domain email yet, start with our custom domain email setup guide first.

What We're Building

By the end of this, you'll have a functional email structure where:

Role-based addresses (support@, sales@, billing@, etc.) route to the right people
Multiple team members can see and respond to incoming messages
Customers always see a professional role address, not individual names
You're not paying per-seat fees for each person who needs access

If you're managing multiple domains — agency owners, SaaS founders with product domains, anyone running more than one brand — this structure scales across all of them.

Prerequisites

A custom domain with email hosting configured
Admin access to your email provider's dashboard
A list of the functional addresses you actually need (we'll help you figure this out)
Basic familiarity with email aliases and forwarding

Step 1: Map Out Your Role Addresses

Before you touch any settings, decide what addresses you actually need. Most businesses over-engineer this. You don't need 15 role addresses on day one.

Core addresses most businesses need:

Address	Purpose	Who receives it
support@ or help@	Customer support inquiries	Support team or founder
sales@ or contact@	Sales inquiries, partnerships	Sales team or founder
billing@ or invoices@	Payment issues, invoice requests	Finance person or founder
info@	General catch-all for public forms	Whoever handles inbound

Optional addresses (add when needed):

team@ — internal announcements
marketing@ — vendor pitches
dev@ — technical contacts, API issues
careers@ — if you're hiring

Here's my take: most startups create way too many addresses because it feels professional. Then nobody checks careers@ for six months, and a candidate's follow-up sits there rotting. I've seen it happen. Honestly, I've been the person who forgot about an alias for three months. Start with 3-4 addresses. Add more when you have volume.

Step 2: Choose Your Architecture — Aliases vs. Shared Mailboxes

This is where most guides gloss over the tradeoffs. Both approaches work, but they're different.

Aliases (forwarding addresses)

An alias forwards incoming email to one or more real mailboxes. It's not a mailbox itself — it has no inbox, no sent folder, no login.

Example: support@yourdomain.com → forwards to sarah@yourdomain.com and mike@yourdomain.com

Pros:

Free on almost every provider
Easy to set up (30 seconds per alias)
Everyone sees incoming mail in their own inbox
No extra credentials to manage

Cons:

No shared "sent" folder — Sarah and Mike can't see what the other replied
Replies come from individual addresses unless you configure "Send As"
Collision risk — both might reply to the same email
Harder to track what's been handled vs. what hasn't

Shared mailboxes

A shared mailbox is an actual mailbox that multiple people access. It has its own inbox, its own sent folder, and its own login credentials (or delegated access).

Pros:

Everyone sees what's been sent and received
Replies come from the shared address automatically
Easier to coordinate who's handling what
Feels more like a team inbox

Cons:

Some providers charge extra for shared mailboxes
Managing access requires more setup
Can be confusing if not everyone knows the workflow

My recommendation for teams under 10 people: Start with aliases. They're free, they work, and they force you to establish communication habits ("I'm handling this one" messages) that you'll need anyway. Graduate to shared mailboxes or help desk software when alias-based coordination becomes painful. And look — I know "painful" is vague. You'll know it when you get there. If you're dreading checking the support inbox because you're not sure what's been handled, that's the sign.

On JustEmails, both approaches are included in the $49/year flat fee. You can create unlimited aliases at no extra cost, or set up actual shared mailboxes and grant access to team members ($2/member/month for additional team seats). No per-mailbox charges, no alias limits. See our breakdown of flat fee vs per-mailbox pricing to understand why this matters at scale.

Step 3: Set Up Aliases for Your Role Addresses

The exact steps vary by provider. Here's how to do it on the common ones.

JustEmails

Dashboard → Domains → select your domain
Click "Aliases" or "Email Addresses"
Create new alias: support@yourdomain.com
Set destination(s): sarah@yourdomain.com, mike@yourdomain.com
Save

Takes about 30 seconds per alias. You can add multiple destinations (comma-separated), so both Sarah and Mike receive every support@ email.

Google Workspace

Admin console → Directory → Groups
Create a group: support@yourdomain.com
Add members (Sarah and Mike's accounts)
Set "Who can post": Anyone on the internet
Save

Google calls these "groups" rather than aliases, but the effect is the same. Requires Workspace admin access. If you're considering switching from Workspace to reduce costs, we wrote a migration guide from Google Workspace that covers the process step-by-step.

Microsoft 365

Admin center → Groups → Shared mailboxes (or distribution lists)
Create new: support@yourdomain.com
Add members
Configure external sender permissions
Save

Microsoft has both "distribution lists" (pure forwarding) and "shared mailboxes" (actual shared inbox). Shared mailboxes are better for role addresses — unified sent folder.

Zoho Mail

Admin console → Mail → Groups
Create group: support@yourdomain.com
Add members
Set moderation settings (usually "No moderation" for internal routing)
Save

Zoho's group functionality is solid. One quirk: you might need to enable "Allow external senders" if you want customers to email support@.

Step 4: Configure "Send As" for Replies

This is the step people skip — and then wonder why replies to support@ show up as "From: mike@yourdomain.com" instead of "From: support@yourdomain.com."

When you receive an email to a role alias that forwards to your personal mailbox, your email client doesn't automatically know to reply from the alias. You have to configure "Send As" (or "Send mail from another address") to enable this.

In Gmail (web):

Settings → Accounts → "Send mail as"
Add another address: support@yourdomain.com
Verify ownership (Google sends a confirmation email to the alias; click the link)
Choose whether to make it the default or select it manually per-email

In Outlook (desktop):

File → Account Settings → select account → Change → More Settings → Advanced tab → add the role address.

In Apple Mail:

Mail → Settings → Accounts → select account → under "Email Address," add the role address (comma-separated).

Once configured, you'll see a dropdown when composing replies. Pick the role address for customer-facing responses.

Pro tip: if you're replying to an email that came in via the alias, most clients will auto-select the matching "From" address. But double-check. I've seen founders accidentally reply from their personal address to a customer who emailed support@, and it looks unprofessional. (I've done this. It's embarrassing.)

Step 5: Prevent Collision — Coordinate Who's Replying

Two people replying to the same customer email is awkward. Three is a disaster. Here's how to prevent it without buying help desk software.

Low-tech solutions (free):

Reply-and-CC rule: When you start replying, immediately CC your teammates with "I've got this one" so they know to back off
Slack/Discord channel: Post "Handling support ticket from [customer]" when you claim an email
Label/tag system: In Gmail, star emails you're handling; teammates check before responding
Draft marker: Open the email and start a draft — some clients show "X is drafting a response"

When to upgrade to help desk software:

If you're handling 30-50+ support emails per day, or your team exceeds 4-5 people, coordination over Slack stops scaling. That's when Freshdesk (free tier for up to 10 agents), Zendesk ($19/agent/month), or Help Scout ($20/user/month) make sense. They add collision detection, ticket assignment, and SLA tracking.

But most small teams don't need them yet. I'm kind of annoyed that every "how to do email" article pushes you toward a $20/seat help desk when you have three employees. It's overkill. Save your money.

Step 6: Route Different Addresses to Different Teams

For larger setups, you might want different role addresses routed to different groups:

support@ → support team (Sarah, Mike, Lisa)
sales@ → sales team (James, Priya)
billing@ → finance (Carlos)

This is just multiple aliases with different destination lists. Set up each one separately.

Considerations:

Make sure at least 2 people receive each critical address (bus factor)
For billing@, you probably want a primary owner plus a backup
Document who receives what — new hires will ask

On JustEmails, you can manage all this from a unified dashboard. If you're running multiple domains (say, your main business plus a SaaS product like ClickzProtect or JustAnalytics), you can set up role addresses across all of them with consistent routing. For a deeper look at how we compare to alternatives, check out our JustEmails vs Google Workspace comparison.

Step 7: Test Everything

Don't assume it works. Test it. I cannot stress this enough.

Send an email to support@yourdomain.com from an external address (your personal Gmail, whatever)
Verify it arrives in all intended inboxes
Reply from one of the recipients — verify it comes from support@, not the individual address
Send to sales@, billing@, etc. — verify each routes correctly

Common issues:

Email not arriving: Check spam folders. Also verify the alias was saved (some providers require an explicit "apply" step)
Arriving but not to all recipients: Multi-destination aliases sometimes need each address added explicitly, not comma-separated
Reply coming from wrong address: "Send As" not configured, or wrong address selected when composing

Common Errors and Fixes

"Alias already exists"

You're trying to create an alias that matches an existing mailbox or alias. Either use a different name or delete the existing one first.

"Send As verification email not received"

Check the spam folder at the alias destination. If it's still not there, your provider might be blocking Google's verification emails — temporarily disable aggressive spam filtering and try again.

"Reply sent from wrong address"

Your email client defaulted to your personal address. Go back to compose, check the "From" dropdown, and reselect the role address. Then set it as default for that type of correspondence.

"Multiple people replied to the same email"

This is a coordination problem, not a technical one. Implement a claim system — Slack notification, CC, starring, something. Alternatively, graduate to shared mailboxes where collision is visible. (Honestly, this will happen at least once no matter what you do. Just apologize to the customer and move on.)

Next Steps

Now that your role-based addresses are working:

Document the structure — who receives what, and who's backup
Set up auto-responders (optional) — "Thanks for contacting support, we'll respond within 24 hours"
Configure email authentication — ensure your role addresses pass DMARC checks with our DMARC implementation guide
Review in 30 days — are any addresses getting no traffic? Remove them. Are any getting overwhelming traffic? Maybe split them or add help desk software

For multi-domain setups, replicate this structure across all your domains. The JustEmails dashboard lets you see all incoming mail across all your domains in one place — role addresses included.

Frequently Asked Questions

What's the difference between an alias and a shared mailbox?

An alias is a forwarding address — emails to support@ get forwarded to one or more individual mailboxes. A shared mailbox is a real mailbox that multiple people can log into directly using the same credentials or IMAP access. Aliases are simpler and free on most providers. Shared mailboxes give you a unified sent folder and better collaboration, but some providers charge extra for them.

How many role-based addresses should a small business have?

Most businesses need 3-5: support@ or help@, sales@ or contact@, billing@ or invoices@, info@ as a general catch-all, and optionally team-specific ones like marketing@ or dev@. Don't over-engineer it — you can always add more later. Start with the addresses customers will actually email.

Can multiple people reply from the same role-based address?

Yes, but the setup varies. With aliases forwarding to individual mailboxes, each person replies from their own address unless they configure 'Send As'. With shared mailboxes, everyone replies from the shared address automatically. Shared mailboxes are cleaner for customer-facing communication where you want replies to come from support@, not john@.

Do I need help desk software or can I just use shared email?

For teams under 5 people handling fewer than 50 emails per day, shared email works fine. Above that, you'll want ticketing, collision detection (knowing when someone else is replying), and SLA tracking — that's when Freshdesk, Zendesk, or Help Scout make sense. Don't pay for a help desk until email actually becomes painful.

Try JustEmails

Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.

Start your 7-day free trial → · How it compares

How to Set Up Role-Based Team Inboxes (support@, sales@, billing@)