Otto Docs

Travel and documents

Trips assembled from booking mail, timezone-correct segments, cancellation deadlines, and the days-in-country ledger.

A trip assembles itself

Booking confirmations arrive in fragments: the flight from one airline, the return from another, the hotel a week later. The trip object parses each one and merges fragments into a single trip keyed by date range, so you stop forwarding yourself bookings and hunting for a confirmation code at a counter.

Parsed out of the mail: PNR, flight numbers, times with their timezone, hotel address, check-in and check-out.

Timezones are the whole point

A flight time without a zone is a bug, not a rounding error. Segment times carry their zone, and where the zone cannot be determined the trip reports the problem rather than guessing.

There is no built-in airport-to-timezone table. It is a data file, empty by default, and an unknown airport produces a zoneless time that is explicitly reported as a problem. The alternative was shipping a guessed table, which would produce confidently wrong departure times.

Trip mode

While a trip is current, or starts within fourteen days, the brief carries a Trip: line right after the calendar: what is due next, then each remaining segment in its own airport's local time, zone named. It is capped at 300 characters so it never pushes the recent thread out of the brief's own budget, and it is left out entirely — not faked — when building it fails.

Cancellation deadlines

Free-cancellation dates are extracted at parse time, and a guard fires once in the twenty-four hours before the deadline lapses, always urgent so it cannot get stuck behind a snooze until the money is already gone: keep or cancel, with a button for each. A deadline whose zone is unknown is compared by date rather than converted, and quoted exactly as the hotel wrote it. Rebooking a stay with a new cutoff earns its own guard.

Check-in

One event fires the moment online check-in opens — twenty-four hours before departure by default, or whatever the booking states — and is skipped if the window is barely worth a separate message. It is keyed to the booking, so a connection or a rebooked duplicate of the same leg never raises a second one. Only sentences that say online, web or mobile count; airport-counter check-in hours are ignored so the message never announces the wrong window.

In the air

Once departure and arrival are both known, the trip tells the queue you are airborne. Normal-priority messages hold automatically, no snooze needed, and land as one digest headed "held while you were in the air" the moment the hold lifts — taxi-in plus ten minutes after landing. Urgent messages and live conversation still go through. A separate arrival note follows: local time at the airport, then what's next — the next flight, the stay that starts that day with its address, or that nothing else is booked. A layover gets no note of its own; only the last leg of a connection does.

Nothing here reads a live flight-data feed — every time above is the booked schedule, degrading honestly rather than reporting a delay it cannot see.

Trip expenses

When a trip carries an id and expenses: true, receipts already in the ledger are attributed to it: the same source email as the booking, a currency the destination uses and home does not, a merchant or note naming the destination, or a travel category — in that order of confidence. Totals are kept per currency, never summed across them, and anything inside the trip's dates that does not match one of those signals is listed separately as not counted rather than silently folded in.

Days in country

Presence per country is derived from trip segments, giving a rolling count against the thresholds that actually matter: visa limits and tourist caps.

It stays silent until a threshold is within reach, or until a booking you are about to make would cross one.

On this page