> ## Documentation Index > Fetch the complete documentation index at: https://docs.riservahq.com/llms.txt > Use this file to discover all available pages before exploring further. # Email settings — who your emails come from, what they say, and how they look *New* Use **Settings → Emails** to set who guest emails come from and which moments send. You can also rewrite their opening and closing lines, and brand them with colours, a logo, a banner image and each experience's own photo. Riserva delivers the mail for you. There is no provider account to create and no API key to paste. The **Delivery** card's **Guest email** badge reads **Sending** when delivery is live. **Log only** means delivery isn't configured. Every email is still written to the reservation's timeline; it just isn't delivered. Contact Riserva support. ## On this page 1. Choose who the email comes from 2. Send from your own address (optional) 3. Rewrite what the emails say 4. Brand the design 5. Preview it, then send yourself a test 6. Choose which emails send All of these save from the bar at the top of the screen. See **Save your changes** at the end. *** ## 1. Choose who the email comes from | Field | What it does | | - | - | | **Sender name** | What guests see in the *From* line. The field shows your store's name as a hint, but it is not filled in for you: "Left blank, guests see the sending address alone." Type the name you want. | | **Sends from** | The address Riserva sends on your behalf. It is read-only, unless you connect your own (below). | | **Reply-to** | Where a guest's reply lands. Leave it blank and replies go to the sending address. | Set a reply-to address. Guests reply to confirmations far more often than people expect, and Riserva's sending address isn't a mailbox anyone at your winery reads. *** ## 2. Send from your own address (optional) Guest email goes out from Riserva's sending address by default, and that address is perfectly deliverable. If you'd rather guests saw `reservations@yourwinery.com`, connect it here. It takes one DNS change. ### Connect your own sending address 1. Under **Custom sending address**, type the address into **Sending address**, such as `reservations@yourwinery.com`. 2. Press **Connect domain**. 3. Riserva shows a short list of DNS records. Each has a **Type**, a **Host**, a **Value**, and sometimes a **Priority**. 4. Add each record wherever your domain's DNS is managed: your registrar, Cloudflare, or your web agency. 5. Come back and press **Check verification**. The address must be at a domain you control. Gmail, Outlook and the like can't be used. Paste each **Host** exactly as shown. These names are relative to your domain, so `send` becomes `send.yourwinery.com` on its own. ### What happens while you wait Nothing breaks while you wait. Guest email keeps going out from Riserva's address until your domain is verified, and the card says so in those words. DNS usually propagates in minutes; it can take up to 72 hours. When it verifies, the badge turns **Verified** and the records disappear. The card reads **Sends from `reservations@yourwinery.com`**. That's the address on every confirmation, reminder and cancellation from then on. **Remove** stops Riserva using your address and puts guests back on Riserva's, immediately. It does **not** undo your DNS records, and you don't need to delete them. If you reconnect the same address later, it picks up where it left off, already verified. Your own address is the difference between a guest recognising the sender and not. It also puts your domain's reputation behind your reservation mail. It is genuinely optional. Plenty of wineries never do it, and their email arrives fine. *** ## 3. Rewrite what the emails say 1. Under **Content**, pick an email. 2. Rewrite its **Opening lines**: the paragraph under the heading. 3. Rewrite its **Closing lines**: the last thing the guest reads. Leave either blank to keep Riserva's wording. Press Enter for a new paragraph. Two things never change, on purpose: * **The greeting stays.** Riserva always writes "Hi Marguerite," itself, so your text is personal without you managing name tags. * **The facts stay.** Date, time, party, confirmation code and location live in the details card, which your words can't touch. A rewrite changes how the email reads, never what it says. The team alert (**New reservation alert**) isn't rewritable. It's addressed to your own staff, and its first line *is* the information. ### Add a "Good to know" note to one experience's emails One more piece of wording lives on the experience, not here. Each experience has a **Good to know (emails)** field, on its page under **Experiences**. Use it for arrival details, parking or dress code. It appears in that experience's confirmation, reminder and update emails as its own little section. *** ## 4. Brand the design Emails are one 600px column. That's fixed, because no email client can be trusted with more. Inside the column, you control: | Field | What it does | | - | - | | **Accent colour** | The button and the confirmation code. If you pick a light accent, the button text darkens by itself so it stays readable. | | **Page colour** | The paper behind the email card. Nothing sits on it directly, so it can go as dark as you like. | | **Card colour** | The surface the words sit on. The text stays dark, so Riserva only accepts light shades here. It will ask for a paler one rather than send something unreadable. | | **Heading style** | Serif or sans, using typefaces every email client already has. Custom font files don't survive email clients, which is why there's no upload. | | **Logo** | Shown above the heading at 150px wide. Drag an image in, or click to pick one, the same as adding a photo to an experience. | | **Header image** | A banner across the top of every guest email. Drag in or click to upload; **Replace**/**Remove** once it's set. | | **Use each experience's photo as the email banner** | On by default. A guest's email is bannered with the photo of the experience they booked, so each experience's emails look like that experience with no setup. Turn it off to always use the header image instead. | | **Footer line** | One line under your name: an address, a phone number, or a note about why the guest is hearing from you. | * Every colour has a **swatch you can click** to open a picker. You can also type or paste a hex code if you have exact brand colours. * Uploads go to your store's files (**Content → Files** in Shopify). * An image only takes effect when you **save**. The toast reminds you. Some email clients block images, so every email is written to read perfectly without them. Don't put anything essential inside an image. Colours must be hex values like `#6B2233`. Anything Riserva can't read falls back to the default palette rather than producing a broken email. Image URLs must be full `https://` addresses. *** ## 5. Preview it, then send yourself a test The **Preview & test** section shows the real email, not a mock-up. It updates live as you type anywhere on the page. ### Choose what the preview shows Two pickers control the preview: * **Email**: any touchpoint, including ones you've rewritten. * **Experience**: pick one of yours, and the preview becomes exactly what a guest of that experience receives. **Sample reservation** shows a generic example instead. With an experience picked, the preview uses its photo as the banner and its real add-ons. It shows a date its schedule actually offers. The money emails show its price; a private buyout shows its flat price, not price-per-guest. **Expand preview** opens it full-size, with a **Desktop / Mobile** toggle. Mobile is the genuine phone rendering, not a shrunken desktop one. ### Send a test email 1. Save any changes first. 2. Enter an address under **Send to**. 3. Press **Send test**. Riserva sends the email and experience you've selected, using your **saved** settings. The test uses saved settings, not what's currently on screen. The help text under the field tells you when unsaved changes are being left out. You'll see one of three outcomes: * **"Test email sent to …"**: it worked. Check the inbox, and the spam folder if it's not there. * **"Logged, not sent"**: delivery isn't configured for this store (usually a dev store). The message was rendered and recorded rather than delivered. * **"The provider rejected the message"**: the banner shows the delivery provider's own words. > **Good to know** > Connecting or removing a custom sending address is **not** a > saved-with-the-bar change. Those buttons act immediately. *** ## 6. Choose which emails send **Notifications** sits at the bottom of the page, because you'll set it once and rarely return. Every touchpoint has a switch, aligned with its name: * Reservation confirmed * Pre-visit reminder * Reservation cancelled * Payment failed * Reservation rescheduled * Payment due * New reservation alert * Waitlist — table ready **Every one is on to start with.** A winery that never opens this page still gets confirmations. Under each name, one line says when that email goes out. ### Change an email's subject line Each touchpoint has a **Subject line** field. Leave it blank to keep Riserva's own subject, shown in the field as a hint. Fill it in to override. Switching a touchpoint off greys its subject field out rather than hiding it. You can always see what the switch governs. ### Set who gets the New reservation alert **New reservation alert** goes to your team, not guests, when a reservation is made online. Under it is an **Alert addresses** field. * Type up to five addresses, separated by commas. * Leave it empty and no alert is sent. * The field saves with the rest of the page. * It greys out while the alert's switch is off. See [Customer emails](/guest-experience/customer-emails#the-alert-to-your-team). ### Payment due: not sending yet **Payment due** carries a **Not sending yet** badge. It's written, but nothing triggers it yet, so its switch changes nothing today. See [Customer emails](/guest-experience/customer-emails#an-email-that-exists-but-isnt-switched-on). > **Good to know** > Turning an email off doesn't make Riserva go quiet. Riserva still records on > the reservation's timeline that the moment happened and the email was > skipped. A guest asking "did you send me anything?" has an answer. *** ## Save your changes Changes on this page save from the bar that appears at the top of the screen when you edit something, like every settings page in Riserva. There are no per-card save buttons. A confirmation toast appears when it's done. *** **What things mean on this screen:** [What things mean: Settings](/reference/settings) ## Related * [Customer emails](/guest-experience/customer-emails) — every touchpoint, when it fires, and what isn't built * [What guests see, end to end](/guest-experience/what-guests-see) * [Troubleshooting](/troubleshooting/troubleshooting#guests-arent-getting-emails) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.