A booking confirmation that silently fails to send is one of the fastest ways to lose someone’s trust, because the guest does not know it failed. They just think you ghosted them. So notifications got their own engine instead of being an afterthought bolted onto each feature.
Queued, retried, logged
Booking confirmations and reminders go out over email and WhatsApp through a single pipeline. Every message is queued, retried on failure, and logged, so when something does go wrong we can see exactly what happened instead of shrugging at a guest.
- One engine for every transactional message, not scattered send calls sprinkled through the code.
- Automatic retries, so a momentary provider hiccup does not quietly drop a message.
- A full log of what was sent, when, and to whom.
We learned the hard way that a provider accepting a message is not the same as it landing. The log tracks both, so “it said it sent” is never the end of the investigation.
Boring infrastructure, but it is the kind of boring that lets both you and your guests sleep. It is the same reliability floor we describe in payments and calendars on autopilot.
by Bolt 958
Want this for your own bookings?
Set up your page, sync your calendar, and start getting paid at 0% commission.
Become a host