> For the complete documentation index, see [llms.txt](https://mava.gitbook.io/mava-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mava.gitbook.io/mava-docs/getting-started/integration-setup/email-setup/custom-email-domains.md). # Custom Email Domains ### Setting Up Email Replies from Your Custom Domain To enhance email deliverability and increase client trust, you can set up email replies to come from your custom domain (e.g., ) instead of . This feature is available to [Whale & Diamond](/mava-docs/price-plans.md) plan customers and allows your support team to maintain a professional and branded email communication experience. ## Why Set Up a Custom Domain for Email Replies? **• Improved Deliverability:** Emails sent from your own domain are less likely to be flagged as spam ensuring all replies are recieved by your end users. **• Increased Trust:** Clients are more likely to engage with and trust emails that come from your company’s domain rather than a third-party service like Mava. ### Prerequisites Before you begin, you must have correctly set up email forwarding. [Follow these instructions](/mava-docs/getting-started/integration-setup/email-setup/email-forwarding.md) to set up email forwarding first, if you've not already done this.
### Step-by-Step Setup Guide #### Step 1: Access the Email Integration Dashboard 1\. Navigate to the Mava dashboard by going to . #### Step 2: Enable the Custom Domain Toggle 1\. Once in the email integrations section, locate the “Custom Domain” option and toggle it on.
2\. In the background, we'll verify your domain via Amazon by sending you an email. You do not need to do anything with this email. #### Step 3: Add TXT Records to Your Domain 1\. From the table will be displayed with 2 TXT and 3 CNAME records. These records need to be copied and added to your domain’s DNS settings.
Note: your CNAME and @ TXT record will need ot match the exact values as shown in the dashboard.\ For DMARC we accept p=none, p=quarantine, and p=reject. 2\. Share these records with your system administrator, who will enter them into the DNS settings provided by your domain provider (e.g., GoDaddy, Google Domains, Cloudflare etc.). #### Step 4: Verify Domain Setup 1\. After the records are added, click the Check Status button in the Mava dashboard.
2\. Mava will verify if the records have been correctly added and the status should show as 'Verified'. This process can take a few minutes, depending on your domain provider.
#### Step 5: Test the Setup 1\. Once verification is successful, send a test email to your support email address and then reply from Mava to ensure that replies are being sent from your custom domain. ### Troubleshooting Tips • Confirm [email forwarding](/mava-docs/getting-started/integration-setup/email-setup/email-forwarding.md) is correctly set up and verified within Mava • Verification Failed?: Ensure the TXT records have been added correctly and wait up to 24 hours for the changes to propagate. • Emails Not Sending?: Double-check your DNS setup, ensuring that all records are entered exactly as provided. • If you've tried both steps above, you can try toggling off the custom domain section and toggling it back on. This will trigger a new verification email from Amazon. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://mava.gitbook.io/mava-docs/getting-started/integration-setup/email-setup/custom-email-domains.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.