Email sending
Send the emails your clients get from your own address, such as [email protected]. Which emails it covers, the DNS records to add, and what to do if verification fails.
Emails your clients get from the app already carry your agency's name, but they come from Leal's address. Email sending changes that: once your domain is verified, they come from your own address, for example [email protected], and replies go to you.
Open Email sending in the agency menu. Only agency admins can set it up. If you don't see Email sending in the menu, it isn't available for your agency yet.
Which emails use your address#
- Password resets, email confirmations and account emails like exports and imports
- Onboarding and setup help emails
- Invitations to your clients' team members
- Emails your clients' customers get, like a link to their loyalty card
Campaign emails aren't included. They use each store's own sender settings. See Sender settings.
Set it up#
1. Choose your address#
Under Send emails from, enter an address on a domain you own, usually your website's, such as [email protected]. Optionally, set Replies go to: where your clients' replies land. Leave it blank to use the agency owner's email. Click Continue.
You can't use a shared email provider's domain (such as gmail.com or outlook.com) or Leal's own.
2. Add the DNS records#
After a few seconds the page shows the records to add. Log in to wherever you manage your domain's DNS and add each one:
| Records | What they're for |
|---|---|
| Three CNAME records | Prove you own the domain and sign your emails (DKIM), so inboxes trust them. |
An MX record and a TXT (SPF) record on bounces.yourdomain |
Handle bounced emails, and help your emails reach the inbox. |
A TXT record on _dmarc.yourdomain (Optional) |
A basic DMARC policy. Only add it if your domain doesn't already have one. |
Tips for adding them:
- Copy the Name column. Most providers add your domain to the end automatically. If you see it twice, delete the repeated part.
- On Cloudflare, set the CNAME records to DNS only (grey cloud), not proxied.
- The MX record's priority is 10. Some providers have a separate box for it.
- The SPF record goes on the bounces subdomain, so it won't clash with an SPF record on your main domain.
3. Wait for verification#
Leal checks automatically every 10 minutes, and switches your emails over as soon as the records are found. Click Check now to check straight away. Each record shows Found or Waiting. Most providers take a few minutes; some take up to 48 hours.
When it's done, the page says You're live, and the agency owner gets an email from your new address. Click Send me a test email to send another.
Nothing changes until then: your clients keep getting emails from Leal's address, under your agency's name.
Statuses#
| Status | Meaning |
|---|---|
| Setting up | Leal is preparing your records. This takes a few seconds. |
| Waiting for DNS | Leal is waiting to find your records. |
| Verified | Emails come from your address. |
| Needs attention | Something went wrong. The page says what. |
If the bounce records aren't found yet but the rest are, your emails are already being delivered from your address. Adding the bounce records helps them reach the inbox.
If verification fails#
If the DKIM records aren't found within 72 hours, Leal stops checking and shows Needs attention. Click Try again to start over. You'll get new records to add, and can delete the old ones.
Changing it later#
- Click Edit to change the part before the @ or where replies go. The domain itself can't be changed.
- To use a different domain, click Remove, then add the new one. After removing, emails come from Leal's address again until the new domain is verified.
Gotchas#
- If your address can't be used for a moment, for example because a DNS record was deleted, emails still go out, from Leal's address under your agency's name. A password reset never fails because of DNS.
- Replies go somewhere real. If you don't set Replies go to, replies land in the agency owner's inbox. Set it to a shared support address if you have one.
Still stuck?
Our team answers every message. Contact support