The pattern
Most growing teams end up with several support addresses — support@, sales@, billing@, renewals@. You probably want each one to land in its own Scrambl inbox so the right team picks it up with the right defaults.
The rule is simple: create one forwarding rule per source address. Each rule filters by its envelope recipient and rewrites to the matching Scrambl inbox. Rules are independent — adding or removing one doesn't affect the others.
Example mapping
| Customer-facing address | Scrambl inbox | Why |
|---|---|---|
support@yourcompany.com | support@inbox.scrambl.com | Default assignees: support team. Default priority: Medium. |
billing@yourcompany.com | billing@inbox.scrambl.com | Default assignees: finance team. Default stage: Needs accounting. |
sales@yourcompany.com | sales@inbox.scrambl.com | Default assignees: AE on duty. Default tags: inbound-contact. |
Setting it up
- In Tickets → Settings → Inboxes, create one Scrambl inbox per source address.
- For each inbox, set its defaults (assignees, priority, stage, tags) so the routing decision is made at intake, not later by a teammate.
- In your mail provider, create one forwarding rule per address —
support@→ support inbox,billing@→ billing inbox, and so on. Each rule is its own setting. - Send a test email to each source address and confirm the ticket lands in the correct Scrambl inbox.
Don't try to handle multiple addresses with one rule. Mail-provider rules can only redirect to one destination at a time. Bundling several addresses into one rule means tickets pile into the wrong inbox and lose their defaults.
When to use a catch-all instead
If you want every address at a domain to land in a single inbox (e.g. *@support.yourcompany.com → support inbox), use the catch-all flag on that inbox instead of writing many rules. See Catch-all inboxes.