Emails
The three layers that shape every email your buyers receive — organization branding, editable texts, and per-event overrides — and when each email fires.
Every email a buyer gets from Bookitive is yours to shape. The system sends transactional mail automatically at key moments — a paid order's tickets, a reservation's payment instructions, a waitlist offer — and you control how all of it looks and reads through three layers.
The three layers
- Branding (visual) — logo, accent color, footer, and the bank/payment details printed on reservations. Branding →
- Texts (copy) — every sentence of every template, plus the sender name and reply-to address. Editing templates →
- Event overrides — any text, overridden for a single event, layered on top of your organization defaults. Event overrides →
The layers stack: an event email uses the event's override if present, otherwise your organization text, otherwise Bookitive's built-in default — so you can customize as much or as little as you like and never end up with a blank email.
The emails and when they fire
Transactional mail "goes out automatically at key moments":
| When it sends | |
|---|---|
| Order confirmation | An order is paid — tickets attached. |
| Reservation | An unpaid reservation is created — payment instructions and deadline. |
| Reservation reminder | Less than your chosen number of hours remain to pay. |
| Abandoned order | Once, when an unpaid reservation expires — invites the buyer to try again. Off by default. |
| Order couldn't be completed | An order can't be fulfilled (seats taken first, or rejected) — explains neutrally. |
| Seat change | You reseat a ticket and choose to notify. |
| Waitlist confirmation | Someone joins a waitlist. |
| Waitlist offer | Seats free up — a time-limited link to buy. |
The full field-by-field list, variables, and which emails can be turned off is in the reference.
Buyer transactional email copy is Czech-only — the templates ship in Czech. (The per-event language setting localizes tickets and invites, not these transactional emails.) Operational mail to you follows your account language. And delivery is best-effort after the sale: a mail hiccup never fails an order — the tickets exist, the email retries.
Related
People directory
One merged view of everyone around your organization — members, event staff, and a saved roster — and how the roster lets you prepare people before granting access.
Branding
Make customer emails look like yours — logo, accent color, footer text, and the bank/payment details printed on reservation emails — with a live preview.