A clinic I work with has been building out its booking system for weeks. Online calendar, deposits, confirmation messages, reminders, follow-ups. Every piece got checked as it was built. Every piece worked.
Then yesterday the owner and I sat down and did something we had not done once: we used it. He took out his phone, booked himself an appointment as if he were a stranger who found the clinic online, and we followed it all the way through to paying and cancelling.
Three hours later we had a list of twenty-four problems.
Why "it works" and "it's good" are different answers
Nothing on that list was broken in the sense of failing. Every message sent. Every payment went through. If you had asked me that morning whether the system worked, I would have said yes, and I would have been right.
But here is what a real customer would have experienced:
- The confirmation email said "your appointment is booked and paid for." They had paid a deposit. The balance was still owed. The sentence was simply false.
- The cancellation policy in that same email was the old policy, not the one the owner had decided on weeks earlier.
- Every message listed the owner's personal mobile number as the clinic's office line.
- The day-before reminder said "need to move it? reply and let us know" — inside the window where moving it is not allowed, and nothing was reading the replies anyway.
- When a client cancelled, absolutely nothing happened. No message, no acknowledgement, no update anywhere. The appointment just quietly vanished.
None of that is a bug. All of it is the business saying something untrue to a paying customer.
What does it actually cost to test your own booking system?
One morning. That is the whole answer.
We did it one step at a time — book, receive, wait for the reminder, mark the session done, get the bill, pay it, get the receipt, cancel, reply by text, call the phone line. After each step we stopped and read what the customer would have in front of them.
The rule we followed was simple: do not fix anything until the run is finished. Write the problem down and keep going. Stopping to fix things mid-test means you end up testing three different versions of the system and trusting none of the results.
By lunchtime the list was complete. By that evening, every item on it that mattered was fixed.
The question three weeks of discussion could not answer
There was one thing nobody knew. When the practitioner marks a client as "seen" from the phone app, does the system actually notice and send the bill?
We had gone back and forth on this. We had theories. We had a fallback plan for if the answer was no.
The test answered it in two minutes. Yes — he tapped it on his phone, and the balance request with a tip option landed by text and email before we had finished talking about it. He paid it with a test card. The receipt came back correct, tip included.
Three weeks of guessing, settled by one booking. That is the part I keep thinking about. The uncertainty was not hard to resolve. It was just never resolved, because resolving it meant doing the unglamorous thing instead of the clever thing.
How to run this on your own business
You do not need a system as complicated as a clinic's to get value from this. If you take bookings, orders, enquiries or payments through anything automated, the same exercise applies.
Use a different phone and a fake name
Not your admin login. Not a preview link. The actual public page, from a device that knows nothing about you, with a name you will recognise later so you can delete the record afterwards.
Go all the way to the end
Most people stop at "the booking came through." The booking is the easy part. The confirmation email, the reminder, the receipt, the cancellation — that is where the untrue sentences live, because nobody ever reads them after the day they were written.
Read every message as a stranger would
Not "is this the message we wrote." Ask: if I had never met this business, what would I think? A personal mobile number reads as unprofessional. A wrong policy reads as a trap. Silence after a cancellation reads as being ignored.
Do the unhappy paths too
Cancel something. Reply to a text. Ring the phone number listed at the bottom of the email. Submit the contact form. Those paths get built once and tested never, and they are exactly the moments a customer is already slightly annoyed.
The uncomfortable part
Twenty-four problems had been live in that system for weeks. Not hidden — sitting in messages anyone could have opened.
We did not find them because we got smarter. We found them because we finally looked at the business from the outside instead of the inside. Builders check whether the thing they made does what they told it to do. Customers just read what shows up on their phone.
Book your own appointment this week. Order from your own shop. Fill in your own contact form. Then read what comes back, and be honest about what it says.
Everything you find will be something a customer would have found first.