Latest in AI
Odessia Has Shut Down: How to Check Existing Bookings and Recover Travel Plans
OpenAI's acquisition has closed the travel service, leaving existing users with a more immediate question than what ChatGPT might launch next.
Odessia says OpenAI has acquired it and its travel service is no longer available. If you already have a booking or need an itinerary, the company's published contact is support@odessia.com. Start with that support route and your original confirmations before making replacement reservations.
The practical problem is separating a closed planning interface from the status of an actual trip. A disappearing app tells you very little about whether a hotel has your reservation, whether a flight was ticketed or which cancellation terms apply.
What Odessia has actually confirmed
The official shutdown notice confirms the acquisition, the end of the service and the support address for booking modifications and access to existing travel plans. It does not announce blanket cancellations, automatic refunds or a transfer of customer itineraries into ChatGPT.
That leaves important details unresolved. There is no published support response-time commitment in the notice, and no self-service export procedure described there. Treat those as questions for support rather than filling in the gaps with assumptions about what an acquisition normally means.
Founder Francis Davidson's announcement says he is joining OpenAI to work on travel. The next OpenAI travel product, its availability and its relationship to existing Odessia bookings are separate questions. This announcement does not give customers a migration path to a replacement product.
Check the reservation before paying again
My recommendation is to make a small inventory from the records you already have. Search your email for the original confirmation and payment receipt, then separate booked items from recommendations that were merely part of a proposed itinerary.
For each booked item, record the provider, travel dates, confirmation reference, amount paid and the cancellation deadline shown in the original terms. Keep a local copy of the confirmation so access does not depend on the travel agent's interface remaining available.
Then check the reservation through the provider's official site or published customer-service channel. Ask whether it is confirmed and what changes must go through the original booking agent. Do not pay for the same trip twice just because the planning app has disappeared. If something is missing, establish its status before choosing a replacement.
This is a suggested checking process, not a claim that Odessia has canceled bookings or that every provider can modify them directly. Different reservations can have different servicing arrangements.
Send support a request it can resolve
Use support@odessia.com for the purposes named in the notice: existing bookings, modifications and access to travel plans. Include enough information to identify the trip, but avoid sending payment-card details, passwords or identity documents in an initial email.
For example, a traveler could write: “I booked a hotel for 18–21 November under this reservation reference. Please confirm the reservation status, send my existing itinerary and tell me how to request a date change. My confirmation shows a cancellation deadline of 15 November.” Replace every detail with the actual booking information.
That is more useful than asking whether everything is fine. It gives support a specific record to find and a concrete deadline to address. Preserve the original confirmation and the reply together, particularly if the request changes a date, price or refund condition.
If departure is close, say so explicitly and also contact the provider through its official channel. The shutdown notice does not establish how quickly Odessia will respond, so an unanswered email should not be your only source of confidence before traveling.
The lesson for choosing the next AI travel agent
An AI agent can make planning feel pleasantly continuous: preferences, suggestions and reservations all sit in one conversation. That convenience becomes a weakness when the conversation is the only place a traveler can find the underlying records.
For the next service, look for provider confirmation references, downloadable itineraries and a clear route for post-booking changes. Ask who services a reservation after payment and what happens when the assistant is unavailable. These are useful selection criteria even when the model's recommendations are excellent.
The durable part of an AI travel product should be the trip record and its support process. A better chat interface cannot compensate for uncertainty about where you are staying tomorrow.
I'm Paras. I work at the intersection of AI, engineering and distribution.
I help AI founders explain product changes and customer workflows clearly, including the details that matter after a launch.