Your PMS is very good at telling you who booked. It has nothing to say about the guests who asked and then went elsewhere. For most operators, that's most of the people who get in touch.
Every one of those conversations has a reason in it. Collected together, they tell you more about demand than any report you already have.
The five usual reasons
When Octo handles an enquiry that doesn't turn into a booking, it records why. The reasons tend to fall into five groups, and each one points to a different fix.
- No availability. Demand you couldn't serve. Worth knowing which dates, and whether a sister property or a waiting list could have caught it.
- Over budget. A pricing signal. Look at which stay lengths and dates it clusters around before touching your rates.
- Under the minimum stay. Guests wanted shorter stays than you allow. In quieter weeks, relaxing the minimum might fill the gaps.
- Wrong location. A marketing question. Are your ads or listings reaching people who want to be somewhere else?
- Went quiet. The easiest win. A timely follow-up brings some of these guests back.
What else every conversation tells you
Beyond the reason, Octo picks up why people are travelling (business, relocation, leisure, contract work) and which extras they ask about, such as parking, late check-out or an extra night. Patterns show up quickly: if several guests ask about parking in one week, it's probably worth adding to your booking flow.
The dashboard on our homepage shows an example month: 412 enquiries, of which 138 booked direct and 274 didn't. The figures are illustrative.
Turning it into action
You don't need a data team. Once a week, look at the reasons and ask three questions:
- Which reason grew this week, and on which dates?
- Is there one rule (a minimum stay, a rate, a policy) that keeps coming up?
- Who went quiet, and should they get a follow-up?
Octo can send that follow-up for you. It's the same teammate that answered the enquiry, so it already knows what the guest wanted.