How to Set Up a Support Email Address: Ownership, Forwarding and First-Week Checks
Move customer email out of personal inboxes: pick an owned address, forward it, prevent reply loops, assign owners and test it for a week.
- Updated
- Reading time
- 12 min read
11 sections
- Which setup fits your team?
- Step 1: Pick an address your company owns
- Step 2: Route the mail to where it will be read
A support email address works when four things are true: the company owns the address, more than one person can see every message, each message has one owner, and automatic replies cannot loop. Set it up in this order: create the address in your own domain, decide where it is read (a shared mailbox, a group inbox or a help desk), forward or route it there, then test replies, auto-replies and ownership for a week before you print it anywhere.
This guide is vendor-neutral. It cites Google Workspace, Microsoft 365 and the email standards that apply to every provider, checked November 12, 2026. Chatsy publishes this blog and sells a forwarding-based support inbox; the Chatsy-specific steps are in one clearly marked section and in our support email setup docs.
Which setup fits your team?
Most teams pick one of three models. The table compares them on the questions that cause trouble later.
| Model | How it works | Who can reply | Ownership per message | Fits |
|---|---|---|---|---|
| Shared mailbox (Microsoft 365) | One mailbox that several licensed users open | Members with Send As or Send on Behalf permission | None built in; agree a folder or category rule | 2 to about 10 people, low volume |
| Group inbox (Google Groups Collaborative Inbox) | Mail goes to a group; members work it in Groups | Group members | Assign a conversation, then mark it complete, no action needed, or duplicate (three separate states) | Google Workspace teams that want assignment without a new tool |
| Help desk or ticket inbox | Your address forwards into a tool that creates numbered tickets | Seats in that tool | Status, assignee and history per ticket | Teams that need reporting, saved replies or chat and email in one place |
Microsoft documents that a shared mailbox can store up to 50 GB without its own license, that users need their own licensed Exchange Online mailbox to open it, that only people inside your organization can use it, and that it supports a maximum of 25 users (Microsoft Learn: About shared mailboxes). Google's Collaborative Inbox lets members assign a conversation to themselves or another member and mark it as complete, no action needed, or duplicate (Google Workspace: Use a group as a Collaborative Inbox).
A rule of thumb from those limits: if nobody needs to know who owns a message, a shared mailbox is enough. Once two people answer the same customer twice in a week, you need assignment, which means a group inbox or a help desk.
Step 1: Pick an address your company owns
Create the address on your own domain, for example support@yourcompany.com, not a personal Gmail or an employee's mailbox. When a person leaves, a personal address leaves with them, and customers keep writing to it.
Decide three things before you create it:
- The name.
support@andhelp@are the common choices. Pick one, and if you already receive mail at the other, route both to the same place instead of running two queues. - The administrator. Name one admin who controls the mailbox, its forwarding and its password or sign-in policy. The same Microsoft page recommends blocking direct sign-in to a shared mailbox account and keeping it blocked, because people should open it through their own accounts.
- What it is for. Write one sentence, such as "Questions from customers about orders, billing and product use." Sales enquiries, job applications and vendor invoices go elsewhere, or your support queue fills with mail nobody on support can answer.
Step 2: Route the mail to where it will be read
Routing is where most setups break. There are two common patterns.
Forwarding from the mailbox. The address stays a normal mailbox, and a forwarding rule sends a copy of each new message to the tool or group that works the queue. In Gmail, you add a forwarding address under Settings → See all settings → Forwarding and POP/IMAP. Gmail then sends a verification link to the destination address, and forwarding starts only after someone opens that link. Automatic forwarding sends all new messages except spam; to forward only some messages, Google says to use a filter instead (Gmail Help: Automatically forward messages).
Delivering straight to a group or alias. The address is a group or alias rather than a mailbox, so mail lands in the group inbox directly. This avoids a forwarding hop, but you lose a plain mailbox copy unless you add one.
Whichever you use, keep a copy in the original mailbox for the first week. If forwarding fails silently, the copy is the only record of what customers sent.
The verification gotcha. When the destination is a help desk, the forwarding confirmation from Gmail or another provider goes to the help desk's address, not to a person. Look for it as a new ticket or message in the tool, open it and click the link. Many stalled setups are just an unclicked confirmation email.
Step 3: Decide who owns each message
Write the ownership rule down before launch. Three workable rules:
| Rule | How it works | Risk |
|---|---|---|
| Claim on open | The first person to open a message assigns it to themselves | Hard messages wait while easy ones get claimed |
| Round by day | One person owns the queue each day and passes unfinished messages to the next day's owner | Coverage gaps on sick days |
| Assign on arrival | A lead assigns each message to a named owner | The lead becomes a bottleneck as volume grows |
Pair the rule with statuses that mean the same thing to everyone. For example, use "Open" for waiting on us, "Pending" for waiting on the customer, and "Resolved" for answered with nothing left to do. In a plain shared mailbox, folders or categories can stand in for statuses, but nothing stops two people replying at once, and Microsoft's shared-mailbox page notes that you cannot prevent users from deleting messages in it.
Step 4: Stop auto-reply loops before they start
An acknowledgement email ("We got your message") is useful, but two automatic systems replying to each other can keep emailing until someone notices. The email standard for automatic responses, RFC 3834, says automatic responses should not be sent in reply to any message whose Auto-Submitted header has a value other than no. It also says responders may ignore messages that carry List-* headers, which mailing lists add (RFC 3834, Recommendations for Automatic Responses to Electronic Mail).
What that means in practice:
- Turn on only one auto-reply. If the mailbox has an out-of-office rule and the help desk sends an acknowledgement, switch one off.
- Do not forward your support address to a second address that also auto-replies.
- Test with a sender that has an out-of-office reply switched on. You should see one acknowledgement and no second round.
Step 5: Make replies trustworthy
Customers and mailbox providers both judge your replies. Two checks matter.
Sender authentication. Google's email sender guidelines require every sender to Gmail accounts to set up SPF or DKIM for the sending domain, have valid forward and reverse DNS, use TLS, and keep the spam rate reported in Postmaster Tools below 0.3%. Senders of 5,000 or more messages a day must also set up DMARC and align the From domain with SPF or DKIM (Google: Email sender guidelines). A support address rarely reaches 5,000 a day, but if your help desk sends replies through its own servers, ask how it authenticates mail sent "from" your domain.
Signatures and reply text. Use a team signature, not a personal one with a direct phone number you cannot staff. Put the expected response time in the acknowledgement, and only promise hours you actually cover.
A worked example: a five-person online store
This is an illustrative setup, not a customer case. A store with five staff receives about 40 customer emails a day at an employee's address and decides to move them.
| Decision | Choice | Why |
|---|---|---|
| Address | support@store.example, admin = operations lead | Owned by the company; one person controls forwarding |
| Where it is read | Help desk ticket inbox | Two people answer email and need assignment |
| Routing | Gmail forwarding to the help desk address, copy kept in the mailbox | Fast to set up; the copy is a safety net |
| Ownership | Round by day, with a weekly rota | 40 a day is manageable for one owner |
| Auto-reply | Help desk acknowledgement only; mailbox vacation reply off | One automatic system, no loop |
| Status meaning | Open = us, Pending = customer, Resolved = done | Same words in every reply |
The arithmetic for staffing: at 40 messages a day and an estimated 6 minutes each, the queue needs about 240 minutes, or 4 hours a day of one person's time. Measure your own handling time in week one and redo this sum.
First-week checks before you announce the address
Run these checks before the address goes on your website, invoices and order emails.
| Day | Check | Pass when |
|---|---|---|
| 1 | Send a test from an outside account | It arrives once, in the right place, within a few minutes |
| 1 | Reply from the tool | The customer sees your support address, and their answer threads back to the same conversation |
| 2 | Send from an address with an out-of-office reply | Exactly one acknowledgement, no loop |
| 2 | Send an attachment and a long thread | Attachments open; the thread stays together |
| 3 | Check spam folders at Gmail and Outlook test accounts | Your replies land in the inbox |
| 5 | Review ownership | Every message from the week has one owner and a status |
| 7 | Count volume and handling time | You can redo the staffing arithmetic with real numbers |
Only after day 7 should you update the contact page, order confirmation emails and help-center footer.
Setting up a support email in Chatsy
Chatsy's Inbox uses the forwarding model. It needs the Inbox module, which is included on the Hobby plan and above (1 mailbox on Hobby, 2 on Standard, 5 on Pro). Free does not include a mailbox. The steps, as written in the Chatsy docs:
- Create a mailbox. Chatsy gives it its own forwarding address and shows a checklist titled "Connect your support email".
- Verify your address. Chatsy sends a 6-digit code to your support address; it expires after 15 minutes, and the mailbox does not accept email until the address is verified.
- Forward your support address to the Chatsy forwarding address in your email provider. If the provider sends a confirmation link, it arrives in the Chatsy mailbox as a new ticket.
- Send a test email from another account. It should arrive as a new numbered ticket.
Tickets have statuses (Open, Pending, Resolved, Closed, Spam), priorities, one assignee, tags and saved replies with placeholders such as the customer's first name and ticket number. An optional auto-reply acknowledges each new email with its ticket number. Replies go out through Chatsy's email service with reply-to set to the mailbox's Chatsy address, or through your own Postmark account if you connect one; Chatsy has no separate custom sending-domain or DKIM setup beyond that. See shared inbox and email tickets for what the module includes.
When this setup is not enough
A forwarded support address with a small ticket inbox is the wrong tool in some cases:
- You need SLA timers, routing rules or round-robin assignment. A full help desk such as those in our help desk software comparison covers these; Chatsy's mailbox does not.
- More than 25 people need the same Microsoft 365 mailbox. Microsoft's own limit points you to a group or a help desk.
- Email is not where customers are. If most questions arrive in chat, set that up first; see how to add live chat to your website.
- Regulated data arrives by email. Health or payment details need a provider and contract your compliance team has approved. Do not route them into a tool just because forwarding is easy.
Frequently asked questions
Should the support address be a shared mailbox or a group?
Use a shared mailbox for a few people who do not need assignment. Use a group inbox or help desk once you need to know who owns each message. Microsoft caps shared mailboxes at 25 users, and Google's Collaborative Inbox adds assignment and resolution states.
Why did forwarding not start?
Usually the destination never confirmed it. Gmail, for example, sends a verification link to the forwarding address and only forwards after that link is opened. If the destination is a help desk, look for the confirmation as a new ticket there.
Can customers see who answered?
That depends on the tool. Shared mailboxes can send as the mailbox, so the customer sees the support address. Most help desks send from the support address and show the agent's name in the signature.
Do I need DMARC for a support address?
Google requires DMARC for senders of 5,000 or more messages a day to Gmail accounts and SPF or DKIM for everyone. Setting up all three on your domain is good practice either way, and it is your domain administrator's job, not the help desk's.