> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.crisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to setup a Custom SMTP with Amazon SES to improve email deliverability

*Learn how to connect Amazon SES as a custom SMTP provider for emails sent from Crisp.*

A custom SMTP routes outbound Crisp emails through your own email delivery provider instead of Crisp's default sending infrastructure. This guide focuses on Amazon SES, but the same idea applies to any provider that supports standard SMTP credentials.

|| Custom SMTP is available on **Crisp Essentials** and **Crisp Plus** plans. You also need an active **Custom Email Domain** before connecting the SMTP in Crisp.

__In this guide:__
* [Before you start](#1-before-you-start) → requirements, provider notes, and Amazon SES pricing caution
* [Create and verify an Amazon SES domain identity](#1-create-and-verify-an-amazon-ses-domain-identity) → verify your sending domain and test SES
* [Create SMTP credentials and connect Crisp](#1-create-smtp-credentials-and-connect-crisp) → generate SES credentials and add them in Crisp
* [After setup](#1-after-setup) → understand what the SMTP affects and what to monitor
* [Frequently Asked Questions](#1-frequently-asked-questions) → common Amazon SES and Crisp SMTP questions

---

# ${color}[#0080dd](Before you start)

Amazon SES is an email delivery service that can send and receive emails using your own domains and email addresses. SMTP is the protocol Crisp uses to hand outbound emails to Amazon SES so SES can deliver them to recipients.

A custom SMTP affects outbound emails sent from Crisp, including Inbox email replies, transcripts, automated Campaigns, and one-shot Campaigns.

||| Amazon SES pricing and free-tier conditions can change. Check the official [Amazon SES pricing page](https://aws.amazon.com/ses/pricing/) before relying on any cost estimate.

#### ${color}[#445055](Requirements)

__Before following this guide, make sure you have:__
* **Owner access in Crisp** → members may not be allowed to configure email delivery settings
* **A Custom Email Domain in Crisp** → configure it first using [this guide](https://help.crisp.chat/en/article/how-can-i-setup-a-custom-email-domain-ndklh7/)
* **Access to your domain DNS records** → for example through Cloudflare, OVH, GoDaddy, Namecheap, or your registrar
* **An AWS account** → with the permissions needed to manage Amazon SES identities and SMTP credentials
* **Amazon SES production access** → required before real email delivery can work properly outside the SES sandbox

#### ${color}[#445055](Important note about other SMTP providers)

Crisp can work with custom SMTP providers, but this article only documents the Amazon SES flow.

Providers such as Microsoft or Outlook may require additional authentication methods, OAuth flows, app passwords, or multi-factor authentication rules. If your provider cannot connect with standard SMTP server, port, username, and password details, use another provider that supports standard SMTP credentials compatible with Crisp.

---

# ${color}[#0080dd](Create and verify an Amazon SES domain identity)

The first step is to create and verify an Amazon SES identity for the subdomain you use to send emails from Crisp.

#### ${color}[#445055](Create the domain identity)

1. Log in to the [Amazon AWS console](https://console.aws.amazon.com).
2. Open **Services → Business Applications → Amazon Simple Email Service**. You can also search for **SES**.
3. Go to **Configuration → Verified Identities**.
4. Click **Create Identity**.
5. Select **Domain** as the identity type.
6. Enter the sending subdomain used for Crisp, such as `emails.mydomain.com`.
7. Click **Create**.

![Create an Amazon SES domain identity](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss1hxd4em_zb0qjs.png =1000xauto)

#### ${color}[#445055](Configure a Custom MAIL FROM domain)

After the identity is created, open the **Custom MAIL FROM domain** section and click **Edit**. Enter a deeper subdomain, for example `ses.emails.mydomain.com` if Crisp sends from `emails.mydomain.com`.

![Configure Custom MAIL FROM in Amazon SES](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss2xq2o8l_6hc8rm.png =1000xauto)

__A Custom MAIL FROM domain can help you:__
* **Improve deliverability alignment** → SES sends with a domain that belongs to your setup
* **Keep a consistent domain identity** → recipients and inbox providers see your domain chain
* **Handle bounces and complaints cleanly** → SES can process feedback for that sending setup

#### ${color}[#445055](Add the DNS records)

Amazon SES will show DNS records to add for your domain identity and Custom MAIL FROM domain. These usually include DKIM records for the sending domain, plus MX and TXT records for the MAIL FROM subdomain.

![Amazon SES DKIM verification records](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss3x9npu6_b2o0n6.png =1000xauto)

Add the records in your DNS provider. This example uses Cloudflare, but the same principle applies to your own DNS manager.

![Amazon SES DNS records added in Cloudflare](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss41aar35b_hx199m.png =1000xauto)

|| If you use Cloudflare, disable the proxy for these records. The cloud icon must be grey, not orange.

DNS propagation can take time, and Amazon SES checks records periodically rather than on demand. It is normal for verification to take several hours, and sometimes more than 24 hours.

![Amazon SES domain identity verified](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss51qydirj_n2qk5w.png =1000xauto)

|| The Custom MAIL FROM domain is optional in Amazon SES. You can continue the setup while it is still pending, but the domain identity itself must be verified before real sending works reliably.

#### ${color}[#445055](Send a test email from Amazon SES)

While your SES account is still in sandbox mode, Amazon only lets you send emails to verified recipients. To test delivery:

1. Go back to **Configuration → Verified Identities**.
2. Click **Create Identity**.
3. Select **Email address**.
4. Enter a personal email address you can access.
5. Click the verification link sent by Amazon SES.
6. Return to your domain identity and click **Send test email**.
7. Choose a **Custom** scenario and send the test to your verified recipient.

![Send a test email from Amazon SES](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss6cl3in2_n1ogy1.png =1000xauto)

If the test does not arrive, check that the domain identity is verified, the recipient email address is verified, and the DNS records are correct. For provider-specific issues, use the [Amazon SES troubleshooting documentation](https://docs.aws.amazon.com/ses/latest/dg/troubleshoot.html).

#### ${color}[#445055](Request production access)

New Amazon SES accounts start in sandbox mode. In sandbox mode, sending is restricted to verified recipients and quotas are limited. Before connecting SES to Crisp for real customer emails, request production access from Amazon SES.

![Request Amazon SES production access](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss7q1i4we_c10g65.png =1000xauto)

||| Do not route Crisp emails through Amazon SES sandbox for production use. If SES production access is not active, your customer emails may not be delivered correctly.

---

# ${color}[#0080dd](Create SMTP credentials and connect Crisp)

Once Amazon SES is verified and production access is approved, create SMTP credentials and add them to Crisp.

#### ${color}[#445055](Generate SMTP credentials in Amazon SES)

1. In the AWS console, open **Services → Business Applications → Amazon Simple Email Service**.
2. Go to **SMTP Settings**.
3. Click **Create SMTP Credentials**.
4. Choose a username or keep the default one.
5. Create, copy, download, and securely store the SMTP credentials.

![Create Amazon SES SMTP credentials](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss81crz9h2_1ewfl1r.png =1000xauto)

||| Store the SMTP credentials securely. If you lose them, you will need to create new credentials.

#### ${color}[#445055](Add SMTP credentials in Crisp)

Go to [**app.crisp.chat**](https://app.crisp.chat), then open **Settings → Email Settings → Email Delivery → Custom Email SMTP**.

Enter the SMTP server, port, username, and password from Amazon SES, then click **Verify SMTP Credentials**.

![Configure Amazon SES SMTP in Crisp](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/cleanshot-2025-02-27-at-120715_zh59nn.png =1000xauto)

#### ${color}[#445055](Test from Crisp)

After the SMTP credentials are verified, create a new email conversation in Crisp and send a test message to an email address you control.

![Send a test email from the Crisp Inbox](https://storage.crisp.chat/users/helpdesk/website/87ae2703583ac800/ss109dkmqm_xro3lw.png =1000xauto)

Open the received email and inspect the headers if you want to confirm that Amazon SES and your Custom MAIL FROM domain were used.

---

# ${color}[#0080dd](After setup)

Your Amazon SES SMTP is now connected to Crisp. From this point, outbound emails sent from Crisp are routed through SES.

#### ${color}[#445055](What the SMTP affects)

The custom SMTP handles outbound emails emitted from Crisp, including:

* **Inbox emails** → email replies sent from Crisp conversations
* **Conversation transcripts** → transcripts sent by email
* **Automated Campaigns** → event-triggered Campaign emails
* **One-shot Campaigns** → Campaigns sent to selected recipients

Campaign recipient limits do not automatically change just because you connected Amazon SES. To understand recipient limits, see [What are Email Campaigns recipient limits?](https://help.crisp.chat/en/article/what-are-email-campaigns-recipient-limits-cmvcqw/)

#### ${color}[#445055](Useful Amazon SES features)

Amazon SES provides additional tools that can help you monitor and improve email delivery.

__Features worth reviewing include:__
* **Virtual Deliverability Manager** → delivery insights and reputation recommendations
* **Configuration Sets** → sending metrics for deliveries, bounces, clicks, and opens
* **Sending Limits** → quota and rate controls for higher sending volumes

You can learn more in the [Amazon SES documentation](https://docs.aws.amazon.com/ses/index.html).

---

# ${color}[#0080dd](Frequently Asked Questions)

*Still have questions which were not covered in this article? Here is a collection of the most frequently asked questions on this topic.*

###### ${color}[#F08820](Why is my Amazon SES domain identity still pending?)

Domain verification can take up to 48 hours in some cases. Double-check every DKIM record, confirm they were added to the correct DNS zone, and disable any DNS proxying that could hide the records. If the identity remains pending, contact AWS support or your DNS provider.

###### ${color}[#F08820](Why is my Domain Identity verified, but not my Custom MAIL FROM domain?)

Most Custom MAIL FROM issues come from incorrect DNS records, missing records, conflicting MX records, or DNS propagation delays. Review the MX and TXT records shown in Amazon SES and confirm they match exactly in your DNS provider.

###### ${color}[#F08820](Does the custom SMTP only route Campaigns?)

No. The custom SMTP routes all outbound emails sent from Crisp, including Inbox email replies, conversation transcripts, automated Campaigns, and one-shot Campaigns.

###### ${color}[#F08820](Can Crisp support fix my Amazon SES DNS records?)

Crisp support can help you understand where to configure the SMTP in Crisp, but Amazon SES verification and DNS hosting issues must be handled from AWS and your DNS provider.

###### ${color}[#F08820](Can I use other SMTP providers?)

Yes! Crisp supports all SMTP providers, and there are many options to choose from depending on your needs and budget. To name a few: Sendgrid, Elasticmail, Resend, Brevo...

Note that you must use a Transactional SMTP service. "Exchange" SMTP providers (such as OVH, Gmail or Outlook) are not supported. Exchange SMTP are designed to connect specific mailboxes to an email client, not handle email sending for a whole authorized domain identity.