🧰 Understanding "After the Reservation was Updated" Campaign Triggers
When a reservation is updated, it’s important that guests receive the latest information about their stay. To automate this, Bookboost provides three related triggers:
- "After the Reservation was Updated" – This trigger activates when changes occur to the reservation but does not include changes related to space types.
- "After the Reservation or Space Type was Updated" – This trigger includes changes to the number of guests, start/end date, and space type.
- "After the Reservation or Charged Space Type was Updated" – Similar to the second trigger but also includes updates to charged space types.
The logic behind how these triggers function is the same, so this article explains how they work, when an Update Campaign is sent, and how multiple updates affect scheduling.
💡 When Does This Trigger Activate?
This trigger activates when specific changes are made to a reservation:
- Number of guests is changed
- Start or end date is modified
- Space type (room type or area) is updated
When any of these changes occur, the system waits 30 minutes before sending an Update Campaign. This delay ensures that multiple changes made within that timeframe are included in one message rather than sending multiple emails.
A guest email update does not trigger the campaign schedule. However, if the guest’s email is updated, any scheduled campaigns will be sent to the new email address instead of the old one.
⏳How Does the Update Scheduling Work?
- If the reservation was created less than 30 minutes before an update, no Update Campaign is scheduled.
- If an update has already been scheduled, any additional updates within 30 minutes will not trigger another campaign.
- The system waits 30 minutes after the last update before sending the campaign. This ensures all modifications within that period are included in a single message.
- The campaign always contains the latest information at the time it is sent, even if multiple updates occur within the 30-minute window.
Example Scenarios
To make it easier to understand, here’s an example of how the system handles updates:
Time | Action | Outcome |
18:00 | Reservation created | No update campaign sent |
18:29 | First update made | No update campaign sent (update within 30 minutes of creation) |
18:30 | Second update made | ✅ Update campaign scheduled for 19:00 |
18:59 | Third update made | No additional campaign scheduled (within 30 minutes of the last scheduled update) |
19:00 | Fourth update made | ✅ New update campaign scheduled for 19:30 |
📌 Key Takeaways
- Only specific changes trigger an Update Campaign (number of guests, dates, or space type).
- The system waits 30 minutes before sending an update to group multiple changes together.
- If an update is already scheduled, no new campaigns will be triggered for changes within 30 minutes.
- The campaign always contains the most recent updates.
- If the guest’s email is changed, scheduled campaigns will be sent to the new email.