Capability
Confirmations, reminders, delivery alerts and follow-ups sent against the order, before arrival, during the stay and after departure.
Messages hang off the order rather than off a marketing list, so what the customer receives matches what they booked and where it is going. A pre-arrival note carries the delivery window and the access detail.
During the stay the delivery alert lands at the moment the driver confirms the drop. Anything that changes on the order, a swap or a late pickup, reaches the customer without somebody remembering to send it.
After departure the follow-up asks for the review and opens the door to next season, timed off the actual return rather than off a guessed date.
4 bikes and 2 umbrellas, 14 Sea Pines Circle. Left inside the garage.
Every message hangs off the order, so a reply about a delivery reaches the person holding that run rather than a shared inbox.
Staff hours spent answering questions the customer should never have needed to ask.
The number to watch is inbound contacts per booking, and repeat bookings from past guests.
This is transactional messaging tied to orders. It is not a marketing automation suite, and it does not manage broadcast campaigns or audience segments.
Every capability page on this site carries a section like this one. Why that is.
Confirmations, reminders, delivery alerts and follow-ups sent against the order, before arrival, during the stay and after departure.
Bodhisys handles it as part of the platform rather than as a paid module or a partner integration. There is no monthly fee. A 4.5% charge is added to each reservation and paid by your customer at checkout.
Both. Confirmations, delivery alerts and follow-ups go by text and email.
Yes. Messaging runs off the order, so the content matches the reservation and the address.
No. It handles transactional messaging around a booking rather than campaigns.
The same capability behaves differently by category. These are the per-industry versions.
Verified against public documentation, 2026-08.
