When a Meeting Type is set to host time zone, availability windows are calculated based on wherever a rep currently is. If a prospect books six days in advance and the rep will be traveling to a different time zone by then, Chili Piper has no way to account for that, and the meeting gets booked at a time that's correct for the rep's current location but wrong for where they'll actually be.

Admins or reps should be able to set a time zone override for a specific date range, so that future-dated availability calculations reflect where the rep will be, not where they are today. This override should apply to round-robin routing, not just personal meeting links, since that's where the mismatch causes the most operational pain.

The current workaround is asking reps to manually block calendar time ahead of travel, or to never change their device time zone regardless of where they are. Both create friction and rely on rep discipline that doesn't scale, especially for B2C teams with high booking volume and reps who travel frequently.