Skip to content

Meeting WhatsDo at the California Restaurant Show?

Check if your restaurant is AI-ready
WhatsDo

Square Appointments

Square Appointments, connected for AI agents

The reference integration. Your Square account stays the source of truth, and agents get a verified view of what you actually sell and when you are actually free.

Status
Supported, availability live
Agent can
Read availability today
In closed beta
Create a booking
Agent cannot
Cancel or reschedule
Authorization
Server-side OAuth on your account

The next screen asks for your business and the system you run. Nothing is connected until you approve the permissions inside your own Square account, and you can revoke them there at any time.

Point-of-sale tablet and card reader on a wooden counter
Square runs the counter. WhatsDo reads availability from it today, and writes the booking back on the closed-beta path.
01

What the connector does

WhatsDo reads your Square Appointments setup, publishes a verified subset to external agents, and writes confirmed bookings back into the account your staff works in. The read is live today.

  • 01Imports locations, services, durations, prices, currency and timezone.
  • 02Serves live availability to agents as a read, with no holds and no phantom reservations.
  • 03Writes a confirmed appointment after one explicit confirmation of the exact slot. This runs in closed beta today.
  • 04Returns a booking ID intended to match the Square record, which is what the controlled run verifies.
One booking, end to end
  1. 01The agent asks what is freeOpen slots on the provider's own calendar, with the services, prices and currency the business actually publishes.
  2. 02The agent places the bookingThe exact service, time and price are restated to the customer, who confirms once.
  3. 03The booking landsA normal appointment appears in the calendar the staff already use. Nothing new to learn, nothing to migrate.
  4. 04The agent asks again laterThe same booking identifier maps to the same record, so repeating a request never creates a duplicate.

Availability read: live. Booking write: closed beta against a controlled merchant. Cancellation and reschedule: not available yet

Setup in three steps

The whole flow runs on your own Square account through a server-side authorization. Provider credentials never pass through the browser.

  • 01Register your business and confirm the exact Square account.
  • 02Authorize Square with the permissions needed to read services and availability and to create appointments.
  • 03Review the imported locations, services, prices, currency and timezone before going live.

Supported system review

Tell us what runs your calendar and you get one of three answers: agents can read your availability today, your system is in verification, or there is no path yet and we write to you the day that changes.

Your answer comes by email. Nothing is connected and nothing changes in your account.

Got it. We will answer to the address you gave with where your booking system stands today.

That address did not look complete. Try it once more.

That did not go through. Try again in a moment.

Requests are not being taken on this build.

Before you connect

The connector reflects your Square data exactly. Clean data in, useful agent view out.

  • 01Services have accurate names, durations and prices.
  • 02Business hours and staff availability are current in Square.
  • 03Location timezone and currency are correct.
  • 04You hold the Square account owner or admin role for the authorization.
02

What an agent can and cannot do

Written here so the boundary travels with the capability.

  • 01Can: read verified services and open slots. This is live today.
  • 02Can, in closed beta: create a booking after an explicit confirmation of service, time, timezone and price, against a controlled merchant.
  • 03Cannot: cancel or reschedule an appointment.
  • 04Cannot: take payment on your behalf through the agent path.
  • 05Cannot: modify your services, staff or hours.

How we prove a connection works

The booking write is marked live here once that run has been completed on a connected account and published. Nothing on this page is claimed on the strength of a diagram.

  • 01One confirmed booking written by an external agent and matched to the Square record.
  • 02A repeat of the same request that returns the existing booking and creates no duplicate.
  • 03One deliberate failure showing a stable error and a working recovery path.
  • 04The full evidence set retained: request ID, booking ID, backend, time, amount, currency and manual fallback flag.

Questions we get

Does WhatsDo change anything inside my Square account?+

It creates appointments after an explicit confirmation, and that write is in closed beta today. It does not edit your services, staff, prices or hours.

Do agents see my whole calendar?+

Agents see availability for the services you expose, expressed as open slots. They do not receive your client records.

What if a slot is taken between the read and the write?+

The write fails with a stable error code and the agent is sent back to fresh availability. No partial booking is left behind.

Can an agent cancel a booking it created?+

Not yet. Cancellation and reschedule are handled in Square by you or your client while that path is in development.

How do I disconnect?+

Revoke the WhatsDo authorization in your Square account. Agents immediately lose access to your availability.

Connect the Square account your staff already works in.

Connect business

Nothing changes for your staff, and you can disconnect at any time.

Building an agent? Start here