Choosing a booking system: the questions that matter after the demo

Every booking system demos well. The demo is a person who knows the product perfectly showing you a clean calendar with three fake bookings on it. Nothing in that half hour tells you what the thing is like in month six, when you have four hundred bookings a month, a phone call on hold, a group asking to move to next Saturday, and a report you cannot get to answer a question you asked in a sentence.

So evaluate on the parts nobody demonstrates. Below are the questions worth asking, roughly in the order that operators end up regretting them. Ask them in writing, and ask for the answer to be shown on a screen rather than described.

Who owns your customers

This is the first question because it is the one you cannot fix later. Ask whether you can export your full customer list, with email addresses, at any time, in a file you can open, without asking anyone. Then ask whether the guest's email address is captured for every booking, including bookings that come through any marketplace or widget the system connects to.

A system that holds your customer records hostage is not a booking calendar, it is a landlord. Your email list is the only marketing asset that survives every algorithm change, every platform fee rise and every switch of software, and it only exists if the software you chose lets it exist.

Fees, and who is actually paying them

There are usually three layers: the subscription, the per-booking fee, and the card processing. Ask which of the three you can see line by line on a statement, and whether the system passes any fee to the guest as a separate charge at checkout. A guest-facing booking fee is a real thing in this industry and it changes your conversion rate, so you should be the one deciding whether it exists.

Ask what happens to fees on a refund, a partial refund, a gift voucher redemption and a zero-value booking. Those four cases are where the arithmetic surprises people.

Two clocks that decide your week

The guest's five minutes

• Can a guest book without creating an account? Forced account creation is the most reliable way to lose a booking from someone deciding on their phone at ten at night.
• Private or shared bookings. Can you sell a room privately by default and, separately, sell individual seats into a shared session if you ever want to. Some systems can only do one, and the one they cannot do is the one you will want in two years.
• Waivers. Signed at booking, on arrival, or both. Are minors handled by a guardian signature. Does the signed waiver attach to the booking record so you can find it later without a search party.
• Gift vouchers. Sold as a value or as an experience, redeemable against any slot, partially redeemable, and visible in your accounts as a liability rather than as revenue you already spent.
• Deposits and rescheduling. Can you take a deposit rather than the full amount for a large group. Can a guest move their own booking inside rules you set, and does the system enforce a cutoff so nobody moves a Saturday slot on Saturday morning.

Your staff's five seconds

The staff side gets almost no attention in a demo and is used a hundred times a week. Sit at the desk and time these: taking a phone booking from a person reading you a card number, adding two extra players to a booking that starts in twenty minutes, splitting a group of ten across two rooms, and finding the booking made by someone who only remembers their first name and roughly when they came.

Then ask about the calendar rules, which are the quiet source of most operational pain. Can you set a cleanup buffer per room rather than globally. Can you stop a room being bookable at a time when no staff are rostered. Can a single booking hold two rooms at once. Can you block the whole venue for a private event without deleting anything. If a system cannot express your actual operating rules, your staff will express them manually, forever.

Reporting you can read without a spreadsheet

Ask to see the reports, not a list of report names. The ones that matter are occupancy by day type, revenue per available slot rather than per booking, average group size, booking lead time, and the split between direct and third-party sources. If those need exporting and pivoting every month, you will stop doing it by March.

Can it sell something that is not a room

Most systems are built on one assumption: a resource, a slot, and a group who arrive at your address. That assumption holds until you sell anything else, and then it starts to cost you.

A gift experience, an off-site session at a client's office, a school programme with a rotation, a season pass, a self-paced product with no fixed start time, all of these break a rigid slot-and-room model in some small way. It is worth asking the vendor to show you how they would sell a ticket to something that has no room and no staff attached. Operators who run an outdoor game beside their rooms, as City Sleuth partners do, hit this first: an outdoor route has no capacity ceiling, so a system that insists on a resource with a maximum of six will either fight you or force a workaround that your staff maintain by hand. If a second product is anywhere on your five-year list, ask the question now while you still have leverage.

The true cost of migrating

Switching is not free even when the new subscription is cheaper. Budget honestly for these:

1. The bookings already in the old system. Most operators run both systems in parallel until the last old booking has played, which means two calendars and a rule about which is authoritative. Write that rule down before you start.
2. Outstanding gift vouchers. They can be years old and they are a promise you made. Decide how they are honoured in the new system, and tell your staff, before someone shows up with one.
3. Your links. Every review site, directory listing, partner page, old post and printed card points at a booking URL. Redirect the old ones rather than deleting them, and update your own site and your map listing on day one.
4. Your review history. If the system also collects reviews, ask what happens to the ones you already have. Reviews that live only inside a vendor's platform are borrowed, not owned, which is another argument for pushing your review flow to a profile you control.
5. Staff retraining. A fortnight of slower desk work is normal. Do the switch in your quietest month, not before your busiest weekend.

How to decide

Write your ten questions, in your own words, in one document. Send it to every vendor on your shortlist before any demo, and ask for a screen recording rather than a call for the answers. The vendors who answer plainly, including the answers that are no, are usually the ones who will still be answering plainly when something breaks on a Saturday.

Then pick one, and stop shopping. The cost of a slightly imperfect system is far lower than the cost of migrating twice. If a second product outside your walls is part of the plan you are buying for, raise it early with every vendor on the list. It is also the first thing we check with operators who bring City Sleuth to their city, and the partner overview explains why.