Scheduling and booking
Classes and appointments, booked by phone.
Members call to grab a class or an appointment. The agent reads your schedule, finds a spot and books it where your Mindbody account allows. Our team connects it during the build.
What members ask. Mostly about tonight's schedule.
Front-desk calls are about what is on, what is full and who is teaching. The agent answers from your live schedule and your own policies.
- “Is there a spin class tonight?”The schedule, read live
- “Can I book a massage with Ana?”An appointment with the right person
- “The class is full. Can I get on the list?”The waitlist, when your build includes it
- “What are your hours?”Answers from your knowledge base
What the agent can do. Once it is connected to Mindbody.
Each of these is set up for your site during the build. Which ones you get depends on what Mindbody's API allows for your account.
Reads the schedule
Classes, appointment times and staff, read from Mindbody during the call.
Books classes and appointments
Read back to the member and booked once they agree, where the API allows.
Waitlists
When a class is full, the agent adds the caller to the waitlist if your build includes it, or passes the request to your front desk.
Reminder calls
A call a day or two ahead to confirm or take a new preferred time, placed through our Voice API from your Mindbody bookings, with the result posted back to you.
Win-back calls
Calls to members who haven't booked in a while, placed through our Voice API from a list your system sends.
Logs every call
A signed event after each call carries the call record, ready to note on the member's record in Mindbody. The outcome and summary are on the call once it is evaluated.
How it connects. Built by our team, for your account.
There is no ready-made Mindbody connector to install. During the build, our team connects your agent to Mindbody with the same documented building blocks every agent uses: custom tools and the call webhook.
- 1
Map the calls
We list the calls your team takes and the Mindbody actions each one needs, and check what your Mindbody account lets an outside system do.
- 2
Connect the tools
Each action becomes a custom tool: an HTTPS request to Mindbody's API that the agent makes during the call.
- 3
Report every call
A signed event after each call carries its details and outcome, to log in Mindbody or start your next workflow step.
- 4
Test, then go live
Test calls run against your real Mindbody account before any customer call reaches the agent.
Questions. Straight answers.
Is there a ready-made Mindbody connector?
No. Our ready-made connectors today are Shopify, Wix Bookings and monday.com. Our team connects Mindbody during the build, with custom tools against its API and the signed call.ended webhook. There is no Mindbody app to install.
What do you need from our Mindbody account?
API access for the actions you choose, such as a key or token created in Mindbody. It is kept in the agent's gateway settings, never in its tool file, and each agent gets only the tools set up for it. What your Mindbody plan lets an outside system do decides what the agent can do there, so we check that first.
What happens when the agent can't help?
With the caller's agreement, it passes the request to your team by email with a written summary, so someone can follow up. Every call also ends with a signed event your systems can act on.
Related. Other systems and guides.
Wix Bookings
Real bookings in your Wix calendar, from live availability.
Wix Bookings → Connected by our teamSquare Appointments
Bookings with the right team member, and deposit links.
Square Appointments →Appointment reminder calls
How reminder calls are placed through the Voice API and how the result comes back.
Read the guide →Running Mindbody? Tell us about your calls.
We'll map your front-desk calls, check what your Mindbody account allows, and plan the agent around it.