Export the traveler list you already have. Mezze matches names, arrival windows, hotels and flight details — then builds shuttle waves, a rooming handoff for the hotel, and a personal itinerary for each attendee.
Booking produces a confirmation list. Operations needs something else entirely: who lands when, who shares a vehicle, who sleeps where, who eats what, who is in which breakout, and what breaks when one flight moves. Most teams rebuild that by hand in a spreadsheet, every single time.
Paste any list of names and landing times — nothing is uploaded, it runs in your browser.
Open the flight clustering tool Or import a full travel export| Column in your export | What Mezze does with it |
|---|---|
| Traveler / attendee name | Matches to your existing attendee list, or creates the person |
| Flight number | Kept on the attendee record and printed on the manifest |
| Arrival date and time | Groups arrivals into shuttle waves with a curb buffer |
| Departure date and time | Plans the return waves backwards from the earliest flight |
| Airport / terminal | Splits waves by pickup point |
| Hotel / property | Feeds the rooming list and decides each wave's drop-off |
No integration, no API key, no permission needed from your travel provider — you export, you import, you own the data.
Deliberately. Booking platforms monetise the transaction and are good at it; keep the one you have. The operational layer underneath — the part that turns a booking list into a plan people can follow — is what nobody builds, and it is the only thing Mezze does.
Paste the export, and within a minute Mezze tells you who has no arrival time, who has no hotel, which shuttle is over capacity, and which deadline is closest.
Join the offsites waitlist — free See how it works