Multi-Alias Email

A single Ticket0 workspace can receive from multiple email addresses — one per product, region, or team function. There's no "separate inbox per address" — all addresses flow into the same workspace, and Ticket0 auto-tags tickets by which address they came in on so you can filter, route, and report on them separately.

Common multi-alias setups

How it works

1. Verify each sending domain once, under Settings → Domains (see Custom Domain Configuration). Multiple addresses can share a verified domain — you don't re-verify per alias.
2. Register each alias under Settings → Aliases. An alias is {local-part}@{verified-domain} with an optional display name and auto-tags.
3. Forward each address from your existing mail provider to your workspace's single inbound address <workspace-slug>@inbox.ticket0.ai. Ticket0 reads the original To: header to match the alias.

All traffic arrives via one forwarding rule per mailbox. Ticket0 does the splitting based on the To: address.

Adding an alias

1. Go to Settings → Aliases → Add alias
2. Pick a verified domain
3. Enter the local part (e.g. billing)
4. Set a display name (e.g. Billing Support) — used when Ticket0 sends replies from this alias
5. Optionally add auto-tags (comma-separated, e.g. team:billing, type:payment) — every ticket arriving on this alias gets these tags automatically

Routing tickets to specific people

Auto-tags make it trivial to route by alias using Settings → Routing:

• If To contains billing@ → assign to Billing group
• If Tags contain team:billing → assign to a specific operator
• If Subject contains urgent → escalate

Configure rules in Settings → Routing → New rule.

Catch-all forwarding

If you want every address on a domain to hit Ticket0 without registering each one as an alias upfront, set up a catch-all forward in your mail provider (e.g. Google Workspace's default routing rule). Tickets arrive as normal; addresses that don't match a registered alias will show as-is without auto-tags.

Per-alias reporting

Filter the inbox by tag (e.g. team:billing) or by the To: address to break down volume, resolution time, and AI performance per alias.