Booking Confirmation Emails: Templates, Timing, and Authentication
A discussion of booking confirmation and reminder emails, covering template structure, timing, and authentication without promising a specific inbox-placement rate.
bookz is an appointment booking platform for service businesses — salons, personal trainers, consultants, and medical practices. When a client books, they need to receive a confirmation immediately. When their appointment is tomorrow, they need a reminder. When they need to reschedule, the rescheduling link in that email has to work. At 200k bookings a week, email is the core product interface.
Template architecture
bookz uses three primary email types: booking confirmation, 24-hour reminder, and post-appointment follow-up. Each is built with Sendbound's React Email renderer. The confirmation email is sent within 500ms of booking completion using Sendbound's priority queue. Reminders are scheduled at booking time using Sendbound's delayed delivery API, which lets bookz pass a future timestamp and forget — no cron jobs, no custom scheduler.
Deliverability configuration
bookz runs on a dedicated IP cluster through Sendbound. Confirmation emails go out on a high-reputation IP pool that's never used for marketing sends. Reminders go on a separate pool. This separation means a spike in reminder unsubscribes — common in any reminder system — doesn't contaminate the reputation of the time-sensitive confirmation pool.
"The dedicated IP pool separation was something we didn't even know we needed. Now I can't imagine not having it. Our confirmation emails never touch the reputation risk from reminder sends."
What's next
bookz is now using Sendbound's inbound email routing to let clients reply directly to their booking confirmation email and have those replies routed to the business owner as a support ticket. What used to require a custom SMTP server and significant engineering is now a three-line Sendbound webhook configuration.
