A support email address is the first support system most companies have. It is also where most early support problems start: a founder's inbox that nobody else can see, a group address where three people reply to the same customer, or replies that land in spam because the domain was never authenticated.
This guide walks through setting up support@yourcompany.com properly for a team of two to ten people: which address to use, the three ways to route it, how to keep your replies deliverable, and when it is time to move from a mailbox to a shared inbox.
Step 1: Pick the address
Use one obvious address and publish it everywhere: your website footer, your app, receipts, and onboarding emails. Customers should never have to guess.
- support@ is the clearest choice for product questions and problems.
- help@ works too, but pick one. Running both splits your queue.
- hello@ or contact@ is better for sales and general enquiries, not support.
- Never send support replies from noreply@. It tells customers you do not want to hear back, and their replies bounce.
Step 2: Choose how the address is routed
There are three common ways to set up a support address. They differ in who can see incoming mail and whether you can tell who is handling each email.
| Option | How it works | Good for | Breaks when |
|---|---|---|---|
| Alias on one mailbox | support@ delivers into one person's inbox (a Google Workspace or Microsoft 365 alias) | A solo founder | A second person needs to help, or that person is away |
| Group or shared mailbox | Everyone in a Google Group or Microsoft 365 shared mailbox sees every email | Two or three people with low volume | Nobody knows who is replying, so emails get missed or answered twice |
| Shared inbox tool | support@ forwards into a tool that turns each email into a ticket with an owner and status | Two or more people answering customers | You need phone, chat, and a large app marketplace on day one |
If you are the only person answering customers, an alias is fine. Once a second person helps, the group option feels natural, but it is where duplicate replies and dropped threads begin. A shared inbox keeps the same address and adds the missing piece: one owner per conversation. Read when startups need a shared inbox for the signs.
Step 3: Forward support@ instead of moving your mail
You do not need to change your MX records or move your company email to set up a shared support inbox. The safest setup is forwarding: your existing mail host keeps receiving mail for your domain and forwards a copy of support@ to the support tool.
- Create support@ in your mail host (Google Workspace, Microsoft 365, or your domain provider) as a group, alias, or mailbox.
- Add a forwarding rule that sends everything for support@ to your support tool's receive address.
- Leave your MX records alone so the rest of your company email keeps working.
- Send a test email from a personal account and confirm it arrives as a new conversation.
In Troppus, the receive address is on Admin → Domains. Forward support@ there and new emails open as tickets. The email setup guide covers the details, including optional direct MX for teams that want it.
Step 4: Authenticate your domain so replies are delivered
Receiving is only half the job. When you reply as support@yourcompany.com, Gmail, Outlook, and Yahoo check that the sender is allowed to send for your domain. Unauthenticated replies are more likely to land in spam or be rejected. Three DNS records handle this:
- SPF lists the services allowed to send email for your domain.
- DKIM adds a cryptographic signature that proves the email was not altered and came from an authorized sender.
- DMARC tells receiving servers what to do when SPF or DKIM fails, and sends you reports. Start with p=none to monitor, then tighten to quarantine once everything passes.
If replies go out through a support tool, that tool must be authorized for your domain too. In Troppus you add your domain, publish the records shown on the domain page, and click Verify. Once it passes, replies go out as support@yourcompany.com instead of a shared platform address. See email sending.
Step 5: Set expectations with an automatic reply
A short confirmation tells customers their email arrived and when to expect a human. Keep it plain: thank them, give a realistic response time, and point to any self-serve help. Avoid long templates that read like a ticket number receipt.
Troppus workflows can send this on new inbound email, route by address or subject, and assign a group before anyone opens the ticket.
Step 6: Agree on a few team rules
- Every conversation has exactly one owner. Assign before you reply.
- Reply from support@, never from a personal address, so the customer's next email comes back to the team.
- Use private notes for internal discussion instead of forwarding the email around.
- Close conversations when they are resolved so the open queue reflects real work.
- Agree a target first-response time, even an informal one like same business day.
Common mistakes to avoid
- Changing MX records to point at a support tool and breaking the rest of your company email. Forwarding avoids this.
- Replying from a personal inbox, which moves the conversation out of the team's view.
- Skipping SPF, DKIM, and DMARC, then wondering why customers say they never got a reply.
- Publishing several support addresses, which splits the queue across inboxes.
- Using a Google Group or distribution list long after two people are answering, so replies collide.
Frequently asked questions
Can I set up a support email for free?
Yes. If you already pay for Google Workspace or Microsoft 365, an alias, Google Group, or Microsoft 365 shared mailbox costs nothing extra. The cost shows up later as missed emails and duplicate replies once more than one person is answering.
Should support@ be a group or a mailbox?
For a forwarding setup it barely matters: either works as long as mail reaches your support tool. Pick whatever your mail host makes easiest, and make sure forwarding to external addresses is allowed by your admin settings.
Will forwarding hurt deliverability?
Forwarding affects inbound mail, not your replies. Reply deliverability depends on your domain authentication. As long as the tool that sends replies is authorized with SPF and DKIM for your domain, replies are treated like any other email from your company.
When should I move from Gmail to a shared inbox?
When a second person starts answering customers, when you lose track of who replied, or when a customer has to follow up because their email slipped. Compare options in best customer support software for startups.
The bottom line
A good support email setup is one published address on your company domain, forwarded into a place the whole team can see, authenticated so replies reach the inbox, and run with one owner per conversation.
Troppus gives small teams that setup in an afternoon: forward support@, verify your domain, and answer every customer from one shared inbox. Create a workspace to try it.