How to respond to travel inquiries

A traveler planning a multi-day trip doesn't email one operator. They email five or six in a single evening — every company whose website survived their first round of scrolling. Then they wait to see who answers, and how.

Whoever sends the first genuinely useful reply frames the whole comparison. Every email that arrives after yours gets read against it: was it faster, was it clearer, did it actually answer the price question or dodge it? That is a strange kind of power, and most operators give it away without noticing.

I ran my own travel company, AlienAdv, and answered its inquiries myself; in the decade since, HopRolls has answered more than 25,000 of them for operators like Kilimanjaro Heroes, a Tanzania trek and safari company. This guide is the system I landed on: what an inquiry really is, what the first reply has to contain, how fast it has to move, and how to make all of it happen without you standing over the inbox.

What an inquiry actually is

Read one cold and an inquiry looks like almost nothing. "Hi, we're interested in climbing Kilimanjaro next June, two people — what are your prices?" Two sentences. No commitment. Easy to answer carelessly, or to leave until after lunch.

But look at what had to happen for those two sentences to exist. Someone decided — seriously enough to act — to spend thousands of dollars and a week or two of their life on the kind of trip you run. They researched destinations, compared operators, read reviews, and then wrote to a company on another continent that they have never met and cannot visit. An inquiry is a moment of maximum intent and minimum trust. They want the trip badly; they don't yet believe in you at all. The first reply has one job: close that gap before someone else does.

Many inquiries won't turn into a booking this week, and that is normal. Travelers may be researching, budgeting, comparing seasons, or waiting for a partner to agree. When I absorbed that, it changed how I read my inbox. A first reply opens a conversation that may continue for months. Written well, it is the email they can return to when the trip becomes real.

The anatomy of a first reply that wins

Every inquiry, however short, is silently asking four questions:

1. Can you do my trip? Their dates, their group size, their route. Confirm the specifics back to them so they know they've been read, not processed.
2. What will it cost? Real numbers for their actual group — not "prices start from", not "it depends".
3. Can I trust you? Proof, worn lightly: how long you've operated, recent reviews, what's genuinely included, no-pressure terms.
4. What happens next? One clear, easy step — not a menu of five.

Most first replies answer one of these, maybe two. The reply that wins answers all four in a single email — not across four emails, and not behind "let's schedule a call to discuss your needs". One email, readable on a phone in a supermarket queue, that leaves the traveler with nothing they still need to ask before they could say yes.

Here is what that looks like in practice. The placeholders are yours to fill; the shape is exactly what we send.

Notice what those 150 words do. The first line confirms their trip back to them — question one. The bullet list answers question two with real per-person prices and gives them a choice instead of a verdict. Trust is woven through rather than announced: a decade of operating, this season's reviews, everything included, dates held without payment. And the next step is one small, reversible action — reply to hold dates — not "fill in our booking form" or "call our office during Tanzanian business hours". Four questions, one email, under a minute to read.

Speed: the part everyone underrates

You can write the perfect reply and still lose because it arrived on Thursday.

Travelers compare in sittings, not weeks. The same evening they wrote to you, they wrote to your competitors, and the shortlist starts forming as soon as the first answers land. If your reply arrives after theirs, it gets read inside a frame someone else built. If it arrives two days later, there may be no reading at all — politely, the traveler has moved on with the operators who showed up.

And the clock is crueler than it looks, because your clients live in other time zones. Someone in Denver plans their honeymoon after dinner; that's the middle of the night in Arusha. A big share of my inquiries have always landed between midnight and 6am local time. If replies only happen when the office opens, every one of those travelers spends their first hours of excitement reading someone else's email.

I won't hand you a statistic about conversion decaying per hour — I don't have a study, and most of the numbers you'll see quoted on this were invented for a slide. What I have is a decade of the same pattern: when we answered within a couple of hours, travelers kept telling us "you were the first to come back to us" — and those conversations closed far more easily, because ours was the reply everything else got compared to.

The standard we hold ourselves to at HopRolls — and the one I first built for my own travel company — is a priced reply within 1–2 hours, around the clock. Not an acknowledgment; a real answer with real numbers. How to actually hit that bar, including what to do before you automate anything, is its own subject — I've gone deep on it in the response-time guide.

Price in the first email? Yes.

The objection I hear most from operators: "If I give a price right away, they'll just shop it around." I understand the fear. I felt it too, for years.

But walk through what actually happens when you withhold the number. The traveler opens five replies. Three contain prices. Yours says "pricing depends on many factors — shall we schedule a call?" You haven't protected your price. You've removed yourself from the comparison. Nobody books a call to extract a number that three of your competitors handed over for free.

The fear gets the situation backwards. Being shopped isn't a risk you can avoid — being shopped is the starting condition. They were always going to compare. The only decision you get to make is whether your trip is on the table when they do. No price means you're the one eliminated.

The craft is in giving price with context instead of as a naked number. A single figure invites exactly one thought: is it bigger or smaller than the others? Options invite a much better question: which of these trips do I want? Quote two or three routes or tiers, each with one line on what makes it different — the extra acclimatization day, the quieter trail, the better camps — and say plainly what's included, because "cheaper" elsewhere often means park fees billed later.

Qualify without interrogating

Not every inquiry deserves the same twenty minutes of your attention — but the inquiry won't tell you which kind it is unless you learn to read the signals.

Buying signals are specifics. Named dates ("the last two weeks of September"). A fixed group ("we're four adults, two of us have trekked before"). Route-level questions ("is Lemosho worth the extra two days over Machame?"). Logistics questions — which airport, visas, vaccinations — are the strongest of all, because people don't research entry requirements for trips they're idly dreaming about. When you see these, the decision is mostly made; your job is to be easy to choose.

Then there are the dreamers: no dates, "someday", "roughly what does something like this cost?". The standard advice is to filter them out fast and spend your energy on hot leads. My advice is the opposite: answer the dreamers generously anyway. Give them a real reply with real prices, even if it's less bespoke. Multi-day trips run on long cycles — people plan a Kilimanjaro climb or a two-week safari a year out, sometimes two. Some of the easiest bookings I've ever taken started as vague inquiries that went quiet for a year and came back with dates and a deposit. The generous answer costs you almost nothing — especially once it's automated — and it's the one they still have when the dream gets a date.

The trick, for both kinds, is qualifying without interrogating. Don't reply to two sentences with a questionnaire. Answer first — fully, as above — then ask one question, the one the signals point to. Named dates? Confirm availability and offer to hold them. No dates? "Which month are you thinking about?" One question gets answered on a phone in thirty seconds. Five questions get postponed forever.

The inquiry form feeds the reply

Everything above gets ten times easier if the inquiry arrives with the right information already in it — and that is decided by your inquiry form, long before you type a word.

A priced first reply needs exactly four things: travel dates (or at least a month), group size, a budget band, and which trip or route they're drawn to. If your form collects those, the reply is nearly mechanical — look up the price, drop in the options, send. If your form is name, email, and an empty message box, then every inquiry begins with a round of clarifying questions, and you've spent your speed advantage before the race started.

But don't overcorrect into a visa application. Every extra field costs you inquiries from real travelers who couldn't be bothered on a phone at 11pm. The form is a conversation starter, not an interrogation: four or five questions a traveler can answer without opening a calendar or a spreadsheet. Ask for budget as bands rather than a number — people who would never type a figure into a box (it feels like showing your cards in a negotiation) will happily tap "mid-range". How the form, your pricing, and the first reply connect into one system is the heart of the Blueprint.

Common mistakes

I've made every one of these. In rough order of damage:

• The wall of text. Eight hundred words on your company's founding story with the four answers buried in paragraph six. If it can't be read on a phone in a minute, it won't be.
• The "we'll get back to you" placeholder. An auto-acknowledgment with no content isn't a reply — it confirms your inbox works and starts the same clock over again. If a machine sends it, make the machine send something useful.
• PDF attachments instead of a link. A brochure PDF is heavy on mobile, wrong the moment your prices change, and silent — you'll never know if it was opened. A personal itinerary page is current, fast, and tells you when they're looking.
• The generic brochure reply. A copy-paste that reflects nothing back — not their dates, not their group, not their route — reads instantly as automated in the bad way. If it doesn't mention their trip, it isn't an answer; it's a flyer.
• Giving up after one email. A slow decision is common. Silence after your reply almost never means "no" — it means busy, comparing, or waiting on payday. A follow-up sequence does the remembering for you; I've published the actual follow-up emails we send, word for word.

Putting it on autopilot

Everything in this guide can be done by hand. I did it by hand for years — priced replies typed at the breakfast table, at midnight, from a tent at 3,900 meters with one bar of signal. The system doesn't require software. It requires discipline at 2am, which is harder.

What eventually changed my operation was making the whole chain run without me: the form collects exactly what pricing needs; the moment it's submitted, an accurate priced reply goes out with the traveler's own dates, group, and route options; the link in it opens a personalized itinerary page instead of a PDF; and if they go quiet, the follow-up sequence keeps the conversation warm. That chain is what HopRolls is — I built it for my own sales desk first and turned it into a product second, because other operators kept asking for it.

If you want to see the chain run — inquiry in, priced reply out — the one-minute demo shows it end to end. And if you'd rather build it by hand first, everything above works exactly the same typed by a human. The system doesn't care who answers the four questions. It only cares that they get answered, fast.