
Waiting for an opportunity is not the same as having a booking
A last-minute cancellation can open up a useful time slot for someone who needed an appointment. The problem arises when a business notifies several people, they all respond, and no one knows who gets the time slot. A waitlist needs assignment rules, not just a column of phone numbers.
Square's documentation presents waitlists as a way to fill openings caused by cancellations or appointment changes. It is a reference for how the feature works, not a guarantee that it is available on other platforms: https://api.squareup.com/help/us/en/article/7923-waitlist-with-square-appointments. The following process can be adapted for manual management or a compatible tool.
Record preferences that help you make decisions
Record the requested service, its duration, possible dates, and relevant restrictions. Ask whether the person would accept another location or provider if that option is available. Also record which channel they agreed to receive notifications through, without treating that agreement as permission to send unsolicited marketing.
The list should distinguish active requests from those already fulfilled or expired. A request for this week should not trigger notifications indefinitely. Set a review date and explain how the person can remove themselves from the list. Request only the information needed to coordinate the appointment.
Define how each opening is offered
Choose a transparent criterion: request order among compatible people, the service's operational needs, or another stated rule. Avoid promising priority if you will later assign appointments using a different method. Decide how long an offer remains open before moving on to the next person.
For example, a 45-minute session becomes available on Thursday at 5:00 p.m. The team checks who requested that service and can attend at that time. Send an offer with a clear expiration time and explain that the appointment is confirmed only after the specified process is completed. Notifying someone about availability is not the same as making a reservation.
Keep only one valid confirmation
Before confirming, check again that the opening is still available. If several people handle messages, define who can assign it and where that decision is recorded. The schedule must be the final source of truth; an isolated conversation should not create a second booking for the same resource.
When someone accepts, remove or update their waitlist request. Also close offers that are no longer available. If the client does not respond, record a clear outcome, such as offer expired, instead of assuming they declined all future options.
Evaluate the process using real cases
Review how many offered openings were confirmed, how long it took the team to respond, and how often there was confusion about the booking. A long list does not prove the process is working: compatibility and clear confirmation matter.
Start by testing with one service and a few time slots. Document exceptions before automating messages. If you use Onix Board, check which capabilities are available in your configuration and keep the same rules even if some of the follow-up is manual.