Business systems / Checklist
When does a small business need an online booking system?
A customer asks when you are free. You offer two times, one has gone by the time they reply, and another message follows. If that is happening throughout the day, an online booking system is worth considering.
The first job is to decide what a customer can safely book without a conversation. A fixed consultation may be straightforward. A job that needs a site visit, a quote and several people may need a request for approval instead. Both can begin online, with different rules behind them.
I start with the diary and the questions you ask before accepting a booking. Once those are clear, we can set up an existing tool or build something around the way your business works. The customer should be able to book without leaving you another job to untangle.
The signs it is time to add online booking
Look at how appointments reach the diary now. Repeated availability messages, missed enquiries while you are working and bookings written in several places are useful signs that the process needs attention. An online calendar should give the customer a clear next step and leave you with a dependable record.
Check whether the appointment itself has a predictable shape. You need to know its duration, who can deliver it, what equipment or space it uses and how much notice you need. If those decisions change with every enquiry, start with a booking request that a person confirms.
A few common enquiries show why the booking rules matter more than the choice of calendar:
| Type of enquiry | A useful first approach | Rule to settle |
|---|---|---|
| A fixed introductory call | Choose from available appointment slots | Who is available and how long the call lasts |
| A room or piece of equipment | Book a named resource or available capacity | What prevents two customers taking the same resource |
| A job that needs a quote | Request a visit or submit details for review | When the enquiry becomes a confirmed appointment |
Give the first version one clearly defined service
Start with the appointment that is easiest to describe and most frequently needs arranging. Give it a name a customer understands, a duration and a clear explanation of what happens afterwards. Decide which details you need before it can be confirmed.
You could begin with a short consultation and keep larger jobs as enquiries. That gives you a manageable first version: can somebody book it on their phone, and does the appointment arrive in the diary with everything you need?
For shared resources, list every constraint that matters. A free staff member does not mean the meeting room is free, and an available vehicle does not mean somebody is available to hand it over. The system needs to check the resources that the actual booking depends on.
Make availability mean a slot you can actually deliver
An appointment needs room in the real working day. Agree opening hours, staff availability, blocked dates and preparation or travel time. Microsoft Bookings documents service availability, date-specific overrides and buffers around appointments. These are useful requirements to check whichever system you choose.
If a service lasts 30 minutes and you need 15 minutes to get ready for the next customer, reserve 45 minutes in the diary. The appointment can still be described as a 30-minute visit. You need that preparation time to stay free.
Decide which calendar is responsible for availability and how changes travel between systems. Test a booking made on the website, a manual appointment added by a member of staff and a cancellation. Check what happens if the connection is delayed or unavailable, rather than assuming calendar sync will always be instant.
Agree a minimum notice period and how far ahead people can book. Microsoft documents these as scheduling policies. Also test the displayed time zone and an appointment around the UK clock change, particularly if you meet customers outside the UK.
Source: Microsoft: configure service availability; Microsoft: business rules for Bookings appointments
Settle deposits, cancellations and confirmations together
Decide whether the appointment is confirmed immediately, after a person reviews it, or after a required payment succeeds. Show the customer the relevant price, payment step and change rules before they complete the booking. A request acknowledgement should say that the appointment still needs confirmation.
Where a deposit is required, the booking and payment records need an agreed relationship. Test a successful payment, a declined card and a customer who closes the payment page. Decide how long a provisional slot is held and how it becomes available again if the payment is not completed.
Stripe explains that payment-event notifications can be retried, delivered more than once and arrive out of order. The practical requirement is that a repeated notification or refresh must not create a second booking or charge. The person implementing the connection should verify the payment record and handle repeated events safely.
Agree who can reschedule, cancel or authorise a refund, and what the customer is told. Check that a cancellation updates the diary and stops the old reminders. Test the wording of the messages as well as whether they are sent.
Try these bookings before a customer does
Use test records and the payment provider’s test environment where payments are involved. Walk through the complete journey on a phone, including the confirmation and the view your staff will use. The aim is to find mismatches between what the customer believes and what the diary actually contains.
These are the checks I would work through for the features you are launching. If you are starting without deposits or customer rescheduling, leave those options off the public page until they are ready.
- Book an ordinary available slot and check the customer and staff confirmations agree.
- Try to book outside working hours, inside the minimum-notice period and on a blocked date.
- Use two test customers to attempt the last available slot or resource at the same time.
- Add a manual diary appointment and check that it affects website availability as agreed.
- Check preparation time, travel gaps and the displayed time zone.
- Try successful, failed and abandoned test payments if payment is required.
- Refresh or repeat the final step and confirm that only one booking exists.
- Reschedule and cancel, then check the calendar, payment status and remaining reminders.
- Make the calendar connection unavailable and check the fallback message and staff alert.
Choose the software after you know the rules
A straightforward appointment diary may fit an existing tool perfectly well. Shared rooms, equipment or a job that passes between several people can need more thought. I want to try an ordinary booking and an awkward one before recommending what we should build or configure.
Include the ongoing costs in that decision: the software subscription, connected services, messaging, payment fees and support. Agree which accounts belong to your business and who can change availability or pause online booking when something needs attention.
The diary and the messages you send today are a useful brief. They show where the time goes and which decisions the booking page will have to handle.
Launch a small version and watch the working day
Open the first service to a manageable group, with somebody responsible for checking new bookings and helping customers who get stuck. Keep an agreed way to take a booking if the online route is unavailable.
Compare the process with your earlier diary: how much arranging still needs a conversation, how often staff correct a booking, and whether customers complete the journey successfully. Include time spent handling exceptions when deciding whether it has helped.
If customers can book the first service and you are spending less time arranging it, add the next one. Let what happens in the diary guide the next change.
Sources
Checked on 22 October 2026.
- Microsoft: business rules for Bookings appointments
Scheduling policies, notice periods, staff availability and buffers in Microsoft Bookings. Check support for these rules in the system you choose.
- Microsoft: configure service availability
Service availability, date-specific overrides and buffer time in Microsoft Bookings.
- Stripe: receiving and handling payment events
Event retries, duplicate delivery and ordering considerations behind a reliable payment connection. Payment and cancellation rules must be agreed for the individual booking process.
- Flying Penguin: online booking systems
Our existing-tool and bespoke booking service, including calendar connections, payment options and the prototype process.