What happens if I change a tour date in chat but not in the OTA?

You create a mismatch: the guest expects the new date, but the OTA and possibly your reservation system still hold the old one. The cancellation window keeps calculating against the original date, so a 'free cancellation up to 24 hours before' can quietly become invalid — exposing you to disputes, chargebacks, and dispatch errors.

Why do date changes break cancellation windows?

Cancellation policies are calculated from the booking's start time as recorded on the platform. If a date moves only in conversation, the platform still measures against the old time — so the protection you and the guest think applies is being computed from the wrong date.

How should tour operators handle date-change requests?

Apply the change to the booking itself and let it propagate to the OTA it came from, rather than just confirming in the message. The conversation and the reservation — including its cancellation terms — need to move together.

Can date changes be handled automatically?

Yes. Tourbo's Guest Communications is connected to your OTAs and reservation system, so a date change made in the inbox updates the booking and the channel together, keeping cancellation windows and dispatch accurate.

Guest communications

Handling Tour Date-Change Requests Without Breaking Your OTA Cancellation Windows

June 17, 2026 · Tourbo

When a guest asks to move their tour to another day, the dangerous move is to reply “no problem, you’re all set” without changing the booking everywhere it lives. Do that and the OTA still holds the original date — so the cancellation window keeps calculating from the wrong day, and the protection you both assume applies may not. Date changes are the most common way a friendly reply turns into an operational and financial problem. Here’s how to handle them cleanly.

How a simple date change goes wrong

Picture the chain. A guest booked through an OTA for Thursday with “free cancellation up to 24 hours before.” On Tuesday they message: “Can we switch to Saturday?” You say yes in the chat. But the booking record — on the OTA, and maybe in your own system — still says Thursday.

Now several things are quietly broken:

The cancellation window is measured against Thursday, not Saturday. The 24-hour protection is computed from the wrong date.
Your operations team dispatches against Thursday’s manifest. Saturday’s vehicle and guide may not account for this group.
If anything goes sideways, the OTA’s record disagrees with what you promised, which is exactly the position you don’t want to be in during a dispute or chargeback.

Nobody did anything malicious. The reply just didn’t reach the booking.

Why the cancellation window is the sharp edge

Cancellation terms are calculated from the booking’s recorded start time. That’s the whole mechanism. Move the date in conversation only, and the platform keeps doing math against the original time — so a window you believe is open may be closed, or one you think is closed is open. Either way, you’ve lost the certainty the policy exists to provide, and you won’t find out until someone tries to cancel or you’re explaining yourself to the platform.

The clean way to handle a date change

The rule is simple: the conversation and the booking move together.

Confirm the new date and availability before you promise anything.
Apply the change to the booking itself, not just the thread.
Propagate it to the OTA the booking came from, so its record — and its cancellation window — reflects reality.
Make sure operations see the new manifest, so dispatch matches what the guest expects. (This is why a tight day-before dispatch check catches what slips through.)
Then reply to the guest — now your “you’re all set” is actually true.

The friction is that steps 2–4 mean logging into the OTA, updating the reservation, and remembering to tell ops — for every change, while you’re also running tours. So it gets shortcut to step 5, and the gaps accumulate.

Closing the gap automatically

This is precisely the problem Guest Communications is designed around. Because it’s connected to your OTAs and reservation system, a date change made in the unified inbox updates the booking and the channel it came from together — so the cancellation window recalculates correctly and the change flows to operations, instead of living only in a chat bubble. It doesn’t just reply about the booking; it modifies it. (More on why that distinction matters in managing guest messages across channels.)

The bottom line

A date change isn’t a message to answer; it’s a booking to move. Keep the conversation and the reservation in sync — including the cancellation terms and the dispatch manifest — and the friendly “sure, Saturday works” stays true all the way through, instead of becoming a dispute you didn’t see coming.