# Email Address Customization

On advanced plans, you can customize the "From" email address used to send picture links to your guests. This allows you to maintain consistent branding and ensures that any replies from guests go directly to your inbox.

While this requires a one-time setup with your domain registrar or IT department, it provides a more professional experience for your participants.

{% hint style="warning" %}
**Public Domain Restriction** 

Public email domains (e.g., `@gmail.com`, `@icloud.com`, `@yahoo.com`) **do not** support this type of authorization. You must own a private domain (e.g., `@yourcompany.com`) to use this feature.
{% endhint %}

***

### Overview & Preparation

To use a custom sender address, you must authorize Simple Booth to send emails on your behalf. This is done by adding a [**Sender Policy Framework**](https://en.wikipedia.org/wiki/Sender_Policy_Framework) **(SPF)** record to your DNS settings.

* **Timeline:** DNS changes can take up to **24 hours** to propagate across the internet. Please plan your setup at least one day before your event.
* **Access:** You will need access to your domain registrar (e.g., GoDaddy, Google Domains, Namecheap) or the ability to submit a request to your IT department.

***

### Configuration Steps

{% stepper %}
{% step %}
Login to your domain registrar's dashboard and locate your **DNS Management** settings. You will need to add or edit a **TXT record** for your SPF.

**If you do not already have an SPF record:** Create a new TXT record and paste the following value: `v=spf1 a:mail.simplebooth.com ?all`
{% endstep %}

{% step %}
**Important:** A domain can only have **one** SPF record. Adding multiple SPF records will cause your emails to fail.

If you already have an SPF record, you must combine the rules into a single line.

* **Existing Google Record:** `v=spf1 mx include:_spf.google.com ~all`
* **Incorrect (Two Records):** `v=spf1 mx include:_spf.google.com ~all` `v=spf1 a:mail.simplebooth.com ?all`
* **Correct (Combined Record):** `v=spf1 mx include:_spf.google.com a:mail.simplebooth.com ~all`
  {% endstep %}

{% step %}
Once your DNS is configured:

1. Open the [Email Settings](/copy-of-halo-app/experience-designer/post-capture/send-and-print.md) within your preset in the Experience Designer.
2. Replace `no-reply@simplebooth.com` with your desired custom email address.
3. **Save** your changes.

If the DNS settings have synced correctly, you will see a success message. If they haven't processed yet, you will see a warning, and emails will default to `no-reply@simplebooth.com` until the setup is validated.
{% endstep %}
{% endstepper %}

***

### Troubleshooting

If your custom address is not validating after 24 hours, you can verify your SPF record using an external tool like **MXToolbox**:

1. Go to an SPF Record Lookup tool.
2. Enter your domain and click the lookup button.
3. Check the results for the following:
   * **Prefix:** `+`
   * **Type:** `a`
   * **Value:** `mail.simplebooth.com`
   * **SPF Multiple Records:** Ensure this shows that "less than two records" were found.

<figure><img src="/files/TQ2WX2eNkohhSaOcOZQC" alt="" width="375"><figcaption><p>SPF Lookup Help</p></figcaption></figure>

{% hint style="info" %}
**Working with IT Departments**&#x20;

If your organization has a dedicated IT department, they likely manage a complex SPF record. Instead of editing it yourself, send them a request to **whitelist `mail.simplebooth.com`** within your domain's SPF record.
{% endhint %}

***

{% hint style="success" %}

## Plan Availability

:white\_check\_mark: Pro, Select

:x: Lite, Core, Plus
{% endhint %}


---

# 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://docs.simplebooth.com/copy-of-halo-app/experience-designer/post-capture/send-and-print/email-customization/email-address-customization.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.