Custom Email Domains

Why Use a Custom Domain?

With a custom domain, your emails come from your own address (like [email protected]) instead of a shared @yaplet.io address. This matters for three key reasons:

Brand Trust

Customers recognize and trust emails from your own domain. A @yaplet.io address may look unfamiliar and get ignored.

Better Deliverability

Custom domains build their own sending reputation. With proper warmup, your emails are far more likely to reach inboxes instead of spam folders.

Newsletter Access

Newsletter campaigns require a verified custom domain. This is not optional — Yaplet enforces it to protect deliverability for all users.

You cannot send newsletter campaigns from a @yaplet.io email address. When you try to create a newsletter campaign, Yaplet checks for a verified custom domain email. If none exists, the campaign cannot be created and you'll be prompted to add a custom domain first.

Full Setup Guide

Setting up a custom domain involves adding the domain in Yaplet, configuring DNS records with your domain registrar, and verifying everything works. This process typically takes 15–30 minutes of active work, plus up to 48 hours for DNS propagation (usually much faster).

Add Your Domain in Yaplet

Navigate to Settings > Emailing > Domains tab
Click the Add Domain button
Enter your domain name — for example, yourcompany.com (just the domain, no https:// or www.)
Toggle Need warmup to ON (strongly recommended for new domains — see the warmup section below)
Click Add

Yaplet creates the domain and generates all the DNS records you need. The domain will show as unverified until you complete the next steps.

Copy Your DNS Records

After adding the domain, Yaplet displays a DNS records table. This table contains all the records you need to add to your domain's DNS settings. Each row shows the record Type, Name, Value, and (for MX records) a Priority.

Use the copy button next to each record name and value to avoid typos. DNS records must be exact — even a small mistake will cause verification to fail.

You will need to add the following records. All of them are required for full functionality:

DKIM Records (3 CNAME records)

DKIM (DomainKeys Identified Mail) signs your outgoing emails so receiving servers can verify they actually came from your domain. Yaplet generates three DKIM tokens, each requiring its own CNAME record.

Type	Name	Value
CNAME	`{token1}._domainkey.yourcompany.com`	`{token1}.dkim.amazonses.com`
CNAME	`{token2}._domainkey.yourcompany.com`	`{token2}.dkim.amazonses.com`
CNAME	`{token3}._domainkey.yourcompany.com`	`{token3}.dkim.amazonses.com`

The actual token values are unique to your domain and shown in your dashboard.

DMARC Record (1 TXT record)

DMARC tells receiving servers what to do with emails that fail authentication checks. This is required by most email providers.

Type	Name	Value
TXT	`_dmarc.yourcompany.com`	`v=DMARC1; p=none`

MX Record for Receiving (1 MX record)

This record tells the internet to deliver emails sent to your domain to Yaplet's servers. Without it, incoming emails to your custom addresses won't reach your inbox.

Type	Name	Value	Priority
MX	`yourcompany.com`	`inbound-smtp.eu-central-1.amazonaws.com`	10

If your domain already has MX records (e.g., for Google Workspace or Microsoft 365), adding this record will also route email to Yaplet. Make sure you understand the implications — you may want to use a subdomain like mail.yourcompany.com instead if you don't want to affect your existing email setup.

SPF Record (1 TXT record)

SPF (Sender Policy Framework) tells receiving servers which mail servers are authorized to send email on behalf of your domain.

Type	Name	Value
TXT	`yourcompany.com`	`v=spf1 include:amazonses.com ~all`

If your domain already has an SPF record, do not create a second one. Instead, add include:amazonses.com to your existing record. For example, if your current record is v=spf1 include:_spf.google.com ~all, change it to v=spf1 include:_spf.google.com include:amazonses.com ~all.

MAIL FROM Records (1 MX + 1 TXT record)

The MAIL FROM domain is a subdomain (mail.yourcompany.com) used as the technical sender address. This improves deliverability by aligning the envelope sender with your domain.

Type	Name	Value	Priority
MX	`mail.yourcompany.com`	`feedback-smtp.eu-central-1.amazonses.com`	10
TXT	`mail.yourcompany.com`	`v=spf1 include:amazonses.com ~all`

Tracking Domain (1 CNAME record)

This record enables link click tracking in your emails. It points a subdomain to a CloudFront distribution that handles tracking redirects.

Type	Name	Value
CNAME	`link.yourcompany.com`	(CloudFront domain shown in your dashboard)

Certificate Validation (1 CNAME record)

This record validates the SSL certificate for your tracking domain. The exact name and value are generated by AWS Certificate Manager and shown in your dashboard.

Type	Name	Value
CNAME	(shown in your dashboard)	(shown in your dashboard)

CAA Record (if one already exists on your domain)

CAA (Certification Authority Authorization) records control which certificate authorities are allowed to issue SSL certificates for your domain. If your domain already has a CAA record, you must add amazon.com as an allowed issuer — otherwise AWS Certificate Manager cannot issue the SSL certificate needed for your tracking (link.) subdomain, and that part of the setup will fail.

Check your DNS for an existing CAA record before verifying. If one exists and doesn't include amazon.com, add the following entry:

Type	Name	Value
CAA	`yourcompany.com`	`0 issue "amazon.com"`

If your domain has no CAA record at all, you don't need to add one — CAA records are optional and only restrict issuance when they're present.

Add Records to Your DNS Provider

Log in to your domain registrar or DNS provider and add all the records listed above. Here are quick instructions for the most common providers:

Go to your domain's DNS settings in the Cloudflare dashboard
Click Add record for each record
Set the Type, Name, and Content (Value) from your Yaplet dashboard
For CNAME records: set Proxy status to DNS only (grey cloud icon). Proxied CNAME records will break DKIM and certificate validation
Save each record

Go to Domain List > Manage > Advanced DNS
Click Add New Record for each entry
Select the type and enter the host and value
For CNAME records, Namecheap automatically appends your domain — enter only the subdomain part (e.g., _dmarc instead of _dmarc.yourcompany.com)
Save all changes

Wait for DNS Propagation

DNS changes take time to propagate across the internet. This can take anywhere from a few minutes to 48 hours, though most records propagate within 1–2 hours.

Verify Your Domain

Once you believe the records have propagated:

Go back to Settings > Emailing > Domains
Select your domain from the dropdown
Click the Verify DNS button

Yaplet checks each record against your DNS. If everything is correct, your domain status changes to Verified (green badge). If verification fails, double-check your records — the most common issues are:

Typos in record values (use the copy button)
CNAME records being proxied through Cloudflare (must be DNS-only)
SPF record conflicts (multiple TXT records instead of merging)
DNS hasn't fully propagated yet (wait and try again)

Adding Email Addresses to Your Domain

Once your domain is verified, you can create email addresses on it:

Click "Add email" in the domain's emails section

Enter the email prefix

For example, entering newsletter creates [email protected]. The same prefix rules apply as with yaplet.io emails (3–30 characters, lowercase, starts and ends with a letter or number).

Select a widget

Choose which widget this email should be associated with. Incoming emails to this address will route to that widget's inbox.

Click "Add"

The email is created and ready to use immediately for inbox conversations. For newsletter campaigns, this email will now appear as a sender option when creating campaigns.

Incoming Emails and Threading

Custom domain emails work the same way as yaplet.io emails when it comes to receiving and threading:

Incoming emails to your custom domain addresses (e.g., [email protected]) create new chats in the inbox, assigned to the widget linked to that email address. The sender becomes a visitor.
Email threading is automatic — every outgoing email includes a unique Reply-To address. When customers reply, responses route back to the same conversation.
Email-source chats (started from an incoming email) auto-send agent messages as email. The chat header shows an "Email" badge.
Related email chats are accessible from the sidebar, showing all conversations with the same email in the same widget.

The email behavior is identical for yaplet.io and custom domain emails. The difference is only in branding, deliverability, and newsletter access — not in how conversations work.

Email Warmup System

Email warmup is the process of gradually increasing your sending volume over time to build a positive reputation with email providers (Gmail, Outlook, Yahoo, etc.). New domains have no sending history, so ISPs are suspicious of sudden high-volume sends.

Why Warmup Matters

Sending hundreds of emails from a brand-new domain on day one is a sure way to land in spam folders — or get your domain blacklisted entirely. Warmup prevents this by slowly building trust.

When you enable warmup, Yaplet automatically controls your daily sending limit:

New domains start with a conservative daily limit
The system looks at your last 7 days of sending activity to calculate the next day's limit
Active sending gradually increases your limit over time
Inactive periods decrease the limit to prevent sudden spikes after a pause
Limits recalculate automatically at midnight UTC each day

Warmup Settings

You can view and adjust warmup parameters for your domain:

Setting	Description
Today's sending limit	Maximum number of emails you can send today (shown with UTC time range)
Interval between emails	Calculated automatically — the minimum delay between consecutive sends
Max limit	The ceiling your daily limit will never exceed
Min limit	The floor your daily limit will never drop below
Change factor	How aggressively the limit adjusts day-to-day (percentage)

You can manually override today's sending limit by clicking Edit sending limit. Manual overrides only last until midnight UTC — after that, the system recalculates automatically based on your sending history.

Disabling Warmup

If you use an external warmup service (like Lemwarm, Warmup Inbox, or similar), you can disable Yaplet's built-in warmup. When warmup is disabled:

Emails send immediately with no rate limiting from Yaplet's side
You are fully responsible for managing sending volume and reputation
Amazon SES account-level limits still apply

Disabling warmup without an alternative warmup strategy is risky. Emails from a cold domain sent in bulk are very likely to be marked as spam. Only disable this if you know what you're doing or have an external warmup service in place.

Sending Logs

Click the Logs button on your domain to see email send statistics for the last 7 days. The logs show a breakdown by email type:

Type	Description
Campaign	Emails sent from newsletter campaigns
Workflow	Emails sent by automation workflows
Other	Inbox replies, notifications, and other transactional emails

This helps you monitor your sending volume and track whether you're approaching your warmup limits.

Managing Domains

Switching Between Domains

If you have multiple verified domains, use the domain dropdown at the top of the Domains tab to switch between them. Each domain has its own DNS records, verification status, warmup settings, and email addresses.

Deleting a Domain

Click Delete domain to remove a domain and all its associated email addresses. This action is permanent and cannot be undone. Any emails currently in-flight or scheduled for delivery from this domain will fail.

Before deleting a domain, make sure no active newsletter campaigns or automation workflows are using email addresses on this domain. Deleting a domain with active campaigns will cause those campaigns to fail.

Quick Reference: Yaplet.io vs. Custom Domain

To recap when you should use each type:

Use yaplet.io emails when:

You want to start handling email immediately with zero setup
You only need inbox conversations (receiving and replying)
Branding is not a priority

Use custom domain emails when:

You want emails to come from @yourcompany.com
You plan to send newsletter campaigns (custom domain is required)
You want to build your own sender reputation for better deliverability
You need email warmup controls for high-volume sending

Newsletter reminder: You can only create newsletter campaigns with a verified custom domain email. The campaign creation page will block you if you only have yaplet.io emails. Set up and verify a custom domain before planning your first newsletter.