System emails
Transactional email templates, layouts, branding, and provider settings.
Settings → System emails is the home for everything that shapes outbound mail:
| Section | Purpose |
|---|---|
| Templates | Per-event subjects and MJML bodies |
| Layouts | Shared HTML/MJML wrapper with a {{ slot }} for template content |
| Configuration → Branding | Logo, colours, font, footer — see Email branding |
| Configuration → Email provider | Sender address, SMTP transport (read-only for most tenants) — see Notifications overview |
Templates
Each workspace starts with a complete default template set. You may edit any template; restore defaults per key if you need to reset copy.
Your customised templates are kept
When ServEase refreshes its standard booking emails, a template you have customised is left exactly as you wrote it; only templates you have never edited are brought up to date. Restore default for a key replaces your version with the standard one, so use it only when you want that.
Payment instruction emails
If you customise the payment instructions email, keep the facts a customer needs to pay:
- the amount to pay (
payment.amountFormatted); - for bank transfer or cheque, the payment reference (
payment.reference) the customer must quote; - the payment details you configured on the payment method — the field list (
instructions.fields), or its description or notes when that is where you wrote them.
A cash payment settled in person does not need a separate reference. The payment link email is different: its link is the way to pay.
Locales
Each notification key (for example booking_confirmed) can have one row per locale. Customers and staff receive the variant matching their language preference when available, with tenant fallback rules when not.
Placeholders
Template subjects and MJML bodies use placeholders such as:
- Customer or staff name
- Service name and booking time
- Booking reference and links (
bookingUrl,paymentUrl, etc.)
The editor shows the variables schema for each template so you know which placeholders are valid.
MJML
Bodies are written in MJML for responsive email HTML. Use mjml.io try-it-live to prototype, then paste the MJML into ServEase.
Status
Templates can be draft or live. Only live templates are used for outbound mail.
Layouts
Layouts wrap all templates with shared headers, footers, and styling. Every layout must keep a {{ slot }} marker where template content is injected.
Configuration
Open the Configuration tab for Branding and Email provider settings. Branding is editable by tenant admins; provider and deliverability fields are usually managed by ServEase — contact support if you need a custom domain or SMTP change.