Email confirmation gate

The email confirmation gate lets you review automatic emails before they reach a guest. When it’s on, instead of sending a booking confirmation, payment instruction, or other operator-initiated customer or owner email straight away, Reynt renders it and parks it in the Mail Outbox first.

Emails that acknowledge something the guest just did are never held — see What is and isn’t held.

It’s a safety net — useful while you’re setting up templates, importing data, or simply want a human to glance at every guest email before it goes out.

Turning it on

Enable it under Settings → Email delivery → Email Confirmation Gate (“Hold automatic emails for review before sending”). It’s a per-tenant switch and off by default. Turn it off and automatic emails send immediately again.

Choosing what happens next

With the gate on, you pick how a held email resolves:

Wait for me — nothing goes out until you send it from the Mail Outbox. The safest setting, and the one to start with. The cost is that every automatic email becomes a task: if nobody works the outbox, guests hear nothing.
Send after a delay — the email sends itself once the delay is up (15 minutes by default; anything from 1 minute to 24 hours). You get a notification the moment it’s held, with time to look at it and, if something is wrong, hold it back.

The second one is the better fit once your templates have settled. It turns the gate from an approval queue into an interception window: you don’t have to do anything for the normal case, and you still get a chance to catch the unusual one.

The useful action inside that window is Hold back, not Send — the email was going to send anyway. Holding it back stops the clock on that one email, which then waits for you exactly as it would in “Wait for me” mode. So you only have to decide that an email needs a closer look, not finish looking within the delay.

What is and isn’t held

Only emails you set in motion are held — a booking confirmation, a cancellation, a declined inquiry, an offer, a modification. These are not held:

Receipts for something the guest just did — the confirmation for a booking request, an inquiry, a contact-form message, or a received payment. The guest is waiting on that response right then, and a missing one reads as “the form didn’t work”, so it always sends immediately.
Instant bookings — when your booking flow is set to instant, a storefront booking confirms itself and its confirmation goes straight to the guest. Reviewing it would mean the guest who just paid hears nothing.
Your inbox replies — operator-written replies from the Inbox send in real time.
Team notifications — booking-request and contact-form alerts to your own inbox.
Test emails — the “send test” buttons on the Notifications hub.

An automatic email that’s turned off in the Notifications hub is never produced in the first place, so it never reaches the outbox — the preference check happens before the gate.

The Mail Outbox

Open Mail Outbox in the main sidebar — it appears there only while the confirmation gate is on. It lists every held email with its type, recipient, subject, and — in “Send after a delay” mode — when it goes out. A row reading Waits for you has no clock on it: either you’re in “Wait for me” mode, or someone held that email back. For each row you can:

Preview — open the exact rendered email you’re about to send.
Send — dispatch it, unchanged, to the recipient.
Hold back — stop its automatic send so it waits for you. Only shown while a send is actually scheduled, and reversible by pressing Send.
Discard — cancel it; it is never sent (this can’t be undone).

When you have a backlog, Confirm all and Discard all act on every pending email at once. If a send fails, the email stays pending so you can retry.

The Mail Outbox nav item shows a badge with the number of emails waiting, and the top-bar notification bell surfaces the same count, so held mail doesn’t get forgotten.

Once an email is sent from the outbox, it’s recorded in Mail logs like any other outgoing mail.