Bookings · Note 11

Does your Book button say what actually happened?

Define request, confirmation and payment before designing the button.

MACD JournalUpdated 28 / 09 / 26

You tap "Book" on a phone. What happened? Perhaps you sent a request. Perhaps a table or appointment is being held while the business checks the diary. Perhaps the slot is confirmed. Those are different outcomes, and a customer should not have to guess which one applies.

Before designing a button, define the final state. A request can be received, awaiting confirmation, confirmed or paid. A request is not a confirmed booking. A confirmed booking is not proof of payment. If the business needs to check availability by hand, a clear request form may be exactly right. Call it a request and say when the customer can expect an answer.

Keep the form short enough to finish on a phone. Ask for the details needed to handle the service, state which fields are required and show how to fix an error without wiping the valid answers. After submission, give a reference, the current state and the next step. A screen-reader user should receive the same meaningful feedback.

Then test what happens when the straightforward path breaks:

  • The last slot goes while two people are filling the form. Does the page show a real availability check or an unverified promise?
  • A payment fails. Does the customer see "not paid" rather than "confirmed"?
  • The customer taps twice. Can the team see that it is one request, not two bookings?
  • The email confirmation is delayed. Can the customer find the request state elsewhere?

These are design questions and operational questions together. A polished button cannot settle them. The business needs an owner for exceptions, a way to correct a mistaken state and a record of what the customer actually saw.

Try your own Book link on a phone. At the end, can you tell exactly what happened, who acts next and when you will hear back? If not, fix the wording and the handoff before claiming the website takes bookings.

Sources: W3C guidance on form instructions and notifications; GOV.UK confirmation-page pattern.

Want us to test your booking flow? Show us your booking link and we'll tell you what we can review.

Next noteWhat should you ask before paying for a website?→← All notes