> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/communication-client/connecter-votre-domaine-pour-lenvoi-demails.md).

# Connect your domain for sending emails

By default, all emails sent by Yoplanning to your clients — confirmations, tickets, invoices, reminders — originate from **<info@yoplanning.com>**. By connecting your domain name, they will originate from **yourdomain.com**.

***

## Why connect your domain?

* **Your customers recognize the sender.** The displayed address is yours, not your software's.
* **You improve deliverability.** Emails are authenticated in the name of your domain: this is the most effective way to prevent emails from going to spam. See also [Email in spam and delivery problems](/en/faq/faq-generale/email-dans-le-spam-et-probleme-de-delivrance.md).
* \*\*You can track your emails one by one: received, opened, or never arrived — from both the History and the order list. No more unverifiable "I haven't received anything" messages.

{% hint style="info" %}
This feature is **pay-as-you-go**, billed per email sent. See [Pricing and Billing](#pricing-and-billing).
{% endhint %}

***

## Prerequisites

1. **A payment method must be configured** in your Yoplanning account (GoCardless, Stripe, etc.). Since this feature is billed on a pay-per-use basis, it cannot be activated without a billing method.
2. **A domain name that belongs to you**, and access to its **DNS configuration** (at your hosting provider or registrar: OVH, Gandi, Ionos, Google Domains, Cloudflare…).
3. **Knowing how to add a DNS record**, or having a service provider who will do it for you.

***

## Connect your domain

1. **Log in to Yoplanning.pro.**
2. Menu **Administration** → **Configuration** → **Team**.
3. Open the **three small dots** menu in the top right corner of the Team page, then **Edit**.
4. Scroll down to the bottom of the **“Emails”** section.
5. Click on **“Connect a domain”**.
6. Enter your **domain name**, then confirm.
7. The window will then display a **list of DNS records**. Copy them and add them to your domain's DNS zone with your hosting provider.
8. **Please wait.** The verification is automatic: activation usually occurs within **a few hours**, sometimes **24 to 48 hours**. You can also force a check by clicking the verification button in the window.
9. Once activated, the window indicates that your emails now leave from **<xxxx@yourdomain.com>**.

{% hint style="warning" %}
**Enter the domain name alone, without prefix or email address.**

* ✅ `example.com`
* ❌ `david@example.com`
* ❌ `www.example.com`
  {% endhint %}

{% hint style="info" %}
**Yoplanning does not provide support for your DNS zone.** Configuration screens differ from one hosting provider to another: if you are unsure where to paste the records, contact your hosting provider's or registrar's support team, who are familiar with their interface.
{% endhint %}

***

## Track sent emails

Connecting your domain doesn't just change the sending address: it gives you access to **email tracking**, in two places.

### History > "Emails" tab

Menu **History** → tab **“Emails”**. Here you will find the **list of all emails sent**, with for each its **receipt status** and its **read status**: email successfully delivered to the recipient's inbox, and email opened or not.

This is the first tool to open when a customer claims to have never received their confirmation or ticket: you can immediately distinguish an email that never arrived from an email that arrived but was never opened.

### Tracking icon in the order list

In the **command list**, an **icon** directly indicates the status of communication with the client:

* Has an email been **sent** regarding this order?
* Has he been **received**?
* Has it been **opened**?

The same monitoring applies to **payment links** sent to your customers: you can see if the link has arrived and if it has been opened, before sending a reminder.

{% hint style="info" %}
This tracking is **only available to teams that have connected a domain**. Without a connected domain, the **Emails** tab in the History and the order tracking icons will not appear.
{% endhint %}

### Les statuts possibles d'un email

Chaque email de l'Historique porte l'un des statuts suivants :

| Statut                 | Signification                                                                                                                                                                                                                                                                                |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **En cours d'envoi**   | L'email est en cours d'envoi de Yoplanning vers le fournisseur d'email.                                                                                                                                                                                                                      |
| **Envoyé**             | L'email a été envoyé au fournisseur d'email et devrait arriver au destinataire.                                                                                                                                                                                                              |
| **Livraison retardée** | L'email n'a pas pu être transmis au destinataire à cause d'une erreur temporaire (par exemple boîte mail pleine, erreur sur les serveurs d'emails). Il sera délivré prochainement.                                                                                                           |
| **Délivré**            | L'email a bien été remis au destinataire.                                                                                                                                                                                                                                                    |
| **Marqué comme spam**  | Le destinataire a marqué l'email comme étant du spam. L'adresse mail du destinataire pourra être bloquée par notre fournisseur d'email pour éviter de nouveaux envois.                                                                                                                       |
| **Échec (bounced)**    | Le serveur d'email a refusé l'envoi. Ce statut est accompagné d'une raison (souvent une boîte mail inexistante). Après plusieurs échecs de livraison, l'adresse mail du destinataire devient bloquée par notre fournisseur d'email.                                                          |
| **Bloqué**             | Plusieurs raisons possibles : l'email est invalide ou n'existe pas, le destinataire a bloqué l'adresse mail d'envoi, ou le destinataire a marqué un email précédent comme étant du spam. Lorsqu'un email est bloqué par le fournisseur d'email, il n'est plus débloqué sauf action manuelle. |
| **Erreur**             | La syntaxe de l'adresse mail n'est pas valide. Cet email n'a pas été envoyé au fournisseur d'email et n'est pas facturé.                                                                                                                                                                     |

***

## Pricing and Billing

|                         |                                                                                               |
| ----------------------- | --------------------------------------------------------------------------------------------- |
| **Price excluding VAT** | **0,0035 € - 0,0056 CAD / email envoyé**                                                      |
| **Billing Method**      | In terms of consumption, this relates to the number of emails actually sent from your domain. |
| **Subscription**        | None. This is not a subscription option.                                                      |

Specifically, 10,000 emails sent in a month represent **€35**. This amount is added to your Yoplanning bill, just like [SMS](/en/faq/faq-generale/tarification-des-sms-envoyes-depuis-yoplanning.pro.md) messages.

{% hint style="info" %}
**Emails sent from `info@yoplanning.com` are never charged.** Only emails sent from your own domain are charged. As long as your domain is not activated—and during a possible [temporary return to sending via Yoplanning](#temporary-return-to-sending-via-yoplanning)—you pay nothing.
{% endhint %}

***

## Why not just connect my Gmail or Outlook account?

This is the question that comes up most often: since I already have a professional address with Gmail or Outlook, why doesn't Yoplanning use it directly to send my emails?

The answer lies in the **volume**. Yoplanning sends a lot of emails: confirmations, tickets, invoices, pre-session reminders, post-activity messages. Standard email inboxes are not designed for this type of email delivery.

* **API sending limits are low.** Gmail, Outlook, and similar email services cap the number of emails an external program can send, usually on a daily basis. A busy weekend is enough to reach the limit.
* **At best, the sending stops.** Once the limit is reached, no more emails are sent until the next day: your customers receive neither their confirmation nor their ticket.
* **At worst, your account is blocked.** An unusual volume of automated sending is a warning sign for these services, which can suspend the account — and you then lose access to your email itself, not just to Yoplanning's sendings.

### And what about the idea that "emails are free"?

That's a misconception. **You already pay for your emails**, one way or another: the Google Workspace or Microsoft 365 subscription that hosts your professional address includes a sending quota, and this quota has a cost.

Using a professional sending platform, like Yoplanning, provides you with something that a simple connection to your Gmail or Outlook account cannot guarantee:

* a **deliverability** that is continuously improved, with authentication of your domain and monitoring of sending reputation;
* **continuity of service**: no daily limit reached during peak season, no suspended account, and automatic fallback in case of incident.

***

## What the feature covers — and doesn't cover

* **Sending only.** Yoplanning sends emails from your domain, but **does not handle receiving emails**. If a customer replies to your sending address, the reply arrives in the email account associated with that domain at your hosting provider. **Make sure this mailbox exists and is being checked**, otherwise your customers' replies will be lost.
* **Receipt and reading, no content analysis.** The tracking indicates whether the email has **arrived** and whether it has been **opened**. It does not detail the recipient's behavior within the email beyond this information.
* **The usage rules remain unchanged.** Connecting your domain does not authorize you to send commercial emails from Yoplanning: the restriction to informational and notification emails still applies. For your campaigns, see [Export customer emails](/en/yoplanning-academy/yoplanning-au-quotidien/communication-client/exporter-les-emails-clients.md).

***

## Special cases

* **You have a white label.** As soon as one team connects a domain, other teams within the same white label can **reuse that same domain**. Activation is then **immediate**, since the DNS configuration is already in place.
* **Advanced white label.** Organizations that already have their own sending configuration applied everywhere are not affected: their emails already leave from their domain.

***

## Temporary return to shipping via Yoplanning

In two situations, emails are automatically sent from `info@yoplanning.com`:

* **Your DNS configuration has been modified or deleted.** The domain is showing an error in the configuration window. Your emails will continue to be sent — via Yoplanning — while you restore the records.
* **Incident on our sending infrastructure.** In the event of a switchover to our backup solution, all emails are temporarily sent via Yoplanning.

In both cases, **no email is lost**: only the sending address changes while things return to normal.

***

## Common mistakes and solutions

| Symptom                                                          | Cause                                                                    | Solution                                                                                                                                                |
| ---------------------------------------------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **The domain remains "pending" after 48 hours**                  | DNS records are not being published, or are being published incorrectly. | Compare the records displayed in Yoplanning character by character with those in your DNS zone. Verify that you have placed them on the correct domain. |
| **The domain went into "error" mode even though it was working** | The DNS zone has been modified since                                     | Restore the records provided by Yoplanning, then restart the verification.                                                                              |
| **The domain name was rejected**                                 | You have entered an email address or a `www.` subdomain.                 | Enter the domain name alone: ​​`example.com`.                                                                                                           |
| **"Connect a domain" is unavailable**                            | No billing method is configured.                                         | Configure your payment method, or contact Support.                                                                                                      |
| **The "Emails" tab does not appear in the History**              | The domain is not yet activated                                          | The tab appears once the domain is connected and verified.                                                                                              |
| **Your customers respond and you receive nothing**               | No inbox exists on the domain.                                           | Email reception does not go through Yoplanning: create or retrieve the mailbox with your email hosting provider.                                        |

***

## Best practices

* **Use the domain your customers already know**, that of your website: this is what makes the sender credible.
* **Notify the person who manages your DNS** before starting the procedure: the window displays the records once the domain is entered, so you might as well transmit them immediately.
* **Send a test email** after activation — a ticket or confirmation to your own address — and check the result in **History > Emails**.
* **Never delete the records** set up for Yoplanning during a site redesign or a change of hosting provider, otherwise you risk returning to error.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/communication-client/connecter-votre-domaine-pour-lenvoi-demails.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
