Send from your own domain
Make replies come from support@yourcompany.com instead of an initdesk address. Verify your domain, forward your address, run the check, turn it on.
Make replies come from support@yourcompany.com instead of an initdesk address. Verify your domain, forward your address, run the check, turn it on.
Make replies come from support@yourcompany.com instead of an initdesk address. Verify your domain, forward your address, run the check, turn it on.
By default, replies from initdesk come from an initdesk address. Set up a company email address and new tickets in an inbox send replies from your own address, such as support@yourcompany.com. The setup is called Company email address. It has 2 parts: verify your domain once for your organization, then set up the address for each inbox.
This changes email about customer tickets only. Team invitations, sign-in codes, and billing emails keep their current sender.
This is separate from the custom domain for your help center, which changes the web address of the help center.
You do this once for each domain, and every inbox on that domain can use it.
yourcompany.com. Don't include http://, https://, or www..
The records come in 3 groups. Here is what each one does:
| Group | What it does |
|---|---|
| Authenticate sending | 3 DKIM records. DKIM is a signature on each email that proves it really came from your domain. |
| Handle bounces | Records on a subdomain that handle bounced mail. They include SPF, a list of the servers allowed to send for a domain. It sits on that subdomain, so you don't edit your main SPF record. |
| Protect the domain | A DMARC record. DMARC tells receiving servers what to do with mail that fails the other checks. It's marked Recommended and doesn't block verification. |
Some DNS providers add your domain to the end of a name for you. If a provider doesn't accept a name, try it without the final .yourcompany.com. If your domain already has a DMARC record, keep it. Any DMARC policy counts as found.
Each record shows Found, Missing, or Mismatch, and the page shows how many required records were found. DNS changes can take time to spread. While the domain is Pending, initdesk checks again about every 45 seconds as long as the page stays open. The domain is ready when you see Domain verified.
Verifying a domain doesn't change how any inbox sends mail.
The setup page has 4 steps.

support@yourcompany.com. It must be on the selected domain, or one of its subdomains.Saving doesn't turn on sending.
The page shows which address to forward to which. Create a forwarding rule at your email provider that sends your company address to the initdesk inbox address. Use Copy company address and Copy forwarding target to copy the two values. Keep the original sender and message headers intact.
Provider steps are in Forward from Google Workspace, Forward from Gmail, and Forward from Microsoft 365. If you already forward this address to the same inbox, the existing rule is enough. Keep one method so a message isn't forwarded twice.
If the check fails, the page explains why. See Fix email problems, then select Send again.
When the status says Ready to turn on, select Turn on for sending. The page then shows Company email address is live, and Current sender shows the address replies will use.
This applies to new tickets only. Existing tickets keep the sender they started with.
| Status on the Email page | What it means |
|---|---|
| Using initdesk address | No company address yet. Replies come from an initdesk address. |
| Setup in progress | You saved an address, but the domain or forwarding check isn't finished. |
| Ready to turn on | The address and the forwarding check are complete. |
| Live | New tickets send from your company address. |
| Needs attention | Something broke. Select Fix issue. |
Start with a new message. Replying to an older conversation shows the older sender.
You'll see "Complete the sending-domain and inbound checks before enabling." Verify the domain, save the address, and get Inbound connected. The button appears when everything is ready.
See Fix email problems.
Check that the status is Live, that you're testing a new ticket, and that the ticket is in the inbox you set up.