Pick one method

MethodUse whenEffort
Recipient address map (recommended)You just want to redirect one address (e.g. support@yourcompany.com) to a Scrambl inbox.3 fields, ~1 minute
Custom Routing ruleYou need conditions Recipient address map can't express — multiple addresses in one rule, per-sender logic, etc.~10 fields, easy to misconfigure

Most teams should use the first method. The second is only there if you've outgrown it.


Who can do this

  • Required access: an access level that includes Tickets - Full Access.
  • Default access levels that include it: System Administrator.
  • Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
  • You also need super admin access in Google Workspace.
  • Personal accounts: Not available. This is a work feature, so it is hidden in personal (family) spaces.

Owners and admins review and change access levels in Settings → Administration → Members → Access levels.

Method 1 — Recipient address map (easy)

Recipient address map rewrites the recipient on inbound mail. You give it an original address and a destination address, and Google does the rewrite before delivery.

Steps

  1. Sign in to Google Admin as a super admin.
  2. Go to Apps → Google Workspace → Gmail → Routing.
  3. Scroll past the Routing card until you find Recipient address map. Click Configure (or Add another). An Add setting dialog opens.
  4. Description (required): short summary you'll recognize later, e.g. Forward support@ to Scrambl.
  5. 1. Map original recipient to new recipient — click Add and fill the row:
  6. 2. Messages to affect: select the All incoming messages radio (the default). Avoid Only external incoming messages — that would skip internal forwards and test emails from inside your org.
  7. 3. Routing options: leave Also route to original destination UNCHECKED. Checking it delivers to both the original mailbox and the Scrambl inbox, which duplicates every ticket.
  8. 4. Options: check Add X-Gm-Original-To header (recommended). This preserves the original support address in the message headers, which Scrambl can use to apply the right inbox's defaults if you ever consolidate multiple addresses behind one Scrambl inbox.
  9. Click Save.
  10. Wait a few minutes for propagation, send a test email from an external account to your support address, and confirm a ticket appears in Tickets.

That's it. No envelope filter to hunt for. If this method works for you, you're done.


Method 2 — Custom Routing rule (advanced)

What this rule does

You're creating a Gmail Routing rule that does one thing: when mail arrives at your existing support address (e.g. support@yourcompany.com), Google rewrites the envelope recipient to your Scrambl inbox and delivers it there instead. The customer keeps emailing your own address; Scrambl receives the message and creates a ticket. No bounces, no duplicate delivery.

You need super admin access to your Google Workspace account.

Before you start

Five things need touching: the Inbound box, the Modify-message dropdown, Account types, Envelope recipient (the action), and Envelope filter (the condition — hidden under "Show options"). Everything else stays at its default.

Walk-through

1. Open the dialog

  1. Sign in to Google Admin as a super admin.
  2. Go to Apps → Google Workspace → Gmail → Routing.
  3. Find the Routing card and click Configure (or Add another rule if rules already exist).
  4. Name the setting something memorable, e.g. Support emails to Scrambl.

2. Email messages to affect

OptionState
Inbound✓ Check
OutboundLeave unchecked
Internal — SendingLeave unchecked
Internal — ReceivingLeave unchecked

3. For the above types of messages, do the following

From the dropdown, choose Modify message. The rest of the form is the action config.

4. Account types this action should apply to

Check all three:

  • ✓ Active user accounts — covers normal mailboxes
  • ✓ Group accounts — covers Google Groups (a common pattern for support@)
  • ✓ All inactive and unrecognized accounts — covers aliases or addresses that aren't provisioned

Leave Archived accounts with assigned delegate unchecked.

5. Envelope recipient — redirect to Scrambl

Heads-up: This is the action field (what to do). The filter field that limits which messages it applies to is called Envelope filter and is hidden — we'll get to it in step 6. Don't confuse them — they sit in different parts of the form.

Scroll down past Headers, Subject, and Route until you reach Envelope recipient. Configure exactly this:

  1. Check Change envelope recipient.
  2. Select the Replace recipient radio.
  3. In Enter new email address, paste the Scrambl inbox address you copied earlier.

Leave Replace username and Replace domain alone — they only rewrite half of the address and aren't what you want.

6. Show options → Envelope filter — limit to your support address

This is the step most people miss. Without it, the rule applies to every inbound message — not just your support address.

  1. Scroll all the way to the bottom of the dialog, past Encryption.
  2. Click the Show options link. This reveals additional sections including Address lists and Envelope filter.
  3. Inside Envelope filter: check Only affect specific envelope recipients.
  4. Choose Single email address.
  5. Enter your support address, e.g. support@yourcompany.com.

7. Everything else stays at its default

Don't touch these sections — the defaults are correct and changing them will break or duplicate delivery:

SectionWhy skip
HeadersX-Gm-* and custom headers aren't needed for forwarding.
SubjectDon't prepend — keeps the original subject in Scrambl.
RouteThis is not what you want. "Change route" sends mail to a different SMTP server. The setting you actually want is "Change envelope recipient" above (step 6).
SpamBypass-spam isn't relevant.
AttachmentsLeave attachments intact.
Also deliver toThis duplicates delivery (sends to both addresses). We want to redirect, not copy.
EncryptionDefaults are fine.

8. Save and verify

  1. Click Save.
  2. Wait a few minutes for Google to propagate the rule.
  3. Send a test email to your support address from an external account.
  4. Confirm a ticket appears in Tickets within ~30 seconds.

Troubleshooting

SymptomLikely cause
I can't find "Envelope filter" anywhere in the dialog.It's hidden by default. Scroll past Encryption to the bottom of the dialog and click Show options — Envelope filter appears in the panel that opens. (You're probably confusing it with Envelope recipient, which is the action field higher up. They sound similar but do different things.)
Every inbound email got redirected, not just the support address.You skipped step 6. Without an Envelope filter, the rule applies to all inbound mail. Open the rule, click Show options, and add the filter for your specific support address.
Test email doesn't create a ticket.Make sure "Inbound" is checked (step 2), "Modify message" is the action (step 3), the envelope filter matches your address exactly (step 6), and the Scrambl inbox address in step 5 is correct.
Customer gets a "Message not delivered" bounce.The Scrambl inbox address in step 5 is wrong. Open the inbox under Tickets → Settings → Inboxes, copy the full address, and re-paste it into the rule.
Mail arrives but goes to TWO places.You configured "Also deliver to" instead of (or in addition to) "Change envelope recipient". Remove the "Also deliver to" entry — we want redirect, not duplicate.
Reply from Scrambl doesn't thread in the customer's Gmail.Scrambl sets Message-ID / In-Reply-To correctly. A corporate mail filter rewriting headers can break threading — check any third-party security gateways in the path.
Sender shows as your tenant, not the customer.You picked the wrong action type (e.g. "Forwarding" via a per-user filter, instead of a domain Routing rule). Delete the user-level filter and use the Admin → Routing rule described above.

Multiple addresses

If you need to route several addresses (e.g. support@, billing@, sales@) to different Scrambl inboxes, create one Routing rule per pair. Each rule has its own envelope filter and its own envelope-recipient destination. See Route multiple support addresses.