Seven parts, none of them optional

A travel agency quote has seven parts, and the order they appear in weighs as much as the content, because the client reads it on a phone, standing up, and decides on the first screen whether to keep reading.

PartWhat it is there forThe most common mistake
What is being quotedSo the client recognises their request in the first lineOpening with the logo, the company name and the tax ID
Dates and number of travellersAvoids the "it was for the 14th, not the 15th" round tripPutting them at the end, in small print
Total price per personThe number they will compare against the other quotesShowing only the group total, or the price before tax
What is included and what is notPrevents the argument on the day of the excursionA "please ask" where there should be a yes or a no
An itinerary, even a short oneTurns a list of services into a tripPasting the supplier's text as is
Cancellation termsThe client buys calmly if they know how to back outA link to a 4-page PDF
Expiry date and how to acceptWithout a date there is no urgency; without a button there is no acceptanceClosing with "let us know if you have any questions"

None of the seven is optional. If one is missing, the client asks about it on WhatsApp, and every question is one more afternoon without closing.

Order matters more than design

The right order for a quote follows the questions the client asks themselves, in the order they ask them: what is it, when, how much, what is included, how do I cancel, how do I accept.

Most templates do the opposite. They open with the agency (logo, address, tax ID, general terms) and end with the only thing the client came for. That is the logic of an invoice, not of a sale.

A simple test: open your last quote on a phone and count how many times you have to swipe before you see the price per person. If it is more than once, the order is backwards.

The price per person gets compared before the brand does

A client who receives three quotes compares the total price per person first, then what that price includes, and only then looks at who sent it, so those two pieces of data have to be impossible to miss.

The price per person has to be the one they will pay, tax included, and with the boarding fee or the park entrance if they apply. A "plus tax" price that later goes up by 21% does not read as a lower price: it reads as a surprise.

What is included is best written with concrete verbs. "Pickup from downtown hotels" says something. "Services as per programme" says nothing and forces a question.

What the Word template is missing

The Word template, exported to PDF and sent over WhatsApp, covers almost every part of the table and fails at a single thing: after sending it, the agency knows nothing more.

It does not know whether the client opened it. It does not know whether they compared it with two others. It does not know whether they accepted it until the client writes back, and when they write back it is often to ask for a change, which means redoing the file, exporting it and sending it again.

There is a second, quieter problem. The PDF does not book anything. When the client says "go ahead", someone has to go into the system (or the spreadsheet) and enter the booking by hand, with the date, the travellers and the pickup that were already written on the quote. That double entry is where the errors on departure day are born.

The path of a quote, from drafting to bookingFive steps in a row: it is built from catalogue products, sent as a link, opened by the client on their phone, accepted with a tap, and the booking is created on its own with its seats and its payment link.1. Builtproducts, dates,travellers, expiry2. Sentas a link, on WhatsAppor by email3. Openedon the phone, with photos,map and itinerary4. Acceptedwith one tap, beforeit expires5. Bookedseats drawn downand payment linkFrom step 1 to step 5 nobody retypes the date, the travellers or the pickup.
A quote that is accepted on the same page does not need anyone to enter the booking afterwards.

Without an expiry date there is no decision

The expiry date of a quote is the date until which the agency commits to holding the price and the seat, and it is the piece of data that closes the most quotes and that the most agencies forget.

Without an expiry date, the client saves it to "look at later" and opens it again in March with January prices. With one, they decide. For a regular excursion, 3 to 7 days is enough. For a package with a hotel in high season, 48 hours, because the room will not wait longer.

On when to send it there is a rule that works: the same day the client asked. A quote that arrives after 48 hours competes with two that arrived after 2.

From quote to booking without retyping

In Viajalo the quote is a web page, not a file: it is built from catalogue products, sent as a link, the client opens it on their phone and accepts it right there, and the booking is born on its own with its seats drawn down and its payment link.

That fixes both failures of the template at once. The agency can see whether the quote was accepted, and when it is, nobody enters anything by hand: the date, the travellers and the pickup the client already saw are the same ones that end up on the booking.

A few details that change the daily work. Templates are saved per agency, for the combinations that repeat every week. Each product goes in its own currency, without inventing an exchange rate. The page comes out in the client's language, with more than 15 available. And every quote carries its own UTM tags, so at month end you can see which channel brings quotes that get accepted and which brings quotes that get looked at and nothing more.

What does not change is the work of thinking through the trip. Choosing which excursion suits a windy Tuesday in Bariloche is still the agency's job. What goes away is the Word file.