Email Domain

Email Domain settings let you verify a custom domain for sending (and optionally receiving) outreach emails. Using your own domain instead of the default platform domain gives you a more professional appearance and better email deliverability.

Navigate to Settings > Email Domain in the sidebar.

Why use a custom domain?

	Platform domain	Custom domain
Address	you@outreach.aceinfluence.ai	you@mail.acme.com
Setup	Automatic	Requires DNS verification
Deliverability	Shared reputation	Your own reputation
Branding	Platform branded	Your brand
Warming	Not needed	Recommended

Setting up a custom domain

1. Go to Settings > Email Domain.
2. Enter your domain (e.g. mail.acme.com).
3. Click Setup Email Domain.
4. Add the DNS records shown to your DNS provider.
5. Click Check DNS to verify.

Use a subdomain

We strongly recommend using a subdomain like mail.acme.com or outreach.acme.com rather than your root domain acme.com. This:

• Isolates your outreach sending reputation from your regular business email
• Avoids conflicts with existing email services (Gmail, Outlook, etc.)
• Lets you remove or change the outreach domain without affecting company email

Each domain can only be used by one organization.

DNS Records

After setup, you'll see a table of DNS records to configure. Copy each record exactly using the copy buttons.

Record	Purpose	Required for
TXT (SPF)	Authorizes sending on behalf of your domain	Sending
CNAME (DKIM)	Email authentication signatures	Sending
MX	Routes inbound email to the platform	Receiving (optional)

DNS changes can take up to 48 hours to propagate, though most providers update within minutes.

Sending (Outbound)

Sending is automatically enabled when you set up a domain. Once the SPF and DKIM records are verified, you can send emails from addresses on this domain.

After verification, the platform automatically:

• Creates an API key for sending
• Enables domain warming
• Creates custom domain identities for all organization members

Receiving (Inbound)

Receiving is optional. It controls whether the platform can capture emails sent to your custom domain addresses (e.g. creator replies to john@mail.acme.com).

When do you need receiving?

• You have Google Workspace: You probably don't need receiving. Creator replies are captured via Gmail sync automatically.
• You don't have Google Workspace: You should enable receiving. Otherwise, replies to your custom domain addresses won't reach the platform, and features like Inbox and auto-offer detection won't work.

Enabling receiving

1. In Email Domain settings, click Enable Receiving.
2. An MX record will appear in the DNS records table.
3. Add the MX record to your DNS provider.
4. Click Check DNS to verify.

Domain Warming

New domains start with low sending limits that gradually increase over 8 days:

Day	Daily limit
1	50
2	100
3	200
4	400
5	700
6	1,000
7	1,500
8	2,000
9+	Your plan limit

Warming is automatically enabled on first verification. You can toggle it on/off in the domain settings. We recommend leaving it on for new domains to build sending reputation.

Changing your domain

To switch to a different domain, click the delete icon next to your current domain and confirm. This removes:

• The domain from Resend
• All DNS configuration and API keys
• Warming progress
• Custom domain identities for all org members

After removal, you can set up a new domain. Existing conversations using the old domain will not break (replies are threaded), but new outreach will need a different identity.

Related

• Email Identity -- Manage sending identities and default sender.
• Integrations -- Connect Google Workspace for Gmail sync.