Status updates trigger notifications

Silent state changes erode user trust and generate support load: customers who cancel, reschedule, or get confirmed without receiving a notification assume the transaction failed and either double-book, contact support, or show up to appointments that no longer exist. Missed notifications on cancellation and rescheduling are a direct user-experience failure that drives no-shows, duplicate bookings, and chargebacks. Out-of-band confirmation is also a baseline expectation under consumer protection guidance for bookings involving payment.

Wire a notification call into each status-transition handler so the email or SMS fires in the same code path as the database update, after the transaction commits. Put the integration behind a small helper in src/lib/notifications.ts and call it from every handler that writes status. Example:

await db.booking.update({ where: { id }, data: { status: 'CANCELLED' } });
await sendBookingEmail(booking, 'cancelled');