# Import travel and review guests' own bookings

> Load flights and hotel rooms from a travel agency's spreadsheet, fix the rows that need a decision, and clear the review flag on bookings guests added themselves.

- Do first: [Find the event and the people in it](https://www.attend.vip/help/agents/find-your-event.md)
- Attend MCP tools: `travel_import_edge__eventImportTravelFlights`, `travel_import_edge__eventImportTravelLodging`, `travel__listEventTravel`, `travel__markTravelReviewed`, `travel__listAttendeeTravel`, `travel__adminAddTravelFlight`, `travel__adminUpdateTravelFlight`, `travel__adminAddTravelLodging`, `travel__adminAddTravelGround`, `travel__setTravelStatus`, `chat__suggestFlightCohorts`
- Updated: 2026-11-02

Travel is attached to guests who are **already in the event**. Importing never creates guests, so add the guests first. Imports are silent: guests get no email or push.

## Bulk import

Use `travel_import_edge__eventImportTravelFlights` for flights and `travel_import_edge__eventImportTravelLodging` for hotels.

1. **Map the spreadsheet to rows.**
   - **Flights**: one row per passenger per flight leg. Fields:
     - `rowNumber`;
     - `email`, or `firstName`/`lastName`/`fullName` (`SMITH/JOHN MR` is fine);
     - `direction` (`Arriving` or `Departing`), `pnr`, `airlineCode`, `flight` (such as `UA123`);
     - `departDate`, `departTime`, `from`, `to`, `arriveTime` (`06:10+1` means the next day);
     - optional `seat`, `bookingClass`, `ticketNumber`, `status`.
   - **Hotels**: one row per occupant. Fields:
     - `hotel`, `confirmationNumber`, `checkInDate`, `checkOutDate`;
     - optional `roomType`, `bed`, `specialRequests`;
     - `roomShareRef` to group roommates when there's no confirmation number.
   - Set `dateOrder` (`dmy` or `mdy`) when the dates are ambiguous. Send at most 500 rows per call, and keep all of a booking's rows in the same call.
2. **Dry-run** with `dryRun: true`. Each row comes back as one of:
   - `create`, `update` or `unchanged`;
   - `cancel`;
   - `not-a-guest`: no guest with that email or name in this event;
   - `needs-resolution`: the name matches several guests;
   - `invalid`, `duplicate-in-file` or `conflict`.

   The result also lists warnings. `LEGS_REMOVED` means an update would drop flight legs: an update replaces the booking's whole itinerary with the file's legs.
3. **Resolve.** For each `needsResolution` entry, ask the organizer which guest is meant, or skip the row. Pass `resolutions: {<identity>: {action:"link", guestId}}` or `{action:"skip"}`.
4. **Commit** with `dryRun: false`, the same rows and the resolutions. Re-uploading the same file is safe: existing bookings are updated or left alone, never duplicated. Only an explicit `Cancelled` status cancels a booking, and a booking missing from a later file is left untouched.

## The review flag

When a guest adds or edits their own travel, the row is flagged **Needs review**.

1. Call `travel__listEventTravel` for the event's whole travel list. Each row has `enteredBy` (`guest`, `staff` or `import`) and `reviewState`, and `reviewCounts` totals what's still waiting.
2. Check the flagged rows with the organizer, then clear them with `travel__markTravelReviewed`, passing `kind` (`flight`, `lodging`, `ground` or `rental`) and up to 500 ids from that list. Dry-run first. This doesn't change the booking itself.

## One-off changes

- **One guest's travel:** `travel__listAttendeeTravel`.
- **Add or update a booking:** `travel__adminAddTravelFlight`, `travel__adminUpdateTravelFlight`, `travel__adminAddTravelLodging` and `travel__adminAddTravelGround`.
- **Flight or transfer status** (`scheduled`, `delayed`, `departed`, `arrived`, `cancelled`): `travel__setTravelStatus`.
- **Arrival groups for transfers or chat:** `chat__suggestFlightCohorts` suggests groups of guests arriving together.

To chase guests who haven't booked yet, use `travel_missing` in [Message people who…](https://www.attend.vip/help/agents/message-people-who.md).
