Timezones and the traveller's clock
Every automatic message is scheduled against the clock the traveller is actually living on. Getting that wrong is the difference between a good-morning message and being woken at 3am.
How it is worked out
In order:
- Before departure — the trip's Departing from timezone. If you have not set one, the departure timezone of the first flight.
- Once they are moving — the arrival timezone of the last segment that has finished. A flight that lands in Madrid puts them on Madrid time.
- After the return flight — home again, because the return flight lands there. No special handling needed.
The trip's own Timezone field is the destination, and is only the fallback when nothing else applies.
The field that matters most
On any segment, Ends in (timezone) is what moves the clock. Set it whenever a segment finishes in a different zone.
This is not just for flights. Coaches, trains, ferries and long car transfers cross zones too, and they are the ones most often left blank — Madrid to Lisbon, a train into London, a ferry between islands.
Flight lookup and PDF import fill this in for you (see load your first trip). Segments you add by hand do not, so it is worth a glance before you save.
When no segment carries the change
Sometimes a zone change belongs to nothing: a self-drive day across a border, or a leg logged as one line. Add a segment of type Timezone change at the moment it takes effect, with the new zone in Ends in (timezone).
It appears in the traveller's itinerary as a clock-change note, which is useful to them anyway.
Checking it
Open the trip's timeline. Any segment that ends somewhere else shows both zones. If a traveller reports messages arriving at strange hours, that is the first place to look — followed by the trip's Departing from field. Every automatic message is scheduled on this clock; the full list is in what the concierge sends, and when.