Notifications & Comms Center · Documentation

User Journey

The end-to-end path through Notifications & Comms Center, from trigger to outcome.

1
Event → personalized message → sent
A guest completes a booking. `booking.created` fires, the booking-confirmation template is picked and personalized against the guest's context, and a confirmation lands in the delivery log — no agent involved. Separately, the owner opens a marketing template, generates an AI-personalized variant, enables it, and triggers a send that also lands in the sent viewer.
2
How it connects
The center is fed by the rest of the ecosystem: bookings (#01/#15/#20), payments (#34), promotions (#36), and loyalty (#12) emit events that map to templates — booking.created → confirmation, payment.captured → receipt, booking.cancelled → notice (reminder / review-request / marketing are manual-trigger). Every send emits `notification.sent`, and the sent viewer is the same surface #03's replies and all confirmations share.