By Afrikabase Team · Published October 15, 2026
Short answer: Booking inquiries can get lost at four points: when an inquiry is never captured in one place, when nobody clearly owns it, when the reply is slow or incomplete, or when nobody follows up after the first answer. Find the stage that leaks first, then fix the process before you buy software.
A hotel does the hard part. A guest finds the property, likes what they see, and sends a message asking about rooms, rates, or dates. Then nothing visible happens. Maybe the message sat in an inbox nobody checked over the weekend. Maybe two staff members each assumed the other had replied. Maybe a reply went out, the guest asked one more question, and the conversation quietly ended. The guest books somewhere else, and the hotel concludes it needs more visibility.
Sometimes it does. But a hotel that already receives inquiries may be losing part of that demand after it arrives, and that is a different problem with a different fix. This article walks through the four places hotel booking inquiries can get lost, how to tell which one is costing you, and when software helps versus when it only hides the problem.
What counts as a booking inquiry at a hotel?
A booking inquiry is any contact from a potential guest that could lead to a reservation: a question about availability, a request for rates on specific dates, a group or event quote, a question about what is included, or a message asking whether the hotel can accommodate a particular need.
These can arrive by phone, email, a website form, a messaging app, social media, a walk-in, or a message sent through a booking platform. The channel matters less than one question: after the inquiry arrives, what happens next? The first step is to find out how your guests actually contact you rather than assuming it.
Not every contact is a sales inquiry. Existing guest requests, reservation changes, and complaints often arrive through the same channels. This article focuses on the inquiries that could become a booking.
Where do hotel booking inquiries get lost?
Every inquiry travels the same path: it is captured, routed to someone, responded to, and followed up until it reaches an outcome. Each stage is a possible point of failure, not a guaranteed one. Here is what each one can look like in a hotel.
Capture: is every inquiry actually received and recorded?
If inquiries arrive through a phone line, an email inbox, a website form, and one or more messaging or social accounts, there may be no single place where all of them are visible. An inquiry can also fail before anyone sees it: a form that does not submit, an email address that bounces or lands in spam, a call that goes unanswered with no record, or a direct message on an account that is checked once a week.
What you may notice: staff cannot say how many inquiries arrived last week.
A fix to try: choose one place where every inquiry is logged, even if it starts as a shared spreadsheet. Then test your own contact points. Submit your own form, send your own email, and call your own line after hours, and see what happens to each.
Where this may not apply: a small property with one channel and one person handling it may not have a capture problem.
Route: who owns the inquiry?
An inquiry that everyone can see is not the same as an inquiry that someone owns. When responsibility is unclear, an inquiry can sit because each person assumes someone else is handling it. When the process depends on one person, a day off or a busy shift becomes a gap.
What you may notice: two people reply to the same guest, or nobody replies because everyone thought it was covered.
A fix to try: name an owner for each type of inquiry, such as rates and availability, group quotes, and special requests, and name a backup for when that person is away.
Where this may not apply: some hotels win business because the owner replies personally. Keep that where it creates value, but make sure a tracked backup still exists.
Respond: is the first reply timely and complete?
A fast reply that does not answer the question can cost as much as a slow one. If staff have to search for rates, policies, or availability before answering, replies get slower and vary depending on who is on shift. Guests may also have to repeat information they already gave.
What you may notice: replies take very different amounts of time, and guests often come back with the same clarifying questions.
A fix to try: decide what a timely reply means for your property. There is no universal number, and the right standard depends on your channels and staffing. Then write down standard answers to the questions you receive most, so every first reply contains what the guest needs. Our posts on after-hours guest inquiries and repetitive guest questions look at two common causes in more detail.
Follow up: what happens after the first reply?
Many guests need more than one conversation. They compare options, check dates with family, or ask a second question a day later. If follow-up depends on someone remembering, it will be inconsistent. And if nobody reviews the inquiries that did not book, the hotel never learns why.
What you may notice: nobody can say which inquiries are still waiting, and interested guests go quiet without anyone contacting them again.
A fix to try: after the first reply, set a specific next action: who will contact the guest, and by when. Mark each inquiry as open, waiting, booked, or lost so you can see what is actually happening.
Where this may not apply: not every inquiry deserves repeated follow-up. A guest who says they have booked elsewhere should be closed, not chased.
How can a GM tell which stage is leaking?
You do not need new software to find out. Use the table below to match what you are seeing to a quick check you can run this week.
| Stage | What you may notice | A quick check | Likely constraint if confirmed |
|---|---|---|---|
| Capture | Staff cannot say how many inquiries arrived last week, or a guest says they wrote and nobody saw it | Contact your own hotel through every public channel and note where each message lands and who sees it | Inquiries are not reliably recorded in one place |
| Route | Duplicate replies, or inquiries that sit because each person assumes another has them | Pick five recent inquiries and ask who owned each one | No clear owner or backup |
| Respond | Slow or uneven replies, and guests repeating details | Compare arrival time and first-reply time on recent inquiries, and note which needed staff to look something up | Missing standard answers or unclear response responsibility |
| Follow up | Interested guests go quiet and nobody contacts them again | Pull recent inquiries that did not book and check whether anyone followed up | Follow-up depends on memory, not a tracked next action |
If these checks show that inquiries arrive and are handled well, the constraint may be somewhere else, such as visibility. In that case, start with how well your website turns visitors into inquiries, which we cover in How a Hotel Website in Liberia Should Turn Visitors Into Booking Inquiries, and with the balance between direct and third-party bookings in OTAs Are a Distribution Channel, Not a Hotel’s Entire Booking Strategy.
What does a one-week inquiry audit look like?
You can run a small version of this audit yourself. For one week, record every inquiry in one place and note what happened to it.
- List every public contact point: phone numbers, email addresses, forms, and messaging or social accounts.
- For one week, log each inquiry in one place: the date, the channel, what the guest asked, and who handled it.
- Record when the first reply went out, and what, if anything, happened afterward.
- Mark each inquiry as open, waiting, booked, or lost.
- At the end of the week, count where inquiries stalled: not captured, not owned, not answered, or not followed up.
- Fix the stage with the most stalled inquiries first.
Hypothetical example, for illustration only. This is not client data and not a benchmark. Suppose a manager logs 20 inquiries in one week. Four cannot be traced to any reply. Six received a first reply but nothing after it. The other ten were handled to an outcome. In this example, the biggest leak is follow-up, not capture, so more advertising would not fix the most visible loss. The manager would start by assigning next actions after the first reply.
When is software the answer, and when is it not?
Start with the constraint. If not enough inquiries are arriving, that is a visibility problem, and our Generate Demand work focuses on it. If inquiries arrive but are missed, delayed, or weakly followed up, that is a process problem, and software added before the process is understood can simply create one more place for inquiries to get lost. If the process already works but repetitive manual work limits how many inquiries you can handle, that is a capacity problem, and tools such as a CRM, a shared inbox, or automation may then be worth considering.
Whatever you choose, keep the human parts that matter. A guest who wants to speak to a person should be able to, and a good process makes that conversation easier to start, not harder.
Key takeaways
- Hotel booking inquiries can get lost at four stages: capture, route, respond, and follow up.
- Diagnose which stage leaks first before buying tools or spending more on visibility.
- Test your own contact points, name an owner and a backup, set a response standard, and track a next action for every open inquiry.
- Run a one-week audit with a shared log. It costs nothing and shows where inquiries stall.
- Add software only after the process is clear.
See where your inquiries are slipping through
If you want a clearer picture of where inquiries are being missed, delayed, or forgotten in your hotel, take the Customer Inquiry & Follow-Up Assessment. It is a short set of questions, about five minutes, on how your business handles inquiries today. You can also read more about how Afrikabase approaches managing customer inquiries and what it looks like in Hospitality & Tourism.