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 addressScrambl inboxWhy
support@yourcompany.comsupport@inbox.scrambl.comDefault assignees: support team. Default priority: Medium.
billing@yourcompany.combilling@inbox.scrambl.comDefault assignees: finance team. Default stage: Needs accounting.
sales@yourcompany.comsales@inbox.scrambl.comDefault assignees: AE on duty. Default tags: inbound-contact.

Setting it up

  1. In Tickets → Settings → Inboxes, create one Scrambl inbox per source address.
  2. For each inbox, set its defaults (assignees, priority, stage, tags) so the routing decision is made at intake, not later by a teammate.
  3. 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.
  4. 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.