Acuity makes clients open a link and book themselves. Fasrad reads “can we move Thursday?”, finds the slot, books it, and replies.
Clients email "can we move Thursday to next week?" — Fasrad checks the calendar, finds a fit, books it, and replies. Acuity makes them open a link and do it themselves.
Acuity does one thing well: it puts a self-serve booking page on the internet. The client lands on it, sees green slots, picks one, fills the intake fields, and you get a calendar event. That covers the client who is already on your site, ready, and willing to drive the form.
But most scheduling never starts that way. It starts in your inbox. "Are you free sometime next week?" "Can we push our 2pm — something came up." "My sister needs the same thing, when can she come in?" Acuity can't read those. They sit in your inbox until you open the calendar, eyeball the gaps, type a reply, and hope nobody else grabbed the slot in the meantime. That's the part Acuity leaves to you, and it's most of the work.
Fasrad is an AI assistant with its own email inbox and a connected Google Calendar. It reads the actual message, understands "Thursday afternoon-ish, not before 1", checks what's open, and books the event — then writes the confirmation back. It also remembers that this client always wants the late slot and that the last appointment ran long. It is not a fancier booking page; it's the assistant who would otherwise be answering those emails.
Where the line falls:
If your bookings come from a polished public page, Acuity is the right tool and you don't need to switch. If your bookings come from messy human conversation, you've been doing Acuity's missing half by hand.
These pages cover the adjacent jobs buyers usually compare before choosing an AI agent.
It gives you an embeddable chat widget (a script tag on your site) where visitors can ask for and book a time conversationally, plus an email address clients can write to. What it does not give you is Acuity's classic visual slot-grid page — the calendar grid with green squares people click. If a clean self-serve grid is the core of how you take bookings, Acuity does that specific thing better. Fasrad's strength is everything that happens in conversation around the booking.
Create, move, and cancel. It works on your live Google Calendar, so a rescheduled appointment updates the real event and re-notifies the guest. It respects buffers and working hours you've described when it picks the new time.
This is a real gap to be honest about. Acuity takes a deposit or full payment and runs structured intake forms inline at booking — Fasrad does not process payments and is not a forms engine. Fasrad can email an intake document, link to your existing payment page, and log answers a client sends back, but if you need payment captured in the booking flow itself, keep Acuity for that step.
You don't have to move everything. Most people keep Acuity for the public self-serve page and add Fasrad on top to handle the email and chat bookings Acuity can't — reschedules, follow-ups, conversational requests. If you do switch fully, connect the same Google Calendar so both read identical availability and run them side by side while you decide.
It books against your live calendar at the moment of confirmation and honors the buffers and hours you set, so it won't place something in an occupied or blocked slot. If Acuity and Fasrad share the same Google Calendar, an Acuity booking instantly becomes a busy block Fasrad sees, and vice versa.
$49/month or $490/year — cancel anytime It's currently in public beta. Note you're not buying a booking-page tool — you're buying an assistant that also reads email, runs a CRM, follows up, drafts outreach, and books, so compare it to Acuity plus the time you spend answering scheduling emails by hand.