Short answer: record every inquiry with its channel and source, mark it booked (with the amount) or lost (with the reason) and divide bookings by inquiries for the same period. That number is your inquiry-to-booking conversion rate: if you handled 800 inquiries in a month and 80 became bookings, you converted 10%. To stop depending on a spreadsheet you need three things: a CRM that records every conversation, a way to detect the booking (in your engine or in the chat) and source attribution (ad, own post or direct contact).
Why don't most hotels know how many inquiries turn into bookings?
Because the inquiry and the booking live in different systems and nobody connects them:
- The inquiry is in the chat; the booking is in the PMS. WhatsApp, Instagram and the phone don't tell the PMS that a booking started in a conversation.
- The guest asks on WhatsApp and books days later on the website. To site analytics that booking looks "direct", and the conversation that produced it doesn't count.
- Nobody records the losses. Without the reason (price, availability, no reply) you don't know what to fix.
- Google Analytics measures visits, not conversations. It sees who enters the site or the engine, not what was said in the chat.
What is the inquiry-to-booking conversion rate formula?
Conversion rate = bookings from the period's inquiries ÷ the period's inquiries × 100.
Two decisions make the number reliable:
- Count inquiries, not messages. An inquiry is a new conversation (a guest who writes to you), even if it has 30 messages.
- Look at the bookings from those same inquiries. If the inquiry came in on the 28th and the booking arrived on the 3rd of the next month, it belongs to the inquiry of the 28th. Mixing one month's bookings with another month's inquiries inflates or shrinks the rate.
On that basis, these are the metrics worth tracking together:
| Metric | What it answers | How it's calculated |
| Inquiries | How much demand do I get? | New conversations in the period, by channel |
| Quote rate | Do I give a price to those who ask? | Quoted inquiries ÷ inquiries |
| Close rate | Do those who get a payment link pay? | Confirmed bookings ÷ payment links sent |
| Booking conversion | How many inquiries become bookings? | Bookings from inquiries ÷ inquiries |
| Revenue and average ticket | What is each booking worth? | Sum of amounts and amount ÷ bookings, per currency |
| Loss reasons | Why don't they book? | Lost conversations grouped by reason |
How do you measure it if you have no tools today?
With a shared spreadsheet you can start tomorrow. One row per inquiry, with these columns: date, channel (WhatsApp, Instagram, phone, email), source (ad, post, already knew you), requested dates, whether it was quoted, result (booked, lost, open), amount and loss reason. At month end, filter and apply the formula.
It works at low volume. With dozens of inquiries a day it breaks: nobody fills in the sheet in high season, bookings that arrive days later aren't matched, and the source ends up as "don't know".
How does WeSpeak measure it?
WeSpeak covers all three pieces without spreadsheets. The full walkthrough is in the guide how to measure bookings in WeSpeak; here is the summary:
- The Funnel records every inquiry. Each conversation enters the CRM and the AI moves it through the stages on its own (Interested, Quoted, Booking intent, Booked), filling in the quoted amount and dates. It only marks it lost when the guest explicitly declines ("I already booked elsewhere", "it's too expensive"), and conversations with 7 days of no activity are closed as lost for inactivity.
- The Conversion Pixel or WeSpeak Payments detect the booking. If the guest books in your engine from the assistant's link, the Pixel ties that booking to its conversation, with number, amount and currency, up to 30 days after the click. If the booking is paid inside the chat with WeSpeak Payments, it is recorded end to end. You use one or the other, never both.
- WeSpeak Tracker tells you where each inquiry came from. Tracker assigns each contact to a single source: Advertising (a Meta ad), Own channels (a WeSpeak link in a story, a QR code or an email) or Direct. Connected to your Meta Ads account, it shows which campaign, ad set or ad brought inquiries and bookings. It also reports back to Meta: through the Conversions API (CAPI), WeSpeak tells Meta about every inquiry that came from a click-to-WhatsApp ad and every confirmed booking, with its amount. With that signal, Meta optimizes your campaigns to find guests who book, not just people who click. You don't need a developer: you turn it on once from Tracker.
- The Dashboard and WeSpeak MCP build the reports. The Dashboard shows overall conversion, capture rate and close rate; with WeSpeak MCP you can ask finer questions from Claude or ChatGPT.
Bookings your team closes by phone or on WhatsApp with an advisor also count, as long as they are marked Booked with their amount in the Funnel.
How do you read the numbers to know what to fix?
The rate alone says how much you convert; the stages say where the sale stalls:
- Many inquiries, few quotes: the assistant or the team is missing prices or availability. Check the PMS or engine connection.
- Many payment links, few confirmed bookings: guests reach the payment step and don't finish. Review your payment policies and the methods you offer.
- Losses for "High price": compare your direct rate with the OTAs' and review rate parity.
- Many inactivity closures: conversations die without a reply. Turn on automatic follow-ups and answer at night too (how, in answering your hotel's WhatsApp 24/7).
- A campaign with many inquiries and few bookings: it brings people who don't buy. Tracker shows which ad converts and which only generates questions.
Common mistakes when measuring inquiry conversion
- Counting messages instead of conversations, which sinks the rate.
- Adding different currencies into one total. Each booking counts in the currency it was charged in.
- Counting the same booking twice, once from the engine and once from the chat.
- Treating the Pixel as the total. It's a floor: it doesn't see the guest who switches devices, rejects cookies or books by phone.
- Not recording the sales the team closes outside the chat, which then don't exist in the reports.
Sources
- WeSpeak help center: how to measure bookings, Funnels, Conversion Pixel, WeSpeak Tracker and booking statistics.
Discover the AI assistant for hotels by WeSpeak to increase your direct bookings and cut OTA commissions. See how to get started →
Frequently asked questions
What is a good inquiry-to-booking conversion rate for a hotel?
There is no universal number: it changes with destination, season, channel and type of inquiry. What helps is comparing yourself with yourself, month over month and channel against channel, and looking at the stage where the sale is lost: quote, payment link or payment.
Can I measure inquiries that turn into bookings with Google Analytics?
Only partly. Google Analytics sees visits to the site and the engine, but not WhatsApp, Instagram or phone conversations. To connect the inquiry with the booking you need a CRM that records every conversation and a way to detect the booking, such as the Conversion Pixel or payment inside the chat.
How do I know whether a booking came from a Meta ad?
With WeSpeak Tracker connected to your Meta Ads account: it assigns each inquiry to its campaign, ad set or ad and, with the Pixel or WeSpeak Payments, shows the bookings and revenue each one generated. It doesn't include Google Ads.
Does WeSpeak send bookings to Meta through the Conversions API (CAPI)?
Yes. With Tracker connected and the feature turned on, WeSpeak reports to Meta through CAPI every inquiry that came from a click-to-WhatsApp ad and every confirmed booking with its amount, with no coding on your side. Meta uses that signal to optimize your campaigns toward real bookings.
What about bookings closed by phone?
They count if your team marks them Booked with their amount in the Funnel. With WeSpeak Voice, every call is also recorded, transcribed and linked to the contact.
