A property switches on WhatsApp and, understandably, enables everything. Guests now receive a message when they book, when the booking is confirmed, when a deposit is received, when a request is acknowledged, when it is updated, when it is resolved.
Within a fortnight the operations group is muted by three of the five people in it, and a guest has blocked the number — which means the confirmation they actually needed for their next stay will not arrive either.
The failure is not the volume in the abstract. It is that guest-facing and staff-facing messages were treated as one decision, so making the team's alerts useful made the guest's experience intrusive.
Choosing per event, and routing per event, separates them: a booking confirmation reaches the guest while its staff twin reaches an operations group, and a property can be noisy internally without a guest experiencing any of it.
The words matter as much as the routing. One editable template per event per channel means the confirmation reads in the property's own voice everywhere it is sent, rather than being written three times and drifting.
Why this matters to you: a messaging channel is a finite asset. It works because guests have not muted it, and the fastest way to lose it permanently is a fortnight of enthusiasm at the start.