The Booking Was Cancelled. Why Did the Welcome Message Still Send?
On Monday, a confirmed Friday stay creates a Thursday welcome message. On Wednesday, the guest cancels. On Thursday, the welcome message goes out exactly on time. The scheduler did its job; the workflow made the wrong decision.
Schedule a check, not an unconditional send
At send time, verify the current reservation, property, arrival date, contact route and manual holds. If a required source is unavailable, keep an access-related message pending for review rather than treating an old record as current.
| Event | Expected result |
|---|---|
| Guest cancels before dispatch | Suppress the welcome message and record why |
| Arrival moves to Sunday | Invalidate the old schedule; allow one appropriate message for the new date |
| A complaint remains open | Pause promotional or review messages; assess necessary operational messages separately |
A complaint should not suppress an essential update about where to collect a key. Assign rules by message purpose rather than applying a blanket “do not contact” switch to every operational situation.
Test what the guest does not receive
Replay the same rescheduling event twice. Does it create two messages? Place a manual hold and run the next synchronization. Does the hold survive? Finally, ask the duty manager to explain why a particular message did not leave. The answer should identify a reservation, a reason and any outstanding human action.
Use delivery labels honestly. “Queued,” “handed to provider,” “delivery confirmed” and “read” are different claims. Show only the evidence the channel actually provides. A dependable guest workflow is one the host can explain both when it sends and when it deliberately stays silent.