Could Your Website Sell the Appointment Someone Just Canceled?

One empty hour, two people who could use it

Imagine a tutor offering private, one-hour pottery lessons. At 10:00 on Tuesday, the 3:00 lesson is canceled. The tutor needs 15 minutes afterward to clean up and has another customer at 4:15. That leaves a specific opening, not a free afternoon that any service can occupy.

A visitor had previously tried to book a private lesson on Tuesday afternoon. Instead of reaching a dead end, they chose to hear about openings that fit that request. The website kept the service, acceptable times and contact permission together. Now there is a relevant person to notify.

This is already possible in established booking products. Square supports appointment waitlists joined through an online booking site or entered by staff. Acuity describes sending a booking link when a canceled or rescheduled appointment matches a waitlist request. A website can provide the clear doorway into those tools; it does not necessarily need a new booking engine. [1] (opens in a new tab) [2] (opens in a new tab)

The opportunity is to remember the person who almost booked, then give them a useful next step when circumstances change. No discount is required for that idea to work, and no software can create demand that was never there.

Offer the lesson, then let the calendar confirm it

For our studio, the offer page would show the private lesson, Tuesday's full date, 3:00–4:00 PM in the studio's local time, location, price and what is included. Someone deciding on short notice should not have to search a second page for the address or discover an extra materials charge at checkout.

The message should say that an opening is available to check, not that the customer has been booked. If several interested people receive it, only the person who completes the required booking steps should get the confirmation. Here is an original example of how those two moments could look:

For a custom implementation, the booking system needs to decide who gets the slot when two people act together. Availability must be checked and the place reserved as one protected operation; two separate checks can both see an empty slot. Do not confirm from a calendar snapshot saved earlier. If checkout temporarily holds a place, define when that hold expires and how a failed payment releases it. These are design requirements to test, not features to assume every provider implements identically.

The other customer deserves a sensible ending too: the page can explain that this opening has gone and offer to keep their request active. It should not leave a payment form looking available, silently replace the requested time, or expose who took the appointment.

Some cancellations should leave an empty space

Change one detail in the story: the tutor canceled because they are ill. There is no available lesson to sell. An integration that reacts to every cancellation by contacting customers would create work the business cannot deliver. Staff need a way to mark an opening as unavailable before notifications go out.

Timing also matters. A 2:50 cancellation does not help a customer who needs 30 minutes to get to a 3:00 lesson. Match the service length, tutor, equipment and preparation time as well as the start time. Set a minimum notice period that fits the operation. Acuity specifically documents a waitlist minimum-hours setting that overrides its general scheduling limit, so check both rather than assuming they match. [2] (opens in a new tab)

People also need a real choice about hearing from you. Explain what the waitlist messages cover, let a request expire or be withdrawn, and keep that permission separate from unrelated promotions. For a custom SMS connection using Twilio, its policy requires prior consent, identification of the sender and a way to withdraw consent. Follow the provider's requirements and the rules applicable to your business; a checkbox alone is not a compliance review. [3] (opens in a new tab)

A text sent is not a text received. Acuity lists unsupported destinations and explicitly says it cannot guarantee every delivery. Keep a permitted human contact option for customers who cannot use the online flow, and make the page readable with a keyboard and on a small screen. Failed notifications should be visible to staff without triggering an endless sequence of repeated messages. [4] (opens in a new tab)

Start with the booking system you already use

As checked on October 20, Square's US help page lists its appointment waitlist for Appointments Plus and Premium, and for Square Plus and Premium with advanced bookings capabilities added. It requires an online booking site and says class waitlists are unavailable. Our example is a private appointment; group workshops need a separate capability check. [1] (opens in a new tab)

Acuity lists waitlists on Standard/Growing and Premium/Powerhouse plans. Its documented customer flow sends a link and allows booking only while the time remains available. Check the features and notification options in your own account before promising a particular customer experience. [2] (opens in a new tab)

This is usually a configuration and website-design question first. Make the waitlist easy to find when the desired service is full, explain what joining means, and connect the return journey to the actual booking page. A bespoke dashboard is unlikely to be the first thing a one-person studio needs.

If the existing tools cannot match several resources or coordinate multiple locations, a custom connection may be justified. Ask the builder to show how cancellations reach the system, how repeated events avoid duplicate messages, and how staff pause the process. The cost is in those connections, testing and maintenance, as well as the visible page.

Compare the extra subscription cost with the cost of building and supporting that connection. Square's US pricing applies paid-plan fees per location and lists payment processing separately. Other providers have their own plan and messaging conditions. Use the current quote for your account rather than treating a waitlist as a free feature everywhere. [5] (opens in a new tab)

Did you recover a lesson—or just move a gap?

Run a small trial for one service before expanding. In an illustrative month, suppose 12 lessons are canceled. Eight have enough notice and a suitable tutor to offer again. Three replacements are booked and attended. Record that as three attended replacements from eight eligible openings, alongside the four cancellations you could not realistically refill.

Now look more closely: one of those three customers moved from a lesson next week, and that later slot stayed empty. You filled today's calendar, but one booking merely changed dates. Under those assumptions, there are two additional attended lessons across the combined period, not three. If the later opening is subsequently filled, update the result rather than counting the same recovery twice.

Keep the trial simple: count eligible openings, completed replacement bookings, attendance, newly created gaps, message costs and staff minutes. Record cancellations and refunds too. Booking value is not profit, and a small before-and-after sample does not prove the waitlist caused every improvement.

A studio with regular unmet demand may find this worthwhile. A business with very few cancellations, little notice or nobody waiting may be better served by a clear booking page and a manual callback list. The best first version gives the right customer a fair chance at a real opening—and gives the owner confidence that the lesson actually fits.