WhatsApp chatbot for travel agencies: the 3 combined questions that quote in a single exchange

Six data points, three lines, a single exchange. The three questions bundle together what is useless in isolation: departure city and dates with a flexibility margin; who is traveling, with ages and passports; total budget for the group along with the payment method. And they carry one more element, the one that actually makes people reply: inside the message goes a fully filled-in example, so the person copies it and changes their own details instead of drafting a message at eleven at night. In travel that is not tidiness, it is timing: what gets quoted in a single exchange gets quoted on fares that still exist. The exact text is below; you send it from WhatsApp Business, and the day you go past roughly twenty quotes a week it starts to pay off to automate the assembly, never the question.

Six separate questions take three days, and the fare will not wait

The typical thread starts on a Sunday night with a "hi, how much is Cancún for July?". The agent replies on Monday morning asking for the dates. The person answers in the afternoon. On Tuesday you ask how many people are traveling. On Wednesday it turns out there are two kids. On Thursday you find out they are departing from another city. On Friday you ask about the budget, and that is where the conversation dies.

Five days to get what you could have had in two hours. And in between, three things happened that only happen in travel: the airfare you saw on Monday is gone by Thursday, the hotel category you were going to propose has run out of availability for those dates, and that same person messaged two other agencies on Sunday night.

It is not that the client is difficult: six rounds of back-and-forth are six exit doors. At each one someone gets distracted, forgets, or gets an answer first from one of those two other agencies.

The three combined questions, with the filled-in example inside

This is the text. It goes as the first reply to any price inquiry, even the ones that only name a destination and a month.

Hi [name]! Yes, we put together [destination] for those dates.

To give you a real price and not a "from" figure, I need three things. Here is a fully filled-in example: copy it and change your own details.

1. Departure and dates: "We are departing from Córdoba. From 12 to 22 July, 10 nights. We can shift it by up to 3 days either way if it comes out cheaper."

2. Who is traveling, with ages: "2 adults and 2 kids aged 9 and 14. All four with passports valid until 2028."

3. Total budget and payment method: "Up to USD 6,000 in total for the four of us, including airfare, hotel and transfers. We are paying by card in installments."

With those three lines I will send you two concrete options today.

Six data points, three lines, a single exchange. Each question bundles together things that are useless in isolation.

The filled-in example is not politeness: it is what makes people reply

Three things happen when the example goes inside the message, and none of them happen when only the question goes.

It cuts the effort down to copy and edit. Nobody drafts a paragraph on WhatsApp at eleven on a Sunday night. Everybody can replace four words in a text that is already written.

It sets the unit before a misunderstanding appears. "USD 6,000 in total for the four of us" establishes that the number covers the whole group. It is the most expensive disagreement in the industry: the client thinks in total and the agency quotes per person based on double occupancy. When the quote arrives, the reaction is "wow, way too expensive" and there is no way to recover the conversation by explaining the fine print.

It legitimizes flexibility. "We can shift it by up to 3 days" gives permission to say something almost nobody offers on their own, and that is exactly where the price difference sits. A client with a three-day margin lets you search; one with a fixed date leaves you a single fare.

And there is a side effect: the message stops sounding like an interrogation about money and starts sounding like a form. Asking "what budget are you working with?" cold has a predictable answer, which is "send me some options and we will see".

Ages matter more than the number of passengers

Never ask how many people are going. Ask who is traveling, with the ages, because that single piece of information resolves four things at once.

A child under two travels as an infant and pays a different fare. The child rate usually cuts off between ages 11 and 12 depending on the hotel, so a 14-year-old is already an adult as far as the budget goes. Quadruple rooms are scarce across much of Europe and common in the Caribbean, and if you have to open a second room the budget moves more than with any change of airline. And if there are school-age kids, the dates are not negotiable: they are tied to the school break, which is also the most expensive week of the year.

The passport goes on the same line on purpose. Many destinations outside the regional bloc require six months of validity at the time of travel, and it is worth verifying the specific requirement for the destination because it changes. Making the person write a date forces them to get up and find the document. That is when the expired passports show up, the ones still being processed, and the minors traveling with a single parent who need authorization. Finding that out in message one saves three weeks of work on a trip that was never possible.

Ask for the budget as a total, with scope and payment method

Three modifiers that turn a question nobody answers into one almost everybody answers.

As a total, for the group. That is how the client thinks and how the money leaves their account.

With the scope spelled out. "Including airfare, hotel and transfers" is what makes USD 6,000 mean something. Without scope, the same number could be an all inclusive or a bare airfare plus whatever comes up.

With the payment method attached. In the region this is not an administrative detail: USD 6,000 in installments and USD 6,000 by bank transfer are two different trips, with different suppliers and different margins. Tax surcharges on foreign-currency spending change often and vary by country, so verify the one currently in force before promising a final price. Besides, someone who has already thought about how they will pay has stopped daydreaming about the trip and started buying it.

If they still dodge the number, do not push with the open question. Move to three fixed brackets for the whole group and ask for the closest one. Choosing a bracket does not feel like revealing how much you have.

And here is the honest limit of the message: some people will not answer the three lines or pick a bracket. That is not a failure of the text, it is the answer. Someone with neither dates nor a number in mind is browsing, not requesting a quote, and finding that out in message one instead of at the proposal stage is half the value of all this.

What goes in the second message, never in the first

Beach or city, all inclusive or breakfast only, whether they accept layovers or want a direct flight, airline preference, medical insurance, seats, excursions. All of that matters and none of it goes in the first message.

The first one has to be answerable from the couch in ninety seconds. The second one only goes to people who already got through the three lines, and there you do ask in detail, because that person has shown they are seriously shopping for a quote.

The calculation that tells you whether you have a quoting problem or a sales problem

Two numbers you already have, from last month.

A: proposals you actually put together last month, not inquiries that came in. B: how many of those sold.

Multiply A - B by the real time it takes you to build one. Time the next one: searching for airfare, checking availability, assembling the package and writing the proposal usually lands between 25 and 40 minutes, but use your number, not mine. With 40 proposals built, 5 sold and 25 minutes each, that is 35 dead proposals: around 15 hours of the month spent on people who were never going to buy.

The three combined questions do not make you sell more. They make you quote less, which is the opposite of what is usually promised. They filter before the 25 minutes and not after: anyone who does not complete the three lines never enters the proposal queue. In implementations of this kind we usually see that between a quarter and a third of the proposals built should never have been built. It is a typical range stated as such, not the audited result of a client: measure your own A and B over a month.

If you build 8 proposals a month, this calculation will tell you there is no project here. That is the point of doing it.

When a bot is not worth it for a travel agency

• If your sales are corporate or a fixed client base handled by phone. Without a volume of inbound inquiries on WhatsApp there is nothing to automate.
• If you sell high-ticket custom trips, like honeymoons or hand-built safaris, where the relationship is the product. There the bot can only take the intake form, and you already take it well.
• If your fares and departures do not live anywhere you can look them up. If the product lives in two people's heads and in supplier emails, the bot will offer things that do not exist. Sort that out first.
• If the problem is that you are priced above the OTAs and you have not written down what you add. Automating there speeds up how fast people tell you no.

Four clocks that start on their own: the fare, Sunday, the third day and the season

With those cases ruled out, what is left is the one that does apply, and there you send the three-line message yourself, for free, starting today. It holds up to about 20 quote requests a week with one person coordinating. What breaks above that is not the text: it is four clocks that in this industry start running without the agency starting them and without the agency being able to stop them.

The fare window. You quoted on Tuesday, the client replies on Friday, the price no longer exists and you build everything again from scratch. At twenty inquiries a week that is rework; at sixty it is your entire week.

The hours. The peak of travel inquiries is Sunday night, public holidays and the hours when the agency is closed. And that person messaged three agencies in the same sitting: the first reply with real content keeps the conversation.

The follow-up after quoting. Most proposals are not lost on price, they are lost because nobody came back on day three or day ten. With sixty open quotes, nobody sustains that by hand.

Seasonality. Volume is not even: two or three weeks a year concentrate a huge share of the inquiries. You cannot hire someone for a three-week peak, and that is exactly when you lose the best ones.

What simply cannot be done by hand is replying at 23:40 with a real range instead of a "from" price, cross-checking the complete intake form against what is actually available. That is no longer a way of writing: it is an integration.

The Sunday 22:00 test

You do not need to measure for a month to know whether this applies to you. Next Sunday night, open the agency WhatsApp and count two things: how many inquiries came in since Friday at 19:00, and how many of those already have a reply with a number in it —not an "I will send you options tomorrow", not a "from USD 890".

Then find the oldest proposal you still consider open and check what day you built it. If more than seven days have passed, that fare no longer exists: the proposal is alive in your spreadsheet and dead in the operator system, and the day the client says yes you will rebuild the whole thing without charging for that hour.

With those two things you already know which side you are on. Four inquiries over the weekend and all four with a price: your problem is not speed, it is something else, and a bot does not touch it. Thirty inquiries and half of them waiting until Monday: the sale did not get away because of the discount you did not give, it got away in the hours when the agency was closed and the person kept scrolling.

If those two numbers came out ugly, info@striqtech.com. If they came out fine, save them and count them again in the peak week, which is when this really breaks.