Vuelo Travel

Bookings are made under Vuelo's Booking Terms and Conditions (https://getvuelo.com/uk/legal/terms-of-booking-service/); the Vuelo card and pay page show them. Start booking a Vuelo offer, by the offerId and paymentOption that search_trips returned; call it whenever the traveller asks in the chat to book one. The Vuelo card then shows the traveller a Pay button that opens Vuelo's secure page (Apple Pay, Google Pay or a card), or, where there is no card or they ask for one, Vuelo texts them a secure link; nothing is booked until they pay. Never show a link in the chat, except a passkey approval link Vuelo returns for you to show. Pre-fill: pass everything you already know about the traveller, from this conversation or what you know about the user, so checkout is a single tap with nothing to type: leadTraveller (full name as on their ID, email, date of birth, home postcode), mobile, and for flights each passenger's name, date of birth, title and gender. Never guess or invent any of it; ask only for what Vuelo says is missing, once, in one message. Flights cannot book without each passenger's name and date of birth. To change how an open booking is paid for, use change_payment_option (calling book_trip again with another paymentOption does the same). Do not wait for the traveller to tell you they have paid: pass notify_url to hear the moment they open the link, pay or cancel, or straight after sending the link call get_booking_status with wait_seconds: 50, which answers the moment they pay. Then tell them it is booked, with the reference.

Cancel a Vuelo booking, before or after the traveller confirms. Pass the taskId if it was made in this conversation; from any other conversation, a made booking can be cancelled with its Vuelo reference (VU-...) and the email or mobile it was booked with. Not confirmed yet: it is called off at once, the texted link stops working and nothing was charged. Already booked: call it first with preview: true and tell the traveller what they would get back (refund.amount, summary). If they want to go ahead, call it again without preview. A reservation with nothing paid is cancelled at once. For anything paid, Vuelo texts the traveller a six-digit code and nothing is cancelled until it is given: ask them for it and call again with code (they can also enter it on their booking page). Never guess a code, and never say a paid booking is cancelled until this or get_booking_status says so.

For a flight-and-hotel package from search_trips: every other flight for the same route and dates, each priced as a package with the same stay, with what it costs each traveller more or less than the current flight. The Vuelo card uses this for its Change flight list; call it yourself when the traveller asks for other flights for a package, then book the offerId they choose.

When the traveller wants to pay a different way (for example reserve now instead of paying in full) before they have confirmed. Switches the open booking to that paymentOption; the link already texted stays the same and opens with the new choice, so nothing new is sent. Only an option the trip lists as available.

Send the traveller's request to Vuelo's support team, who will be in touch with them. Use it whenever the traveller wants something done to a Vuelo booking that the other tools cannot do, or wants a person: change dates or names after paying, a refund question, a payment problem, a complaint, anything. It works in any conversation: pass the taskId if the booking was made in this chat; otherwise their Vuelo booking reference (VU-...) and the email or mobile they booked with, or just their email if they have no reference. To cancel a booking made in this chat, use cancel_booking first: it raises the request itself when Vuelo's team has to do it. Write the message in the traveller's words, with what they want and why. Tell them the ticket reference and reply time this returns.

For a traveller who booked with Vuelo before, in another conversation, and wants to see, change, cancel or get help with it: Vuelo texts the booking's own page to the mobile on that booking. On that page they can cancel, add it to their calendar, and contact Vuelo's team. Pass their Vuelo booking reference (VU-...) and the email or mobile they booked with. If they do not have the reference, pass the mobile they booked with alone (with country if it is not written with +): Vuelo texts that number a link to each of its latest bookings. You never see a link or whether anything matched, so tell them: if the details match, Vuelo has texted the mobile on the booking. They can also see every booking on their mobile at Vuelo's bookings page (/bookings on the site their booking links open), with a code texted to it. Never search their email or messages for a reference instead: ask for the mobile. For anything else they want a person for, use contact_support.

When the traveller asks you to check a support request later ("check it later today", "let me know tomorrow"): you cannot come back by yourself, so Vuelo does. Pass the ticket reference (SUP-...), how many hours from now to check (in_hours, 1 to 72; 4 if they just say later today), and the taskId of the booking in this conversation or the email or mobile the request was raised with. At that time Vuelo checks the request and texts the traveller where it stands, with any refund or cancellation; if the team replies sooner, Vuelo texts them then. Tell the traveller when Vuelo will text. Up to three checks a day per request.

For a booking made in another conversation, or through another assistant: where it stands, by its Vuelo reference (VU-...) and the email or mobile it was booked with. Says booked, reserved, cancelled, cancellation_in_progress or not_booked, with the item, dates, number of travellers, amount, free cancellation date, the stay (hotel, area, stars, room, nights, what is included, any tax paid at the hotel, and a public page about the hotel), the date a reservation must be paid by, any requests with Vuelo's team, and its history oldest first (booked or reserved, cancellation_requested, cancelled, refund_sent, request_raised, team_replied, changed with what changed, request_resolved). It never gives names, dates of birth or the booking page: to give the traveller their page, use find_my_booking. If nothing matches, say the details did not match a booking and ask them to check the reference and the email or mobile; never say which was wrong. For a booking made in this conversation, use get_booking_status.

Progress of the newest booking for an offer, or the newest booking of all, for the Vuelo widget.

The current state of a Vuelo booking started with book_trip. Pass wait_seconds (up to 50) straight after the traveller has the link: it answers the moment they open it, pay or cancel, so you can tell them it is booked without being told.

For a flight offer from search_trips, when the traveller asks about luggage or seats, or before book_trip if they want an extra bag: what the fare includes, the extra bags on sale (each with a choice_id, for which passenger by position, which way, its price and the most allowed), and for each flight how many seats can be chosen and their price range. To add bags, pass extras: [{ choice_id, quantity }] to book_trip; the traveller sees them ticked on the booking page and can change them. Seats are chosen by the traveller on the booking page, from the seat map, never here. Bags and seats cannot be added through Vuelo after booking. Prices are as listed now; the booking page shows the total.

Live rooms and prices at ONE hotel the traveller already has in mind, for their dates and number of guests, without searching the whole town. Pass the reference you hold: a Vuelo hotel link (https://…/h/…), an offerId from an earlier Vuelo search, a Vuelo property_id (VHP_…) or a hotel id from a Vuelo search. Use it when the traveller shares a Vuelo hotel link or asks about the same hotel on other dates. The result appears in the Vuelo card. No result means the hotel has nothing for those dates or is not one Vuelo can sell: say so, and offer to search the town. Prices hold for about an hour: book soon after, or check again.

Details, terms, photos and the payment options for one Vuelo offer, repriced live.

Where a request to Vuelo's support team stands: with the team, replied (the reply is in the traveller's email), or resolved. Pass the ticket reference (SUP-...) and either the taskId of the booking in this conversation or the email the traveller gave. Use it when the traveller asks for an update. To add to a request, call contact_support again with the same booking and reason: it joins the same conversation.

For a traveller who wants to manage a booking here, in the chat, and does not have its reference: every booking on the mobile they booked with. Two calls. First pass the mobile alone (with country if it is not written with +): Vuelo texts that number a 6-digit code, and the answer is the same whether or not it has bookings. Ask the traveller for the code, then call again with the same mobile and the code: you get each booking's reference, what it is, its dates, its status (booked, reserved, cancelled, awaiting_payment, payment_link_expired), and the date to pay by or to cancel free by. Show them the list and ask which one. Then use get_booking, cancel_booking or request_change with that reference and this mobile. Never names, dates of birth or booking pages. If the code is not right, ask them to check the text; after five wrong tries, call again without the code for a new one.

A change to a paid booking, which no tool can make directly: a name on a ticket goes through the airline, and new dates or flights are re-booked by Vuelo's team. Sends the change typed, so the team acts on exactly what the traveller wants, and returns a ticket reference and reply time to tell them. Nothing changes until the team does it, so never say it has. kind passenger_details: passenger (position, from 1), field (name, date_of_birth, title or gender) and new_value (a name exactly as on the passport, or YYYY-MM-DD). kind dates: new_from and new_to. kind flight: which (outbound or return) and new_value. kind special_request (a request to the hotel): request (late_check_in, early_check_in, accessibility, cot, connecting_rooms, bed_type, dietary or other), new_value for a time or bed (e.g. 'arriving 23:30', 'twin beds') and notes; the hotel decides, so say it has been asked for, never that it is confirmed. kind room or other: notes. Before paying, use update_travellers or book again instead. By the Vuelo reference (VU-...) and the email or mobile it was booked with.

When the traveller says the secure link has not arrived, or asks for another: Vuelo texts it again, to the same number. The first time it resends the same link; after that, once it has been opened, or once it has expired, Vuelo cancels it and texts a fresh one, and only the newest works. Never pass the link on in the chat yourself. At most three links a booking.

Find hotels, flights and flight-and-hotel packages on Vuelo for a destination, dates and number of travellers, within a budget. The results appear in the Vuelo card, where the traveller compares and books them: do not follow up with a question asking which one they want. Hotels are live; pass origin and destinationAirport (IATA codes) to include flights and packages. Flight fares are live and ticketed at purchase. Pass cabin for premium economy, business or first. Returns prices, photos and the payment options Vuelo offers for each trip. Show payment options exactly as returned and always show the full price. Call it ONCE for what the traveller asked: every call shows another Vuelo card in the chat. Do not run extra searches for other towns, dates or budgets on your own; if the request is broad ("somewhere near London"), pick the best single destination or ask the traveller, and search again only when they ask for something different.

When the traveller asks for a receipt, an invoice or proof of a booking: Vuelo emails it to the email on the booking (never to an address you give), with what was booked, the dates, and the money as it stands: paid, reserved with the date it is due, on a payment plan, or cancelled with its refund. You do not see the receipt. Pass the Vuelo reference (VU-...) and the email or mobile it was booked with, or the taskId of a booking made in this conversation. If the booking has no email, it says so: then use contact_support.

After a booking has started, when the traveller says someone else is paying (a friend, a partner, a parent, their company); if you know before booking, pass payer to book_trip instead. Vuelo sends that person a secure link of their own, by text, email or both. Only when the traveller asks, with the name and the mobile or email they give you: never guess or reuse a number, and confirm it with the traveller first. The payer sees the trip, the price and who asked, never the traveller's own details, and pays in full from their own Vuelo account (no payment plan). The traveller's own link stops working, so the trip cannot be paid twice; the traveller still gets the booking confirmation. The link lasts 24 hours and the price is checked when they pay. Never pass the link on in the chat yourself.

Correct who is travelling on a booking the traveller has not paid for yet: a passenger's name or date of birth (names exactly as on the passport, dates YYYY-MM-DD). Give only what changes, by position: { passenger: 2, name: "Sophie Hougham", dateOfBirth: "1990-04-12" }. What you leave out stays as it was. The link already sent opens with the new names; nothing is resent. Refused once the traveller has paid: names on a ticket are changed with the airline through Vuelo support.