Skip to main content
Sailia sends a built-in booking confirmation immediately after every successful booking. To customise it — add your branding, set the tone, and include specific instructions — build a workflow on the Booking confirmed trigger.

​
What makes a good confirmation

A solid confirmation email:
  • Confirms what they booked, when, and where
  • Feels personal (uses their name)
  • Looks consistent with your brand
  • Tells them what’s next — what to bring, when to arrive, who to contact

​
Build the email

1

Open Communications → Workflows

Find the Booking confirmed trigger.
2

Choose a session group

Pick All sessions to start, or a specific session group if you want different confirmations for different course types.
3

Create a new template

Click Add communication → Create new template. Name it clearly (e.g. Booking confirmation).
4

Write a clear subject line

Use merge fields to make it personal — for example, Your booking is confirmed — or You’re all set! on .
5

Build the body

See the merge field reference below and include all key details.
6

Set timing and recipient

Pick Immediate timing and send to the Client email.
7

Test and save

Use Send test email before going live. Check on both mobile and desktop.

​
What to include in the body

  1. Friendly greeting — use the customer’s name.
  2. Confirmation statement — make it clear the booking is locked in.
  3. Booking details — name, date, time, location, participants.
  4. What to expect — anything they should know in advance.
  5. Next steps — waiver to complete, arrival time, where to park.
  6. Contact info — how to reach you if anything changes.

​
Merge field reference

These fields are filled in automatically for each booking.

​
Customer

​
Booking

​
Location

​
Tips

  • Keep it scannable — headings and bullet points work better than long paragraphs on mobile.
  • Always test with a real booking before going live.
  • For different course types with very different content, use session groups and build a template per group.
  • Reuse headers, footers, and signatures via saved blocks.

​
Common mistakes

  • Forgetting merge fields — the email feels generic.
  • Including too much information — customers won’t read it.
  • Missing the date, time, or location — the most important details.
  • Skipping the test step — small typos and broken merge fields slip through easily.

Pre-arrival reminders

Send a reminder 24 hours before the session starts.

Follow-up emails

Send a thank-you and feedback request after the session.