The fastest way to reduce no-shows is to let your booking system do two things for every booking: take payment when the guest books, and send a reminder before the start with the time and the meeting point. Those two settings deal with the most common reasons guests don't turn up. The other six settings in this guide close most of the remaining gaps.
This guide is written for small businesses that sell time slots, such as tours, classes, workshops and boat trips. For each fix, it shows what to set in your booking system and why it works, and it ends with a no-show policy you can copy.
What counts as a no-show?
A no-show is a guest who has a confirmed booking but doesn't arrive and doesn't cancel. It is different from a cancellation, where the guest tells you in advance and you can sell the place again. A no-show usually costs more than one ticket: the place stays empty, you may have paid for food or materials in advance, and on a small group the host may have waited while everyone else stood around.
Why guests don't show up
Most no-shows come down to a handful of causes:
- Low commitment. A free booking is easy to make and easy to forget.
- Forgetting. An activity booked weeks ago slips off a busy schedule.
- Getting lost. The meeting point was a street name, not a pin on a map.
- Time confusion. Guests travelling across timezones read the start time in their own time.
- Plans changed. The guest wanted to cancel but didn't know how, so they just didn't come.
Each setting below targets one or more of these.
8 booking system settings that reduce no-shows
1. Ask for payment when guests book
Guests who have paid turn up far more reliably, and if they don't, you are still paid for the place. Set your booking system to take payment online when guests book, or let guests choose between paying now and paying on arrival. Keep pay on arrival for markets where card payments are less common, and for groups and regulars you trust.
In TicketPa, this is the "How guests pay" setting on the Payments page: pay on arrival, pay online when booking, or guests choose. Online payment needs a connected Stripe or PayPal account.
2. Send a reminder at the right time
An automatic reminder catches most forgotten bookings. For most activities, 24 hours before the start works well. For early morning starts, the afternoon before is better, and for long trips you might send it two or three days ahead. A reminder is also a gentle prompt for guests who can't come to tell you, which turns a no-show into a cancellation you can resell.
In TicketPa, every confirmed booking gets a reminder email, and you choose how many hours before the start it goes out on the On the day page.
3. Put the meeting point on the ticket
Give guests a map pin, not just an address, plus one line on what to look for: "by the fountain, look for the orange umbrella". It belongs on the ticket and in every email, so the guest finds it when they need it.
In TicketPa, each location has an address, a map link and notes. The ticket shows all three, so guests open the map straight from their phone.
4. Show the start time in local time
Write every time in the activity's local time, and make sure your booking system does the same. Guests often book before they travel, and a phone set to their home timezone can shift a calendar entry by hours.
In TicketPa, time slots follow your location's timezone, including daylight saving changes, so a 10:00 class stays at 10:00 for everyone.
5. Show your cancellation policy before guests book
A simple rule, such as "free cancellation up to 24 hours before, no refund after that", sets expectations and gives you a fair basis for keeping the payment when a guest doesn't come. Show it before the guest pays, not in the small print afterwards.
In TicketPa, you set a cancellation window and a late refund percentage for each activity, and the booking page states the policy in plain words before guests book. Our guide to writing a fair cancellation policy has four templates.
6. Let guests cancel or move their own booking
This sounds backwards, but it works. When cancelling is easy, guests who can't come tell you instead of disappearing, and their places go back on sale. Even better, offer to move them to another time.
In TicketPa, every ticket has a link where guests cancel up to the start time and get the refund your policy allows. While cancelling is still fully refunded, they can also move to another time slot themselves.
7. Check phone numbers when guests book
An email address is not enough on the day. With a working phone number, you can message a late guest five minutes before the start and often save the booking. Your booking system should check the number when the guest books, in any international format, so you don't find out it is wrong when you need it.
TicketPa checks every phone number at checkout and stores it in a format you can call or message from your phone.
8. Ask guests to do something before they arrive
Small steps before the day raise commitment. Signing a waiver online reminds the guest that they have a place booked, and for activities that need a waiver anyway, it also saves time at check-in.
In TicketPa, guests sign your waiver from their ticket before they arrive, and the guest list shows who still needs to sign.
Then measure it: check guests in and mark no-shows
You can't reduce what you don't count. Check guests in on a guest list for every time slot, and mark the guests who never came. After a few weeks, patterns appear: a start time, a day of the week or a booking channel with more empty places. Your no-show rate is the number of no-shows divided by confirmed bookings for the same period. Change one setting at a time and watch the number.
In TicketPa, you check guests in by scanning their QR ticket, and you can mark no-shows by hand or let TicketPa mark them after each time slot ends. Reports show bookings by activity and channel, and the CSV download lets you count no-shows any way you like.
Which settings to start with
| Setting | Effort to set up | Main cause it solves |
|---|---|---|
| Payment when booking | Low, once | Low commitment |
| Reminder before the start | Low, once | Forgetting, time confusion |
| Meeting point on the ticket | Low | Getting lost |
| Local time on every ticket | None if built in | Time confusion |
| Cancellation policy before booking | Low | Plans changed |
| Guests cancel or move themselves | None if built in | Plans changed |
| Phone numbers checked at booking | None if built in | Late or lost guests |
| Waiver before arrival | Medium | Low commitment |
| Check-in and no-show marking | Medium | Finding patterns |
If you only change two things this week, take payment when guests book and turn on an automatic reminder.
A no-show policy you can copy
Adapt this to your own rules and show it on your booking page before checkout:
Free cancellation up to 24 hours before the start time. Cancellations within 24 hours and no-shows are not refunded. You can move your booking to another time from your ticket while cancellation is still free. If you are running late, call or message us on the number in your ticket and we'll do our best to wait or move you to the next time. If we cancel because of weather or safety, you choose a new date or a full refund.
Keep the wording short and friendly. Guests read policies on their phones, usually in a hurry.
How TicketPa helps with no-shows
TicketPa is booking software for businesses that sell time slots, and every setting in this guide is built in. Guests can pay online when they book, get a QR ticket with the meeting point and map link, and receive a reminder at the time you choose. They cancel or move their own booking within your policy, sign waivers before they arrive and are checked in from your phone. You can see every feature, or how it works for tours and classes.
