How to forward a support email address to your helpdesk

Forwarding is how almost every helpdesk receives email, and it's the step where most setups stall. Here's how to do it in Google Workspace, Microsoft 365 and cPanel, and how to diagnose it when mail vanishes without an error.

The model is the same everywhere. Your client keeps their existing [email protected] address, because their customers already have it. That address forwards to a unique intake address generated by your helpdesk. Mail arrives, becomes a ticket, and replies go back out under the client's brand. The customer never sees the plumbing.

Before you start, get the intake address from your helpdesk. In Boridesk it appears on the client's card as soon as you add them, in the form [email protected], with a copy button next to it. Other platforms put it in channel or mailbox settings.

Google Workspace and Gmail

There are two paths depending on whether the support address is a full user account or a group. Groups are the better choice for shared addresses, and most companies already have it set up that way.

If support@ is a Google Group

1. Go to groups.google.com and open the support group.
2. Click Group settings → Members → Add members.
3. Add the helpdesk intake address as a member, and set its subscription to Each email.
4. Under Posting policies, make sure external senders are allowed to post, otherwise customer mail bounces before it reaches you.

The group route avoids Gmail's forwarding confirmation step entirely, which is why it's worth checking first.

If support@ is a regular Gmail account

1. Sign in to that account and open Settings → See all settings → Forwarding and POP/IMAP.
2. Click Add a forwarding address and paste the helpdesk intake address.
3. Gmail sends a confirmation email to that address. Because the destination is your helpdesk, that confirmation arrives as a ticket. Open it and click the link inside, or copy the confirmation code back into Gmail.
4. Select Forward a copy of incoming mail to, and choose keep Gmail's copy in the Inbox while you're testing. Switch to archive or delete once you trust it.
5. Click Save Changes at the bottom. This is easy to miss and nothing works without it.

Microsoft 365 and Outlook

Microsoft 365 shared mailboxes are the usual setup for a company support address, and forwarding is configured by an admin rather than in Outlook itself.

1. Sign in to the Microsoft 365 admin center at admin.microsoft.com.
2. Go to Teams & groups → Shared mailboxes (or Users → Active users if support@ is a licensed user).
3. Select the support mailbox, then under Mail find Email forwarding and click Manage email forwarding.
4. Tick Forward all emails sent to this mailbox and enter the helpdesk intake address.
5. Tick Keep a copy of forwarded email in this mailbox while testing.
6. Save.

Two things to watch on Microsoft 365. First, some tenants have an anti-spam outbound policy that blocks automatic forwarding to external domains. If mail isn't arriving and there are no errors in the mailbox, ask the admin to check the outbound spam filter policy for automatic forwarding rules. Second, if the organisation uses mail flow rules, one of those may be intercepting messages before forwarding applies.

cPanel

Common for clients on shared hosting with their own domain. This is the simplest of the three.

1. Log in to cPanel and open Email → Forwarders.
2. Click Add Forwarder.
3. In Address to Forward, enter support and pick the domain.
4. Choose Forward to Email Address and paste the helpdesk intake address.
5. Click Add Forwarder.

cPanel forwarders take effect immediately and require no confirmation. If the address also exists as a real mailbox, the forwarder runs alongside it, so mail is both delivered and forwarded.

Testing it properly

Do not test by emailing the support address from an account inside the same organisation. Internal mail sometimes takes a different path and can succeed when external mail fails, which produces a false pass.

Test like a customer:

1. Send a message to [email protected] from an outside address (a personal Gmail account works).
2. Confirm a ticket appears in the helpdesk within a minute or two.
3. Reply from the helpdesk and check the reply arrives at the outside address, showing the client's name rather than yours.
4. Reply again from the outside account. This is the step people skip and it's the important one: the response should land on the existing ticket rather than opening a new one.

That fourth step verifies threading, which is what makes a helpdesk a conversation rather than a pile of disconnected messages. If each customer reply creates a fresh ticket, your reply-to address is wrong.

When mail disappears silently

Forwarding failures are usually quiet. Here's what to check, in order of how often it's the cause.

Symptom	Likely cause
Nothing arrives at all, no errors	Gmail forwarding never confirmed, or Microsoft 365 outbound spam policy blocking external forwarding
Some mail arrives, some doesn't	A filter or mail flow rule is catching messages before the forward applies
Mail arrives but bounces back to the customer	The helpdesk doesn't recognise the intake address. Check for typos and confirm the client is set up on your side
Every reply creates a new ticket	Replies are being sent from a different address than the one customers write to
Duplicate tickets for one message	Two forwarding rules pointing at the same destination, or a group and a forwarder both active

The forwarding loop

One failure worth naming because it's spectacular when it happens. If the support mailbox forwards everything to the helpdesk, and the helpdesk sends notification emails back to that same mailbox, each notification gets forwarded in, treated as a customer reply, and generates another notification. A single message can produce hundreds within minutes.

Any competent helpdesk should drop mail that originates from its own notification addresses. Boridesk does this and ignores it silently rather than bouncing. But it's worth being deliberate about which mailbox forwards where, and avoiding forward-all rules on a personal account that also receives helpdesk notifications.

A note on what customers see

Forwarding only handles the inbound direction. The outbound direction is what determines whether your client's customers notice anything, and it's worth checking explicitly: send yourself a test reply and look at the From name, the From address, the signature and the footer as a customer would see them.

If any of those carry your agency's name rather than your client's, fix it before you go live. Customers are not supposed to learn that support is outsourced, and the first reply is where they'd find out.