Booking systems

Booking system integrations, and exactly where each one stands

4sk.ai reads and writes a salon's diary through a booking-system adapter. Three are built and demonstrated today: Phorest, Booksy and Square Appointments. Each still needs your own account access before it goes live — Booksy's API is partner-gated and Square requires you to authorise us — and no system is described as connected until those credentials have been validated against it.

How the connection works

The receptionist never talks to a booking system directly. Each provider sits behind an adapter with the same contract: read the treatment or service list, read staff and what each of them does, read genuine availability, then create, move or cancel an appointment and record the result.

That is deliberate. Your salon's rules, the conversation on the phone and the reporting afterwards do not change when the diary behind them changes, and a new provider is a new adapter rather than a rebuild.

Before launch we test the journeys that matter with you on demonstration data, and we only put a line live once the connection behind it has been validated.

  • Availability is read live at the moment the caller asks — it is never cached or guessed.
  • Every booking action records what was requested, what the provider replied and how it ended.
  • Credentials are held server-side and encrypted. They never reach a browser.

Current status by provider

Statuses below mean what they say. “Adapter built and demonstrated” means the code exists and has been exercised in the product. It does not mean your account is connected: that always depends on your salon granting access and those credentials being validated.

  • Phorest — Adapter built and demonstrated. Our Phorest adapter reads services, staff and availability and creates or changes appointments. Your own salon still needs to grant access, and we validate those credentials against Phorest before your line goes live.
  • Booksy* — Adapter built — awaiting provider API access. The Booksy adapter is built to their published partner interface and runs today on demonstration data, so a Booksy salon can see the full journey. Booksy's API is partner-gated, so live reads and writes wait on partner access and your own business granting it. * Additional costs and planning may be required.
  • Square Appointments — Adapter built — awaiting provider API access. The Square adapter is built to their published Bookings, Catalog and Team interfaces and runs today on demonstration data. Going live needs you to authorise us on your Square account, and Square requires an Appointments Plus or Premium plan for booking writes.
  • Another system — Scoped per business. Tell us what you use. We review what its interface allows and tell you honestly what can and cannot be automated before you commit.

If your diary cannot be connected

Plenty of businesses ring us with a diary that has no usable interface, or with a paper book. The receptionist still earns its place: it answers every call in your own words, applies your rules, captures the caller's full name, email address and mobile number, and hands your team a proper message instead of a missed-call notification.

We would rather tell you that before you buy than discover it on a real client's call.

Common questions

Which booking systems have an adapter today?
Phorest, Booksy and Square Appointments. Each adapter reads services, staff and live availability and creates or changes appointments, and each is demonstrated in the product on demonstration data. Your own salon still has to grant access, and we validate those credentials against the provider before your line goes live.
What does Booksy or Square need before we go live?
Booksy's API is partner-gated, so live reads and writes wait on partner access and your own business granting it. Square needs you to authorise us on your Square account, and Square itself requires an Appointments Plus or Premium plan before an application can write bookings on a seller's behalf. Until that is in place and validated, the receptionist answers, applies your rules and takes messages or transfers callers.
What if we use something else, or a paper diary?
Tell us what you use. We review what its interface allows and tell you honestly what can and cannot be automated before you commit. Where a diary cannot be read, the receptionist still answers, applies your rules, takes a full message and transfers callers.
Do you claim to be a partner of these providers?
No. We build to the published interfaces these providers offer. We are not describing any of them as a partner, approved, endorsed or certified supplier.
Does it take card details or deposits?
Never on the call. Where your booking system offers its own hosted deposit payment link, the receptionist explains that instead.

Read next

Not sure your diary will work?

Tell us what you use and we will tell you honestly what can be automated, before you commit to anything.

Book a demonstration