Connecting Your Email Domain
Route support emails from your own domain into Ticket0.
Ticket0 handles inbound email by forwarding from your existing mailbox, and handles outbound email by sending from a verified domain you own. These are two independent pieces of the setup:
- Inbound (receiving tickets) — you keep using your existing email provider (Gmail, Outlook, Fastmail, etc.) and set up an auto-forward from
support@yourcompany.comto your workspace's Ticket0 inbound address. No MX record changes. - Outbound (sending replies) — add your domain to Ticket0 so replies go out from
support@yourcompany.comwith proper DKIM/SPF authentication instead of a generic Ticket0 sender.
You can do both, or just one. A minimal setup (forwarding only) is enough to start replying in Ticket0, but outbound replies will be sent from a ticket0.ai address until you connect a domain.
Inbound — forward to your Ticket0 address
1. Grab your workspace inbound address
- Go to Settings → Domains
- Your workspace's inbound address is shown as
<workspace-slug>@inbox.ticket0.ai— copy it
2. Set up forwarding in your email provider
In the provider where support@yourcompany.com is currently hosted, create an auto-forward rule that sends every incoming message to the address you copied.
Typical steps:
- Gmail — Settings → Forwarding and POP/IMAP → Add a forwarding address, then create a filter with
Matches: *→ Forward it to - Google Workspace (admin-level) — Admin console → Apps → Google Workspace → Gmail → Routing → Add a routing rule (preferred for shared support inboxes, avoids per-user confirmations)
- Outlook / Microsoft 365 — Settings → Mail → Forwarding, or an admin-created transport rule
- Fastmail / other IMAP providers — add a rule to Redirect (not Forward, which rewrites headers) the message
Prefer redirect / route over forward when your provider offers both. Forwarding rewrites the From: header, which can break reply threading and trip SPF. Redirect/route preserves the original sender headers.
3. Send a test email
Email support@yourcompany.com from any outside account. Within a few seconds the message should appear as a ticket in Ticket0.
Outbound — send replies from your domain
This step is optional but strongly recommended. Without it, replies go out from a ticket0.ai address; with it, replies go out from support@yourcompany.com with DKIM/SPF passing.
1. Add the domain in Ticket0
- Go to Settings → Domains → Add domain
- Enter your domain (e.g.
yourcompany.com) - Ticket0 shows the DNS records you need to add
2. Add the DNS records
Add the DKIM and SPF records shown in Ticket0 to your DNS provider. See SPF and DKIM verification for details and troubleshooting.
DNS typically propagates in 5–30 minutes. The domain shows as Verified in Ticket0 once the records are live.
3. Pick the From address
Once verified, Ticket0 sends outbound replies from the address shown under your domain (e.g. support@yourcompany.com). You can set a different local part if you prefer.
Forwarding adds a small amount of latency (typically a few seconds). It also means your existing email provider is in the path — if you ever migrate off them, update the forwarding rule at the new provider too.
Multi-alias setup
A single workspace can receive from multiple addresses — one per product, region, or team. Forward each address to the same Ticket0 inbound address; use Settings → Aliases to route tickets based on the recipient. See Multi-alias email.