# Set up a custom reply address

{% hint style="warning" %}

### Before you start

You will need access to your organisation's **DNS settings**. This is usually managed by your IT department or the person responsible for your domain. You do not need to do the technical part yourself, but you will need to loop them in.
{% endhint %}

By default, emails sent from the platform come from the generic platform address `noreply@letsgetdigital.com`. If you want emails to show **your organisation's email address** instead — for example, `events@yourorganisation.nl` — you need to verify your domain first.

This page walks you through how to do that.

{% stepper %}
{% step %}

### Step 1 — Enter your reply address

In the platform, go to your email settings and enter the email address you want to use as the reply address. Once you do, the platform will show a notice that your domain is not yet verified, along with three DNS records that need to be added.
{% endstep %}

{% step %}

### Step 2 — Share the DNS records with your IT contact

The platform will display three **CNAME records** — each with a Host and a Value. These need to be added to your domain's DNS settings by whoever manages your domain.

The records look something like this:

<div data-with-frame="true"><figure><img src="/files/VMaeJKbGxE03k4YdsZLa" alt=""><figcaption><p>Custom domain is set with 3 CNAME records that have not yet been verified</p></figcaption></figure></div>

Send these values to your IT contact and ask them to add all three to the DNS settings of your domain.

{% hint style="info" %}

#### **Why CNAME records?**

These records point to our mail processor (SendGrid), which handles the email authentication on our behalf. For this method, adding SPF records to your DNS is not required. This is what allows mail services like Outlook and Gmail to trust that emails are genuinely coming from your organisation — and not treat them as spam.
{% endhint %}
{% endstep %}

{% step %}

### Step 3 — Confirm and wait

Once your IT contact has added the records, go back to the platform and click **"I have added these records"**. The platform will then check whether the records are in place. Records that are validated will turn **green**.

DNS changes can take up to **24 hours** to take effect globally, so if verification does not succeed immediately, try again after a few hours.

{% hint style="info" icon="circle-question" %}
**Records still aren't validated after 24 hours?** Please contact support at `support@letsgetdigital.com` or give us a call.&#x20;
{% endhint %}
{% endstep %}

{% step %}

### Step 4 — Verification complete&#x20;

<div data-with-frame="true"><figure><img src="/files/SDRxwKO6zAw6VqPxPIJH" alt=""><figcaption><p>Domain verification was successful and is now active. The table of CNAME records is no longer visible.</p></figcaption></figure></div>

Your domain is now authenticated. Emails sent through the platform will show your organisation's address, and participants will receive them in their inbox rather than their spam folder.

This is a one-time setup per domain so this step does not need to be repeated unless you explicitly change your domain again.&#x20;
{% endstep %}
{% endstepper %}


---

# Agent Instructions: 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://knowledge-base.letsgetdigital.com/the-admin-panel/settings/general-settings-app-+-vp-1/mail-settings-app-+-vp/set-up-a-custom-reply-address.md?ask=<question>
```

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.