An unavailable online booking page does not necessarily mean the salon's schedule is unavailable. The receptionist should identify which dependency failed before deciding whether direct phone booking remains possible.
Separate the public booking interface, scheduling API, staff calendar, and payment path. The salon may permit a supported alternative write path, or it may require staff review during the outage. Do not assume that bypassing the website is authorized simply because a calendar is readable.
Define the degraded booking mode
Record which services and actions remain allowed, where pending requests are stored, and who reviews them. The fallback should survive the failed dependency. A callback queue hosted only inside the unavailable system is not a dependable alternative.
Return clear action states to the conversation: confirmed, pending, explicitly rejected, or uncertain. A timeout after submission needs different recovery from a failure before any write occurred.
Work through a fictional Saturday outage
A customer cannot complete an online booking and calls about a cut with a preferred stylist. The salon's scheduling write path is also unavailable. The agent captures service, stylist preference, branch, alternative windows, and a confirmed contact route.
It explains that staff must confirm the appointment. If the customer says they may already have submitted the web form, the request is marked for duplicate reconciliation before another booking is created.
| Outage case | Required outcome |
|---|---|
| Website down, approved backend healthy | Supported booking path may continue |
| Schedule read-only | Preferences captured, no reservation claim |
| Submission outcome unknown | Reconciliation before retry |
| Payment path unavailable | Deposit status remains pending |
| Systems recover | Owned queue reviewed for current intent |
Resume without duplicating customer effort
After recovery, check whether staff or the customer already completed the booking elsewhere. Contact preferences may have changed, and an opening discussed earlier may no longer exist. Do not replay every request as though its original context is still current.
Direct fallback booking reduces disruption when permissions and data remain reliable. Request-only intake is more conservative and creates staff work, but it avoids false commitments when the available information is incomplete.
Track pending request age and unresolved uncertain writes during the incident. Review false booking confirmations when defining what evidence permits the agent to say a visit is booked.
Questions about online booking outages
Can the agent promise the requested time will be held?
Only if a real supported reservation exists. A saved preference is not a hold.
Should customers keep trying the website?
Follow the salon's incident instructions and avoid encouraging repeated submissions that may duplicate bookings.
What should staff receive after recovery?
The original request, preferences, possible prior submissions, attempted actions, current status, and an owner for each unresolved item.