Notifications
What gets emailed, when, and to whom.
Every customer-facing email in the system goes through one shared sending path, is logged, and is owner-editable — there's no email hidden somewhere that skips these rules.
Customer emails
Roughly forty distinct templates cover the full lifecycle of every product line: confirmations, receipts, reminders (booking, invoice, membership renewal, ID expiry, card expiry), status changes (approved, suspended, reactivated), and the post-purchase "want an account?" nudge for guest checkouts.
A customer who has opted out of notifications never receives one — that suppression is checked centrally, not per-template, so a new email type can't accidentally bypass it.
Editing templates
Owners and admins can edit any template's subject and body from
/admin/email-templates, using {{variable}} placeholders for
computed content (amounts, dates, links). Editing never touches the
computed values themselves — only the wording around them. A template can
be reset back to its default at any time.
Staff digests and alerts
Three scheduled digests summarize activity for staff: a daily front-desk brief, a daily accounting brief, and a weekly owner report. Separately, one-off staff alerts fire on specific events that need a human to look at something soon — a failed automatic provisioning step, a new inquiry needing review, a refund held above the approval threshold. Both digests and alerts are owner-editable the same way customer templates are.
Resending an email
If a customer says they never got something, staff can resend either a specific proposal email or any past entry from a customer's communication log — this re-delivers the exact content that was actually sent, not a freshly re-rendered version that might differ if the template's changed since.