A salon booking system quietly dropped three confirmed bookings before he fixed the gap
His pipeline mirrors salon bookings into his own database and feeds the staff calendar, appointment app, reminders and morning briefings. Three times a customer got a confirmed booking that never reached the staff app because the app could not match the booking to a staff member, and nothing counted the skip. The fix was an unassigned bucket plus counting every skipped booking.
How it works
- A booking is confirmed to the customer
- The pipeline mirrors it into his database
- The staff app cannot match it to a staff member
- The booking is skipped silently
- He adds an unassigned bucket and a skip counter
Why it’s worth knowing
The customer was told yes and the staff never knew. The bug was not the drop, it was that nothing anywhere counted it.
Where it’s from
Summarized from a public post on reddit.com. See the original ↗