A8gent
Build guide - Square Appointments

Square Appointments no-show follow-up: the missing message

Square sends reminders and can charge a no-show fee. It does not document a rebooking message afterwards. Here is the Bookings API build that sends one.

A8gent

What you get from this guide

  • What Square handles natively: reminders, confirmation requests and no-show fees
  • The one thing it does not document: a rebooking message after the no-show
  • The NO_SHOW booking status and the booking.updated webhook, from Square's developer docs
  • The Appointments Plus or Premium gate on seller-level API access
  • A two-touch rebooking sequence with a daily sweep so nothing is missed

What Square already does

Square Appointments covers the period before the appointment well, and you should set that up before touching an API. Its help article on booking notifications and reminders explains that clients can receive confirmation requests, reminders and notifications by text, email or both, managed from Appointments, Settings, Communications in Square Dashboard. If a client has not confirmed by the time a reminder is due, the confirmation request is resent with the reminder.

For the appointment itself, the article on cancellation and prepayment policies describes holding a card and charging it if the client does not show or cancels outside your window, as a flat fee per appointment, a fee per service, or a percentage of each service price. That article lists Appointments Plus and Premium subscribers among its audience.

Prevention first

A reminder that stops a no-show is worth more than any message that tries to recover one. If reminders and confirmation requests are not switched on yet, do that today and measure for a month before you build anything.

The gap: after the no-show

Once the slot has passed and a team member marks the booking as a no-show, the documented tools are about the fee. What is not described is a message to the client that says: we missed you, here is how to rebook. In a busy salon or studio that message is the first thing to be forgotten, because the person who would send it is already with the next client.

Before, during and after the appointment
MomentSquare featureAutomated today
Days beforeConfirmation request by text or emailYes
Hours beforeReminder by text or emailYes
Missed slotNo-show fee on a held card, Plus and PremiumCharged by your team under your policy
After the missRebooking messageNot documented - this is the build

That is the whole scope. This is not a replacement for anything Square does. It is one or two messages, sent on the back of a status your team already sets.

What the Bookings API exposes

Square's BookingStatus reference lists six statuses: PENDING, CANCELLED_BY_CUSTOMER, CANCELLED_BY_SELLER, DECLINED, ACCEPTED and NO_SHOW. The last is a booking that was accepted and that the seller has since marked as a no-show.

The booking webhooks guide documents two events, booking.created and booking.updated. With seller-level permissions they fire for bookings made or changed through the API, the Square Dashboard or the seller's online booking site. Each notification carries a merchant_id, location_id, type, an event_id you can use for idempotency, and the booking under data.object. Your endpoint has to be a public HTTPS URL that returns a 2xx within 10 seconds.

Two documented limits shape the fallback. Listing bookings is restricted to a start-time range of no more than 31 days, which is fine for a daily sweep. And services with a non-zero no-show fee cannot be booked through the Bookings API, which matters if you later want the automation to create the rebooking itself rather than send a link.

The plan gate

The Bookings API overview separates two kinds of access. Seller-level permissions give full visibility of the seller's calendar, and every change to a booking is sent to webhooks. Square states that a seller must have a subscription to Appointments Plus or Premium to use this feature. Buyer-level permissions only cover bookings the calling application created.

For a no-show follow-up you need seller-level reads, because the bookings you care about were made by clients and staff in Square, not by your app. For OAuth applications the webhooks guide names the permissions as APPOINTMENTS_READ and APPOINTMENTS_ALL_READ. If you are on the free Appointments plan, confirm what your account returns before planning a build around it.

The build

Written for n8n, using a Webhook node and the HTTP Request node against Square's API. The same shape works on Make.

1

Create the Square application and token

In the Square Developer Console, create an application for your own business. For a single seller you can use that application's access token; for several sellers you need the OAuth flow with the two appointment read permissions.

2

Subscribe to the booking events

Add a webhook subscription for booking.updated and booking.created pointing at your Webhook node. Validate each notification the way Square's webhook documentation describes, respond with a 200 immediately, and store the event_id so a redelivery is ignored.

3

Filter on status

Read data.object.booking.status. Continue only on NO_SHOW. Everything else ends here, apart from booking.created, which you keep for the stop signal in step 6.

4

Add the daily sweep

A Schedule trigger each morning lists bookings whose start time fell in the previous day and keeps those with a NO_SHOW status. Upsert them into the same table by booking id. If the webhook already recorded the booking, nothing changes; if it did not, the sweep catches it.

Daily sweep - yesterday's bookings

GET https://connect.squareup.com/v2/bookings
    ?location_id=<LOCATION_ID>
    &start_at_min=<yesterday 00:00, RFC 3339>
    &start_at_max=<today 00:00, RFC 3339>
Authorization: Bearer <access token>

Keep rows where status == "NO_SHOW"
5

Look up the customer and write the record

The booking carries a customer_id. Fetch the customer for the name, phone and email, then store booking id, customer id, service, missed start time, status = open, step = 0 and next_touch set to the next morning.

6

Wire the stop signals

A booking.created event for the same customer id means they rebooked: stop the record. Stop on any inbound reply and on STOP. Give the front desk a one-click manual stop for the client who rang to apologise.

7

Send two touches, then close

An hourly sweep sends the due touch, after re-checking the status and quiet hours. Touch one the next morning, touch two three days later, then status = closed_no_response. Two is enough. A third message about a missed haircut is nagging.

Message copy

Touch 1 - no fee charged

Hi {first_name}, it is {business}. We missed you
for your {service} yesterday - hope all is okay.
You can pick a new time here: {booking_link}
Reply STOP to opt out.

Touch 1 - fee charged under your policy

Hi {first_name}, it is {business}. We missed you
for your {service} yesterday, so the {fee} no-show
fee in our booking policy has been applied.
We would still love to see you: {booking_link}
Reply STOP to opt out.

Keep the fee line factual. Do not let a model write it freely, because the amount and the policy wording have to match what the client agreed to at booking. For clients who drift away rather than miss a single slot, the salon win-back guide covers the longer game.

Texting rules

These messages leave from your number, not Square's. In the US, a 10-digit number sending automated texts needs A2P 10DLC registration before the first send, and the A2P 10DLC guide walks through it. A client who opted out of Square's texts has not automatically opted out of yours and the reverse is also true, so keep your own opt-out list and respect it everywhere. If you cannot show consent for texting, send the follow-up by email instead.

Testing and measuring it

The behaviour you most need to confirm is in your own account: what happens when a team member marks a real booking as a no-show. Test it there, with a booking for yourself, before any client receives a message.

  1. Create a booking for a test customer record with your own phone and email. After the slot, mark it as a no-show in Square.
  2. Watch for the booking.updated notification. Note whether it arrives and how quickly. This tells you whether the webhook path or the daily sweep will carry most of the load in your account.
  3. Run the daily sweep by hand and confirm it finds the same booking and does not create a second record.
  4. Create a new booking for the same test customer and confirm the open record is stopped.
  5. Reply STOP to the test text and confirm no further message goes out, from this workflow or any other you run.
  6. Mark a late cancellation the way your team normally does and check which status it carries, so you know whether both cases reach the workflow.

That last test matters. Square describes the NO_SHOW status as covering a client who missed the booking or cancelled without enough notice. If your team uses it for both, decide whether both should receive the same message. A client who rang an hour before to cancel does not need to be told they were missed.

Measure three numbers a month: bookings marked as no-shows, how many of those clients booked again within 30 days, and how many replied. Compare the rebooking figure with the months before the build. Keep the fee question separate. A no-show fee recovers money for the slot that was lost. The rebooking message recovers the client. They are different outcomes and one does not replace the other.

Two operational habits keep it working. First, the status is the trigger, so make marking no-shows part of closing the day, not an occasional tidy-up. Second, look at the sweep log weekly. If the sweep is finding bookings the webhook missed, that is fine. If it is finding none for weeks while you know there were no-shows, the status is not being set and the conversation to have is with the team, not with the API.

Where these builds go wrong

  • Building on the free plan with buyer-level access, then finding the app cannot see bookings made in Square.
  • Relying on the webhook alone, with no daily sweep to catch a missed status change.
  • Treating late cancellations and true no-shows the same when your team marks both as NO_SHOW.
  • Sending a breezy rebooking text right after charging a fee, without mentioning the fee.
  • No stop on booking.created, so a client who rebooked that evening is still chased.
  • Responding to the webhook slowly and missing the 10 second window.
  • Texting from an unregistered US number and reading silence as delivery.
  • Staff not marking no-shows at all. The status is the trigger.

More context for appointment businesses is on the salons and gyms and fitness studios pages. The appointment reminders guide covers the two-way confirm and reschedule pattern, and what an automation build costs covers pricing.

Sources checked

FAQ

Does Square Appointments follow up after a no-show?
Square's help centre documents reminders and confirmation requests before the appointment, and a no-show payment policy that lets you charge a held card afterwards. We did not find a documented automatic rebooking message sent after a client is marked as a no-show. That missing message is what this guide builds. Check your own Communications settings first, because Square adds features regularly.
Can the Square API tell me a client was a no-show?
Yes, once a team member marks it. The Bookings API has a NO_SHOW booking status, described as a booking that was once accepted but that the seller has marked as a no-show because the client missed it or cancelled without enough notice. Like every booking system, it records a human decision. It does not detect an empty chair.
Which Square plan do I need for this?
Square's Bookings API overview states that seller-level permissions, which give an application full visibility of the seller's calendar and generate webhooks for every booking, require the seller to have a subscription to Appointments Plus or Premium. With buyer-level permissions an application only sees bookings it created itself, which is no use for following up bookings made in the Square app. The same page describes a readable seller-level permission on the free plan, so test what your account returns before assuming either way.
Does a webhook fire when a booking is marked as a no-show?
Square documents booking.updated as firing when updatable booking properties change through the API, the Square Dashboard or the online booking site. The documentation does not single out the no-show mark by name, so do not rely on it alone. That is why the build includes a once-a-day sweep that lists yesterday's bookings and catches any NO_SHOW status the webhook did not deliver.
Should I charge a no-show fee and send a rebooking text?
You can do both, but the wording has to match. A cheerful rebooking text an hour after a fee was charged reads badly. If you charge, say so plainly in the message and then offer the rebooking link. If you waive it for a first offence, saying that is a strong reason for the client to come back.
Can I send the follow-up from Square's own text number?
Not through this build. Square's webhook documentation notes that notifications are sent to your application but no email or SMS is sent to the customer as a result. Your follow-up goes out from your own email account or messaging provider, which in the US means registering a 10-digit number for A2P 10DLC first.
Is it worth building for a small salon or studio?
Work it out with your own numbers. As an illustrative sum only: 8 no-shows a month at an average ticket of 60 is 480 of lost chair time, and rebooking 3 of them recovers 180. If your no-shows are one or two a month, a manual text from the front desk does the same job for nothing.
What does it cost to have this built?
It is a small workflow: one webhook, one daily sweep, a customer lookup and two messages. The variables are texting registration and whether you want the result written back into Square as a customer note. We quote a fixed price in writing per scoped workflow after a free consult.

Done for you

Want every no-show to get a rebooking message without the front desk remembering?

We build the follow-up on top of the Square Appointments account you already run: the webhook, the daily sweep, the stop signals and registered texting. The audit that scopes it is free.

The consult is free, and you keep whatever we build.

Keep building

The rest of the cluster