Notifications and email
Reynt sends transactional emails at each important booking event — booking created and confirmed, payment instructions and receipts, cancellations, inquiry replies, and more. Two console areas control them: the Notifications hub decides which emails go out and what they say, and Email delivery decides how they’re delivered.
The Notifications hub
Section titled “The Notifications hub”Open Settings → Notifications. The left rail lists every notification, grouped into Requests & inquiries, Bookings, Payments, and Contact forms. Each row shows whether it’s on and who it’s for (the guest, or your team). Select one to manage it on the right:
- Delivery — a channel toggle (email today). Turning it off is a hard disable: that automatic notification is never produced, even if a booking action asks for it. Manual resend buttons are unaffected — they always send.
- Email template — the editable content for guest-facing emails (see below).
- Preview — render the actual email with sample data right in the console, so you can check the result of template edits without sending anything.
- Send test email — send yourself a copy with sample data to any address you enter, in the language you pick.
A couple of rows behave slightly differently: the two team notifications (booking-request and contact-form) have no editable content — just a toggle and a test send — and Payment instructions is a manual-send-only email with no automatic trigger.
The notifications
Section titled “The notifications”| Notification | Sent to | Fires when |
|---|---|---|
| Booking request received (team) | Your team | A guest submits a request or inquiry on the storefront |
| Booking request confirmation | Guest | Right after that request/inquiry is submitted |
| Offer / proposal sent | Guest | You send an offer from a booking request |
| Inquiry declined | Guest | You decline a request or inquiry |
| Booking created | Guest | A request is published as a pending booking |
| Booking confirmed | Guest | A booking becomes confirmed |
| Booking modified | Guest | You modify a booking and choose to notify |
| Booking cancelled | Guest | You cancel a booking |
| Payment received | Guest | You mark a bank transfer paid |
| Refund confirmation | Guest | A refund is processed |
| Contact form received (team) | Your team | A guest submits the storefront contact form |
| Contact form confirmation | Guest | Same submission, auto-reply to the guest |
Most booking actions (publish, confirm, cancel, modify, mark-paid) also show a “send email notification” checkbox in their dialog. When the notification is turned off in the hub, that checkbox is hidden with a note pointing back here.
Editing email templates
Section titled “Editing email templates”For each guest-facing email you can customise the Subject, Heading,
Body, and Footer. Leave any field empty to fall back to Reynt’s built-in
default. In the body, type $ to insert a variable — placeholders like the
guest’s name, listing name, check-in and check-out dates, night count, guest
count, totals and amounts due, currency, and payment references are filled in per
email.
Some templates also expose data-inclusion options (whether to include payment instructions, the schedule, receipts, check-in details, the security deposit, or a booking link). The Booking Modified email inherits these from Booking Confirmed.
Per-language templates
Section titled “Per-language templates”Template texts are per language. If you support more than one language, edit each field per locale, and pick a Preview language when sending a test. At send time Reynt uses the recipient’s communication language (see Customers) to choose the right text. Missing template languages are surfaced on the Translations page, so you can fill the gaps (and use AI translation) there.
Email delivery
Section titled “Email delivery”Open Settings → Email delivery to control how mail is sent:
- Mail server — your own SMTP, Mailjet or Brevo account. When configured and enabled, all your mail is sent through it. You can temporarily disable it to route through Reynt without losing your credentials.
- Delivery tracking — on Brevo and Mailjet, a URL you paste into your provider so it reports deliveries and bounces back to Reynt. Without it your mail logs stop at Sent.
- Platform email fallback — when you have no active mail server, let Reynt send on your behalf from a platform address (“Your Name via Reynt”), with replies routed to your notifications inbox. Disable it to require your own server. Reynt never silently sends your mail from a platform address when this is off.
- Notifications address — the inbox that receives your team notifications and test sends. Keep it set.
- Email branding — a brand color that themes all customer emails: the header band, buttons, and accents. (This is independent of the storefront’s theme color.)
- Shared signature — appended to the bottom of every outgoing customer email
(also per-language, with
$variables). - Email confirmation gate — hold automatic customer/owner mail for review before it sends. See Email confirmation gate.
- Inbound email replies — route guest replies back into the Inbox.
- Email legal URLs — privacy policy and terms links added to the footer of customer emails.
- Inbox auto-close — whether (and after how many quiet days) resolved inbox conversations are closed automatically. See Inbox for how the sweeps behave.
Delivery bell and logs
Section titled “Delivery bell and logs”The bell in the top bar links to items needing attention (unread inbox conversations, emails held in the outbox). Every email that’s actually sent is recorded in Mail logs, where you can check its delivery status.