Acuity Scheduling vs Wabery: Booking Tool or the API You Build On? (2026)
Acuity is a finished booking product. Wabery is the messaging API you build your own capture layer on, across WhatsApp, Instagram, and Messenger. Here is how the two fit together in 2026.

Acuity Scheduling has been around since 2006. It is reliable, customizable, and trusted by thousands of service businesses. (It is now called Squarespace Scheduling in some places after the acquisition.)
So why are so many teams pairing Acuity with something they build themselves in 2026?
Because the bottleneck is no longer the calendar. Acuity already does calendars beautifully. The bottleneck is everything that happens before a lead ever reaches your booking page: the WhatsApp question, the Instagram DM, the Messenger ping at 11pm. There is no off-the-shelf product that captures that exactly the way your business needs. So you build it, and that is where Wabery comes in.
This is not an "either Acuity or Wabery" post. Wabery is not a booking tool and does not try to replace one. It is the messaging API and platform you build your own capture layer on, then feed qualified leads into the booking tool you already love.
The Core Difference
Acuity Scheduling is a finished scheduling product. Customers land on your booking page, pick a time, fill out a form, pay if needed, and end up on your calendar. You configure it; you do not build it. Acuity is excellent at that job.
Wabery is infrastructure. It gives you a unified channels API for WhatsApp, Instagram, and Messenger, signed event webhooks, native WhatsApp Flows (in-chat forms), automations, a CLI, and an MCP server. With those primitives you build exactly the inbound flow you want: instant replies, in-chat data collection, routing, your own qualification logic, then a hand-off to your Acuity link.
Same destination (a confirmed appointment). Very different categories. Acuity is the thing you buy. Wabery is the thing you build on.
If your lead flow is "click link, pick slot," Acuity on its own is plenty.
If most of your leads message you first and never touch the booking page unless you walk them there, you need a messaging layer in front of Acuity, and you can build it on Wabery in an afternoon.
Quick Comparison
| What it is | Acuity Scheduling | Wabery |
|---|---|---|
| Booking page and calendar | Yes, excellent | No (you keep Acuity for this) |
| Payments and intake forms | Yes | No |
| Staff scheduling and resources | Yes | No |
| Email and SMS reminders | Yes | No |
| Unified WhatsApp / Instagram / Messenger API | No | Yes |
| Signed event webhooks for your code | No | Yes |
| Native WhatsApp Flows (in-chat forms) | No | Yes |
| Automations, CLI, MCP server | No | Yes |
| Build your own qualification / routing logic | No | Yes, in your stack |
| Push leads into your booking page via API | n/a | Yes, you wire it |
Notice there is barely any overlap. That is the point. Acuity owns the calendar. Wabery is the toolkit you build the top of the funnel on.
What Acuity Does Well (and Wabery Does Not Touch)
Let us be clear about Acuity's strengths, because they are real and Wabery does not compete with any of them.
The Booking Page Itself
Acuity's booking page is genuinely good. Customizable, fast, mobile-friendly, integrates with Squarespace natively. If your brand lives on a booking link, Acuity delivers.
Intake Forms and HIPAA
Acuity has excellent conditional intake forms, file uploads, and HIPAA compliance for healthcare. If a client needs to fill out a 15-field questionnaire before arrival, that stays in Acuity.
Payments, Packages, Memberships
Acuity handles deposits, packages, memberships, gift certificates, and recurring appointments. Payments and packages belong in your booking tool.
Reminders
Acuity sends email and SMS reminders and handles the whole appointment lifecycle once a booking exists. Wabery does not manage your calendar.
Where Wabery Slots In
Wabery is not trying to do any of the above. It gives you the primitives to build one step earlier in the funnel, on the messaging surfaces that Acuity has no visibility into.
One API for the DMs Acuity Never Sees
Here is the reality for most service businesses: a chunk of your leads never reach your Acuity page on their own.
"Hey, do you have anything this Saturday?" "How much for a 60-minute massage?" "Do you take walk-ins?"
On WhatsApp, Instagram, and Messenger. At 11pm. On Sunday.
Wabery gives you a single unified API and signed webhook for all three channels, so you do not have to stand up and maintain three separate Meta integrations. One inbound message, one webhook, one place in your code to decide what happens:
app.post("/wabery/webhook", verifySignature, async (req) => {
const { channel, contact, message } = req.body; // channel: whatsapp | instagram | messenger
if (isNewLead(contact)) {
await wabery.flows.send(contact.id, "intake_flow"); // your in-chat form
}
});
In-Chat Data Collection You Build Yourself
You design the WhatsApp Flow: service interest, budget, location, timing, any deal-breakers. The customer fills it out without leaving the chat. The structured answers arrive at your webhook as JSON, and your own code decides whether the lead is a fit before anything touches Acuity.
// Flow submission webhook
const { flow } = req.body;
const score = scoreLead(flow.data); // your rules, your scoring
if (score >= THRESHOLD) {
await scheduler.createLead(flow.data); // push into Acuity via its API
await notify(team, flow.data);
}
No more accepting junk bookings. You wrote the qualification logic, so it does exactly what your business needs.
Routing and Hand-off, On Your Terms
When your logic decides a lead is ready, fire whatever you want: a Slack ping, a CRM record, an automation that sends your Acuity link, or a notification so a human takes over the chat. The booking still happens in Acuity. You just built the step that stops leads from drifting away on the way there.
One Inbox, or Headless, Your Choice
Wabery brings all three channels into a single inbox if you want a UI, or you can run it headless and pipe everything through the API and webhooks into your own tools. CLI and MCP server included, so you can scaffold and test from your terminal or drive it from an AI assistant.
Pricing: You Are Paying for Two Different Things
Acuity Scheduling
| Plan | Price | What it buys you |
|---|---|---|
| Emerging | $20/month | 1 staff, booking page, calendar, reminders |
| Growing | $34/month | 6 staff, remove branding, packages |
| Powerhouse | $61/month | 36 staff, advanced features |
Plus payment processing fees.
Wabery
| Plan | Price | What it buys you |
|---|---|---|
| Pro | $29/month | Unified messaging API, webhooks, WhatsApp Flows, automations, CLI, and MCP server across WhatsApp, Instagram, and Messenger |
Plus any WhatsApp API fees from Meta. (See our WhatsApp API pricing breakdown for details.)
Most teams already pay for Acuity (or Calendly, or Fresha, or Booksy). Wabery sits on top of whichever one you have. You are not replacing your scheduler. You are buying the infrastructure to build the messaging layer the scheduler cannot see, instead of building it on raw Meta APIs yourself.
When Acuity Alone Is Enough
Stick with Acuity on its own if:
- Almost all your leads come from search or your website and go straight to the booking page.
- Your customers prefer filling out forms to messaging.
- Your business barely uses WhatsApp, Instagram DMs, or Messenger for inbound.
- Your follow-up happens over email, not chat.
In those cases there is nothing extra to build.
When to Build on Wabery in Front of Acuity
Build a Wabery layer if:
- You get meaningful inbound volume on WhatsApp, Instagram, or Messenger.
- Leads message you first, then maybe book, and you want code in the loop the moment they do.
- You want every lead to pass your own qualification logic (budget, service, timing) before they take a slot.
- You want one API across channels instead of three separate Meta integrations.
- You would rather ship a custom capture flow in an afternoon than maintain WhatsApp Cloud API plumbing yourself.
The combo is simple: Acuity stays your calendar and booking page; you build your messaging front door on Wabery.
How the Workflow Looks Together
- A lead DMs your Instagram: "Do you have anything Saturday?"
- Your Wabery webhook fires; your code sends a WhatsApp Flow asking service, timing, and location.
- The Flow submission arrives as structured JSON; your scoring logic runs.
- If it is a fit, your code creates the lead in Acuity via its API and notifies the team.
- A teammate sends the Acuity link, or your automation does it.
- The booking happens in Acuity, exactly as it does today.
Acuity does what Acuity does. The capture layer you built on Wabery catches the lead before it ghosts.
The Honest Trade-off
If your pipeline is "search traffic to booking page," Acuity is all you need, with nothing to build.
If your pipeline is "DMs on WhatsApp and Instagram that sometimes turn into bookings," Acuity cannot help with the messy first step, and no finished product captures it the way your business works. Wabery gives you the primitives to build that step yourself, fast.
(Want to see how Wabery compares to other options too? Check our full Acuity alternatives guide and booking software comparison.)
Try Them Together
Acuity has a 7-day trial. Wabery has a free plan with no time limit. Set up both. Keep Acuity as your calendar. Point Wabery at your WhatsApp and Instagram, wire one webhook, and watch where the leads actually come from over the next week.
If most of your bookings start as DMs, you will see the answer on day one, and you will know exactly what to build.
Keep your booking tool. Build the messaging layer that captures leads before they drift away.
Looking at other options too? See our Fresha alternatives, Calendly vs Acuity comparison, or the full booking software comparison for 2026.
Questions or feedback? Reach out anytime