Turtini

Trip events: posting an update about a booking you run

Post an update when something changes on a booking your organization sells or runs on a traveler's trip. Editors, admins and owners can post.

1. Trip events, Post an update about a booking you run.
2. Choose the trip and the booking. Only trips that can see your organization, and only the bookings you sell or run on them, are listed: an agency's accepted proposal items, or bookings a traveler linked to you.
3. Choose what happened and fill in the fields. Each kind has a fixed list of fields; anything else is left out. Fares, prices, margins, commissions, load factors, inventory, crew, other passengers, booking references and contact details are never part of an update, and an update that names one is refused. The note for travelers is read by the traveler and every company on the trip, so it cannot include an amount of money, an email address or a phone number.
4. Post update. Sending the same update twice posts it once.

You are not told which other companies received it.

Settings (owner or admin, under Sharing and automation):
- Linked bookings: let travelers link a booking with you to their Turtini trip. You see that booking and the trip's name and dates.
- Post flight status for us automatically: Turtini's flight tracking (Beacon) or Trip Disruption Radar posts delayed, cancelled, gate changed and arrived updates in your name, only on bookings travelers linked to you, marked as reported by flight tracking. Off by default; turning it off stops it at once.
- Your own update types: a name, a key and up to eight fields. Field names that read as internal data are refused. Choose whether companies with a later booking receive it, and which fields they see.
- Export audit log: every update you posted, received and acted on, each entry hash-chained to the one before it, with the chain checked as it is exported.