Forwarding Setup

Ticket0 receives inbound email by forwarding. You keep using your existing email provider (Gmail, Outlook, Fastmail, etc.) and auto-forward support@yourcompany.com to your workspace's Ticket0 inbound address. No MX record changes, no extra mail server to maintain.

Get your Ticket0 forwarding address

Go to Settings → Domains in your Ticket0 workspace
Your inbound address is shown as <workspace-slug>@inbox.ticket0.ai — copy it

You don't need to have a custom domain connected to see this address; every workspace gets one by default.

Set up forwarding in Gmail

Open Gmail → Settings (gear) → See all settings → Forwarding and POP/IMAP
Click Add a forwarding address and paste your @inbox.ticket0.ai address
Gmail sends a confirmation email — it arrives in Ticket0 as a ticket with a confirmation link. Click the link.
Back in Gmail, choose Forward a copy of incoming mail to and set the rule to keep Gmail's copy in the Inbox (so you don't lose history on the Gmail side)

For shared mailboxes, prefer the admin-level Google Workspace routing rule over per-user forwarding — see below.

Set up forwarding in Google Workspace (admin)

Recommended for team support@ addresses:

Admin console → Apps → Google Workspace → Gmail → Routing
Add routing rule → match envelope recipient support@yourcompany.com
Also deliver to → add your @inbox.ticket0.ai address
Save and wait a few minutes for the rule to propagate

This avoids the per-user confirmation dance and survives user offboarding.

Set up forwarding in Outlook / Microsoft 365

Outlook Web → Settings (gear) → Mail → Forwarding
Enable Start forwarding and paste your @inbox.ticket0.ai address
Tick Keep a copy of forwarded messages

For shared mailboxes, configure a transport rule in Exchange admin instead.

Other providers

Most providers offer forwarding under Settings → Filters, Rules, or Mail forwarding. Enter your @inbox.ticket0.ai address as the destination.

Prefer redirect over forward if your provider offers both. Forwarding rewrites the From: header (which can trip SPF and break reply threading); redirect preserves original sender headers.

Testing

Send an email to support@yourcompany.com from an outside account. Within a few seconds it should appear as a ticket in Ticket0. If nothing arrives:

Confirm the forwarding rule is active in your provider
Send a test directly to the @inbox.ticket0.ai address — if that works, the issue is on the forwarding side
Check your provider's forwarding activity log for bounces

Notes on latency and authentication

Forwarding adds a few seconds of latency compared to native inbound. Some providers also re-sign the forwarded message, which can cause SPF mismatches on the customer's original message — this doesn't affect Ticket0's ability to process the ticket, but if you rely on SPF/DKIM for spam scoring in your own provider, inspect what it's doing to the message headers.