> For the complete documentation index, see [llms.txt](https://support.suptask.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.suptask.com/integrations-automations-and-workflows/email-ticketing-setup/custom-email-domain.md). # Custom Email Domain Send ticket emails from your own domain instead of the Suptask domain By default, emails that Suptask sends to your requesters are delivered from the Suptask sending domain, `support@suptask-mail.com`, using your organization name as the sender name. With a Custom Email Domain, those emails are instead sent from an address on your own domain, for example `support@acme-inc.com`. Your requesters see only your brand in their inbox, with no reference to Suptask in the sender address. Setting up a custom domain is a **semi-automatic process**. You share your desired sending address with Suptask Support, we generate the DNS records for your domain, and your domain administrator adds them to your DNS. Suptask then verifies the records and activates the domain on your Inbox. *** ### What changes with a custom domain A custom domain affects **outgoing** emails only. Incoming emails continue to reach Suptask through the email forwarding you already have in place. | | Default setup | Custom Email Domain | | --------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | Incoming emails | Your choice of email (e.g `support@acme-inc.com`), forwarded to `incoming@suptask-mail.com` | Your choice of email (e.g `support@acme-inc.com`), forwarded to `incoming@suptask-mail.com` | | Sender address on outgoing emails | `support@suptask-mail.com` | Your own address, e.g. `support@acme-inc.com` | | Sender name | Your organization name, e.g. **Acme Inc** | Your organization name, e.g. **Acme Inc** | | Reply-to address | Suptask domain | Your own domain | | DNS configuration | Not required | Required | | Setup | Self-service in the Inbox | Together with Suptask Support | {% hint style="info" %} If you have not yet set up the Email integration, start with Email-to-Slack Ticketing. The custom domain is added on top of a working email setup. {% endhint %} *** ### Before you begin * The Email integration is enabled and working on your Inbox * You have decided which address emails should be sent from, for example `support@acme-inc.com` * You have access to the DNS settings for that domain, or you can work with the person who does * You have contacted [Suptask Support](/getting-started/contact-support.md) to request the custom domain *** ### Step 1: Request your custom domain Contact Suptask Support and share the following: 1. **The sending address** you want to use, for example `support@acme-inc.com` 2. **The sender name** that should be displayed to your requesters, for example **Acme Inc** 3. **The Inbox** the custom domain should apply to 4. **A contact person** who manages your DNS, so that the records can be delivered to the right person Suptask Support will confirm your request and generate a set of DNS records that are unique to your domain. *** ### Step 2: Add the DNS records | Record | Type | Purpose | | --------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------ | | **DKIM** (3 records) | CNAME | Signs your outgoing emails so that receiving mail servers can verify they genuinely come from your domain | | **Return-Path** (2 records) | MX + TXT | Points the bounce address to a `bounce` subdomain on your domain. This aligns SPF with your domain and improves deliverability | #### Example records The records you receive will look like this, with values unique to your domain. In this example the sending domain is `acme-inc.com`. **DKIM** | Host | Type | Value | | ---------------------------------------------------------- | ----- | ----------------------------------------------------- | | `d5u1iqeu7fq2m2y3ofr3t6khw4nm6ln2._domainkey.acme-inc.com` | CNAME | `5u1iqeu7fq2m2y3ofr3t6khw4nm6ln2.dkim.amazonses.com` | | `hrtnnzyyt7kis53ezefwlkf2fgaz4q7f._domainkey.acme-inc.com` | CNAME | hrtnnzyyt7kis53ezefwlkf2fgaz4q7f`.dkim.amazonses.com` | | `kqzytjalcjhywmz43vsx3tytdh2ertyx._domainkey.acme-inc.com` | CNAME | `kqzytjalcjhywmz43vsx3tytdh2ertyx.dkim.amazonses.com` | **Return-Path** | Host | Type | Value | | --------------------- | ---- | ------------------------------------------ | | `bounce.acme-inc.com` | MX | `10 feedback-smtp.eu-west-1.amazonses.com` | | `bounce.acme-inc.com` | TXT | `"v=spf1 include:amazonses.com ~all"` | {% hint style="info" %} Do I need to change my SPF record?\ No. The SPF record is added on the `bounce` subdomain, not on your main domain, so your existing SPF record stays as it is. Suptask Support will tell you if your setup is an exception. {% endhint %} {% hint style="warning" %} Add the records exactly as they are provided, without modifying the host or the value. A single missing character will cause verification to fail. {% endhint %} Two things to look out for, depending on your DNS provider: * **Cloudflare:** set the records to **DNS only**. A proxied record will not verify. * **GoDaddy, Namecheap and similar:** some providers automatically append your domain name to the host or the value of a record. If a hostname ends up duplicated, enter only the part before your domain in the host field, or add a trailing dot to the value. DNS changes are not immediate. Most providers publish the records within a few minutes, but it can take up to 24–48 hours before they are visible everywhere. *** ### Step 3: Verification and activation When the records are in place, let Suptask Support know. 1. Suptask verifies that all records resolve correctly on your domain 2. Suptask activates the custom domain on the Inbox you selected 3. You send a test email to your support address and confirm that a ticket is created 4. You reply on the ticket in Slack and confirm that the reply arrives from your own domain If verification fails, Suptask Support will tell you which record is missing or incorrect so you can adjust it. {% hint style="info" %} A custom domain is activated per Inbox. If you have several Inboxes that should send from your own domain, tell Suptask Support which ones during Step 1. {% endhint %} *** ### Incoming emails still use forwarding A custom domain does not change how emails reach Suptask. Emails sent to your address must still be forwarded to `incoming@suptask-mail.com`. If you have not set up forwarding yet, follow the guide for your provider: * [Gmail / Google Workspace](/integrations-automations-and-workflows/email-ticketing-setup/how-to-configure-the-email-integration-for-gmail-and-google-workspaces.md) * [Microsoft Outlook](/integrations-automations-and-workflows/email-ticketing-setup/microsoft-outlook.md) *** ### Email security and deliverability {% hint style="success" %} Suptask supports the most recent email security standards to ensure email deliveries. This includes DMARC, DKIM and SPF. {% endhint %} When your domain is fully authenticated, your requesters get a cleaner and more trustworthy experience: * No **via** tag in Gmail and no **on behalf of** indicator in Outlook * Emails align with your existing DMARC policy through both DKIM and the Return-Path * Better deliverability, since messages are signed by your own domain reputation #### DMARC DMARC is not required for the custom domain to work, but we recommend having a policy on your domain. Most receiving mail servers expect it, and it protects your domain against spoofing. A domain can only have one DMARC record. If `_dmarc` already exists on your domain, leave it as it is. Your current policy will apply to emails sent by Suptask, since they are signed and aligned with your domain. If you do not have a DMARC record yet, this is a safe starting point. It monitors without blocking anything and sends reports to an address you control: | Host | Type | Value | | --------------------- | ---- | --------------------------------------------------- | | `_dmarc.acme-inc.com` | TXT | `"v=DMARC1; p=none; rua=mailto:dmarc@acme-inc.com"` | Once your emails are consistently passing, you can tighten the policy to `quarantine` or `reject` on your own schedule. *** ### Troubleshooting **Verification keeps failing**\ Confirm that the records were added to the correct domain, that all three DKIM records are present, that both records exist on the `bounce` subdomain, that Cloudflare proxying is turned off, and that your DNS provider has not appended the domain name to a host or value. A duplicated hostname is the most common cause. **Emails still arrive from the Suptask domain**\ The custom domain is activated per Inbox. If emails from a specific Inbox still come from `support@suptask-mail.com` after activation, contact Suptask Support so we can verify the configuration on that Inbox. **Emails land in spam**\ Check that your SPF record has not exceeded the DNS lookup limit, and that your DMARC policy is not stricter than your current setup allows. Suptask Support can help you review the records. *** ### Need help? Contact [Suptask Support](https://claude.ai/getting-started/contact-support.md) if you have any questions about setting up a custom email domain. {% content-ref url="/pages/5WZ9TNX8pOX8HqAuhORE" %} [Email-to-Slack Ticketing](/integrations-automations-and-workflows/email-ticketing-setup/email-to-slack-ticketing.md) {% endcontent-ref %} {% content-ref url="/pages/Kjf5hQAdmX9PhcPXYM9X" %} [Email Customization](/integrations-automations-and-workflows/email-ticketing-setup/email-customization.md) {% endcontent-ref %}