A couple fills in your request form on Sunday evening. They want two weeks in Tanzania next July. They also sent the same form to three other operators. On Tuesday morning, your consultant opens the request and starts on a proposal. By then, another operator has already called them, asked good questions and booked a video call.
The operator who replies first with something useful usually gets the first real conversation. So the answer is simple: reply within hours, make that first reply move the trip forward, and follow up on a fixed rhythm until you get a clear yes or no.
This guide shows how to do that in practice. It covers how fast to reply, how to rank new requests, what to put in a first reply, when to follow up and when to call. It ends with the numbers worth tracking each week.
Why speed matters so much in travel sales
A travel request is a moment of interest. The traveller has just spent time thinking about the trip. They are still at their desk or on their phone. The longer you wait, the more that interest cools or moves to someone else.
Most travellers ask several companies at once. They do this to compare, and that is fair. The first operator to reply sets the frame. They ask the questions, suggest the shape of the trip and become the reference point for everyone who follows.
Speed works when the reply is useful. A fast reply that shows you understood the request gives the traveller a reason to keep talking to you. A quick “thanks, we’ll be in touch” gives them very little.
1. Set a reply time your team can keep
Pick a target and write it down. A good starting point for most tour operators is a personal first reply within two working hours, and the same day for anything that arrives before mid-afternoon.
The exact number matters less than three things:
- Everyone knows it. The target is part of the job, and new staff learn it in week one.
- It covers evenings and weekends. Decide what happens to a request that arrives on Saturday. Someone checks once a day, or Monday morning starts with weekend requests first.
- You measure it. If nobody looks at reply times, they drift. More on that in section 7.
An automatic confirmation email tells the traveller the form worked. The reply clock stops only when a person answers.
2. Rank requests so the best ones get answered first
On a busy Monday, you may have twenty new requests. They differ a lot. Some are ready to book. Some are early dreaming. Some are a poor fit for what you sell.
Answer everyone, but answer the strongest requests first. Use a short scoring guide so the team makes the same call each time.
| Signal | Strong request | Weaker request |
|---|---|---|
| Travel dates | Specific dates or a month | ”Sometime next year” |
| Budget | A number or range that fits your trips | No budget, or far below your prices |
| Group | Named group size and ages | Unclear who is travelling |
| Detail | Mentions places, interests or a past trip | One line with no detail |
| Fit | Destination and style you sell well | Destination you rarely do |
| Source | Referral or returning traveller | Unknown or low-quality channel |
| Contact | Phone number given | Email only |
A simple way to use this: give one point for each strong signal. Five or more points means the request goes to the top of the list today. Two or fewer means it still gets a reply, but a shorter one, perhaps with a link to a ready-made tour.
Ranking also helps when the team is small. It tells the one person on duty where to spend the first hour.
3. Write a first reply that moves the conversation forward
The first reply has one job: get a second message. It should prove you read the request, give a small piece of value and end with one easy question.
Keep it short. Four short paragraphs are usually enough.
- Thank them and repeat back what they asked for. Use their words and details. “Two weeks in Tanzania in July, a safari first and then some beach time.”
- Add one useful insight. Something they did not know and that shows you know the destination. For example, which parks are best in that month, or how long the drive is between two places.
- Suggest a rough shape. A few lines on how the trip could flow. The full proposal comes later.
- Ask one clear question or offer a call. Make it easy to answer. “Would you prefer to fly between parks, or is a longer drive fine if it saves money?”
A long list of ten questions feels like a form. Ask the one question that most changes the trip, then ask the next one in the following message.
Worked example: a first reply that gets an answer
Here is a first reply to the Tanzania couple from the opening. All names and details are fictional.
Hi Sara and Tom,
Thanks for your request. Two weeks in Tanzania in July sounds great: a safari first, then time to relax on the coast.
July is a good month for the northern parks. It’s dry, and the big herds are often moving through the northern Serengeti. That area is far from Arusha, so many travellers fly in one direction to save a long day in the car.
A rough plan could be: Tarangire for two nights, Ngorongoro for two, the northern Serengeti for three, then a short flight to Zanzibar for five nights on the beach.
One question to start: would you like to fly between the parks, or keep costs lower with a longer drive? If it’s easier to talk it through, I’m free for a 15 minute call tomorrow at 10:00 or 16:00.
Best, Nadia
This reply takes about ten minutes to write with a template. It repeats their request, adds one real insight, sketches the trip and ends with a single choice. Sara and Tom now have something to react to.
Use templates, then personalise
Templates save time. Write one first-reply template per destination or trip type, with gaps for the personal parts. The consultant fills in the names, the repeat-back line, one insight and the question. Everything else is ready.
Check templates every few months. Remove anything that no longer matches your prices, suppliers or seasons.
4. Know when to pick up the phone
A call can do in ten minutes what five emails do in a week. It is also the fastest way to understand budget, style and who makes the decision.
Call when:
- The traveller gave a phone number and the request scores high.
- The trip is complex, expensive or for a large group.
- The traveller asks several questions you can only answer with more detail.
- Two emails have gone unanswered and you still have a phone number.
Send a short email first if the traveller did not ask for a call. A message like “I’ll try you this afternoon, or reply with a better time” feels polite and raises the chance they pick up.
After every call, write three lines in the request record: what they want, what they can spend and the next step. The next person who picks up the request can then carry on without asking again.
5. Follow up on a fixed rhythm
Many requests go quiet after the first reply. That is normal. People get busy, travel plans move and partners need to agree. A quiet traveller is often still interested.
Follow-up works best when it runs on a plan. Here is an example rhythm you can adjust. The timings are illustrations, so adjust them to your trips.
| When | Channel | What to send |
|---|---|---|
| Day 0 | Email (and call if strong) | Personal first reply with one question |
| Day 2 | A short note adding one new idea, such as a lodge or activity | |
| Day 5 | Phone or WhatsApp | A quick check-in: “Did my last email reach you?” |
| Day 10 | A sample day from a similar trip, or a photo and short story | |
| Day 20 | A clear question: “Should I keep working on this, or pause it for now?” | |
| Day 45 | A light seasonal note, if they said “later” |
Each follow-up should add something. “Just checking in” with nothing new feels like pressure. A new idea, a useful fact or a simple question gives the traveller a reason to reply.
The day 20 message matters most. A direct question often gets an honest answer. Some travellers say they booked elsewhere. Some say they are still keen and apologise for the delay. Both answers help you plan.
Stop the sequence when the traveller replies
Automated follow-ups are useful only if they stop at the right moment. If the traveller answers, books a call or asks to pause, the sequence must end. Sending “Did you see my email?” after they have already replied looks careless.
6. Send the proposal while interest is high
The first reply gets the conversation going. The proposal is where the trip becomes real. Aim to send a first proposal within 24 hours of having enough information. For many requests, that means the day after the first call or reply.
Version one can be rough around the edges. Send a clear first version, then improve it together with the traveller. A good proposal now is worth more than a perfect one next week.
If you need supplier rates before you can price the trip, tell the traveller when to expect the proposal. “You’ll have it by Thursday noon” sets a clear promise. Then keep it.
7. Measure reply time and offers within 24 hours
You cannot improve what you do not see. Track a few numbers each week and look at them together as a team.
| Measure | How to calculate it | What it tells you |
|---|---|---|
| Median first reply time | The middle value of the time from request to first personal reply | How fast travellers hear from a person |
| Replies within target | Requests answered within your target ÷ all new requests × 100 | Whether the team keeps its promise |
| Offers within 24 hours | Proposals sent within 24 hours of a qualified request ÷ qualified requests × 100 | How quickly interest turns into a real trip plan |
| Reply rate | Requests where the traveller wrote back ÷ all requests × 100 | Whether the first reply works |
| Conversion by source | Bookings ÷ requests, for each channel | Which channels bring buyers |
| Open requests with no next step | Count of active requests without a scheduled follow-up | Where requests are slipping through |
Use the median, the middle value, for reply time. One request left over a holiday weekend can make an average look much worse than it is.
Look for patterns. If Monday reply times are slow, weekend requests are piling up. If one channel has a low reply rate, its travellers may need a different first reply. If offers within 24 hours drop, your team may be waiting too long for supplier rates.
An illustration of what the numbers can show
Here is a made-up example to show how the figures fit together. Every figure is invented for illustration.
A small operator gets 80 requests a month. Last quarter, its median first reply time was 19 hours. Travellers replied to 35 of 80 first messages. After setting a two-hour target and using first-reply templates, the median dropped to 3 hours. Travellers then replied to 48 of 80. The team had more real conversations to work with, using the same marketing spend.
Your numbers will be different. The point is to measure your own starting line, change one thing and check again.
A first-reply checklist
Use this before you hit send on any first reply:
- Sent within our reply target
- Used the traveller’s name and repeated their request in their words
- Added one useful insight about the destination, season or route
- Sketched a rough shape of the trip
- Ended with one clear question or a call offer with two time options
- Logged the request source, score and next follow-up date
- Set the follow-up sequence, so it stops when they reply
Frequently asked questions
How quickly should a tour operator reply to a travel request?
Aim for a personal reply within a few working hours, and on the same day for anything that arrives before mid-afternoon. Pick a target your team can keep every day, including Mondays after a busy weekend. Then measure it, so you know whether you hit it.
What should I write in the first reply?
Repeat the request in the traveller’s words, add one useful insight, suggest a rough plan and end with one question. Keep it short. The goal is a second message from the traveller. The full proposal follows once you know more.
How many times should I follow up with a traveller?
Five or six well-spaced follow-ups over about six weeks is a reasonable plan for most trips. Each message should add something new. End with a direct question about whether to keep going, and respect the answer.
Should I call or email travel requests?
Use both. Email works for the first reply and for sharing ideas. A call is faster for understanding budget, style and who decides. Call strong requests when you have a number, and always after two unanswered emails.
How do I stop requests slipping through the cracks?
Give every request an owner and a next step with a date. Review open requests with no next step once a week. Automate the reminders and follow-ups, so nothing depends on someone’s memory.
Answer faster with OpenVoy
Fast, useful replies are easier when the request, the follow-ups and the proposal live in one place. OpenVoy is an operations system for tour operators, DMCs and travel agencies. Requests from your website and request forms arrive ranked, with the source attached. Follow-up automations run on the rhythm you set and stop when the traveller replies. The itinerary builder turns a first conversation into a live trip page or PDF the same day. Weekly reports show your reply times and offers sent within 24 hours.
If you are comparing tools, see how OpenVoy compares with a general CRM or spreadsheet. Bring last month’s requests and we’ll look at your reply times together.
Book an OpenVoy demo to see how your team could answer every request faster, from the first form to the booked trip.