Vuelo Travel

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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. You never see the link or whether it matched, so tell them: if the details match a booking, Vuelo has texted its page to the mobile on it. For anything else they want a person for, use contact_support.

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.

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.