‘Something went wrong’ isn’t enough: error messages that save a booking

A client picks a time, fills in their details, taps confirm — and the screen says "Something went wrong." That client doesn't email you. They close the tab, and you never learn the booking existed. Vague errors are exactly where quiet revenue leaks out of every online booking flow.

Here's the direct answer: a booking error message earns its place only when it does three things at once — it names what actually went wrong, tells the client the one thing to do next, and keeps everything they already typed. "Something went wrong" does none of them. Below is a ready-to-use library of the errors salons hit most, with the wording that loses the booking, the wording that saves it, and what your system should offer next.

The three-part rule for every error message

Every message worth showing follows the same shape. Miss any part and the client stalls.

• Identify. Name the specific problem in plain words, not a code. "That time was just booked" beats "Error 409."
• Instruct. Give one clear next action. Never leave the client guessing what to click.
• Preserve. Never wipe the form. Their name, phone, service and date should still be there when the message appears.

Underneath all three sits one more rule: never blame the client, and always offer a way forward. An error that ends in a dead end is a lost booking; an error that ends in a suggestion is usually a saved one. It's the same thinking behind avoiding the wider most common salon booking mistakes — you remove friction the client would otherwise hit alone.

A library of common booking errors

The slot was just taken

Two people reached for the same 10:00. Someone has to lose it — but they shouldn't lose the whole booking.

• Bad: "Booking failed."
• Good: "Sorry, 10:00 was just booked by someone else. The nearest free times are 10:30, 11:15 and 13:00 — tap one to keep the rest of your details."
• Recovery: show the three closest open slots for the same service and staff, with the form still filled. Solid double-booking prevention keeps this rare, but it will always happen occasionally, so word it kindly.

The phone number looks wrong

• Bad: "Invalid input."
• Good: "That phone number looks incomplete. Add the missing digits, or switch to email and we'll confirm there instead."
• Recovery: highlight only the phone field, keep everything else, and offer an alternative contact method rather than a hard stop.

The payment or deposit failed

• Bad: "Payment error."
• Good: "Your card wasn't charged — the payment didn't go through. Try again, use another card, or hold this slot for 15 minutes and pay on arrival."
• Recovery: confirm no money moved, keep the slot reserved briefly, and offer a fallback. If you take deposits and prepayments, make it clear the appointment isn't lost while they retry.

The session expired

• Bad: "Session timeout."
• Good: "You've been away a while, so we refreshed the available times. Your service and details are saved — just pick a slot again."
• Recovery: reload live availability, but never discard what the client already entered.

This appointment already exists

• Bad: "Duplicate."
• Good: "You already have a booking for this service on the same day at 14:00. Keep it, or change it?"
• Recovery: link straight to the existing appointment and offer self-service rescheduling instead of forcing a second, conflicting booking.

No staff member is available

• Bad: "No availability."
• Good: "No one can take this service at 09:00. The earliest openings are Thursday 11:00 and Friday 15:30 — or pick 'first available' and we'll match you to any free stylist."
• Recovery: offer the nearest real openings and a "first available" option. Sensible booking rules and buffers prevent most impossible requests before they reach this screen.

The service and staff don't match

• Bad: "Invalid selection."
• Good: "Anna doesn't offer balayage. Colour specialists free that day are Petra and Klára — or keep Anna for a cut instead."
• Recovery: explain the mismatch and offer the two nearest valid combinations, never a blank error.

It's outside opening hours

• Bad: "Time not allowed."
• Good: "We're closed at 20:00 on Sundays. The last Sunday slot is 18:00, and we're open until 21:00 on Fridays — want either?"
• Recovery: show the real closing time and the nearest in-hours alternative on the same or next day.

Quick reference table

Why clear errors are also accessible errors

An error that names the problem and suggests the fix isn't only friendlier — it's more usable for everyone, including clients using a screen reader, booking one-handed on a phone, or reading in a second language. YourSalon Research's work on accessible booking and booking friction points the same way: the moments that lose bookings are almost always the moments where the system knows what went wrong but doesn't say it, and knows a way forward but doesn't offer it. You don't need legal jargon or a compliance badge to fix this. You need plain identification and a concrete suggestion, every single time. We won't promise any specific legal standard here — this is about clarity, not paperwork.

Audit your own booking flow

Walk your own booking as a client and deliberately trigger each error. For every message, check:

• It names the specific problem, not a generic "something went wrong."
• It gives exactly one clear next action.
• It keeps every field the client already filled in.
• It offers a real alternative — a nearer slot, another stylist, another contact method.
• It never blames the client for the system's limits.
• The text reads the same in plain language on a phone as on a desktop.

Run this list once, fix the worst offenders, and you'll recover bookings you never knew you were losing. Pair it with SMS and email reminders so the bookings you save actually show up, and let clients fix their own mistakes later through self-service rescheduling. (Disclosure: YourSalon is our booking and salon software; this guide reflects how we think about error messages that recover a booking instead of losing it.)