An AI Receptionist that books, reschedules & cancels appointments — 24/7 — and writes them straight into
Mindbody.
Plugs into your website and phone line. Voice in 30+ languages. Live by tonight, booking customers by tomorrow. No Zapier, no n8n, no code.
Talk to the agent on the left. Watch the booking appear on the right.
This is the same agent shape you'll deploy. Ask it about a haircut on Tuesday, a reschedule, or a cancel — it'll write the appointment straight into the calendar.
FAQ — Mindbody integration.
Does this actually work with my Mindbody site?
Will it create duplicate clients in Mindbody?
Can it route different inquiries to different staff on my team?
Where do the bookings actually live, calendar or Mindbody?
Can it cancel or reschedule a session from a phone call?
What if a caller has two upcoming bookings in Mindbody?
Does it handle timezones correctly?
Does it create memberships or sell intro packs?
AI Receptionist Call or AI Receptionist Web). Your flow decides which welcome series, which intro pack, which contract template, which location workflow. AnyCRM doesn't try to encode policy that will drift out of date the moment your studio configuration changes.How does the conversion tracking work?
What about my existing website booking widget? Does it go through the same pipe?
How is this different from Mindbody's own Messenger[ai]?
How long until it's actually capturing bookings into Mindbody?
Captures the caller as a Mindbody client, books the appointment or class enrollment in the same call, and feeds one unified conversion pipe for your website forms AND your AI Receptionist.
Every caller who lands on the line becomes a Mindbody client with the right home location and a real client record. When they want a session, AnyCRM books it as a native Mindbody appointment on the right staff member's schedule (or as a class visit in the right class) at the right location. AND the same lead event flows through one unified pipe (with the same shape, same source attribution, and same server-side conversion path used by your website forms) so your Mindbody workflows and your Google / Facebook / LinkedIn Ads both stay in sync.
Every caller becomes a Mindbody client, not a stray missed call
The AI Receptionist captures first name, last name, email, mobile phone, and the location they're calling about. Then AnyCRM writes the client into Mindbody with the right home location DURING the call.
Books appointments as native Mindbody appointments on the right staff member's schedule
The appointment lands as a real Mindbody appointment with the right staff member, the right session type, the right location, and a duration that matches the session type. So it shows on the staff member's schedule and on the client's account exactly the way Mindbody expects, and your existing client-confirmation emails, contract assignments, and autopay drafts fire automatically.
Sends the lead event straight to your CRM. You decide what happens next.
AnyCRM does not pretend to know your membership-creation or contract-assignment rules. Every client-create and every booking sends a lead event straight to your CRM (with source: "AI Receptionist Call" or source: "AI Receptionist Web") where YOUR business logic takes over. Trigger the welcome series, assign the contract, offer the intro pack, route to the right location workflow. We set up the receiving end inside your CRM for you during onboarding, tuned to your studio configuration. AnyCRM doesn't get in the way of policy you've already encoded.
One conversion pipe for your website forms AND your AI Receptionist.
Most studios run two completely separate conversion-tracking stacks: one for the website (booking widget, class schedule embeds, page-load pixels) and a totally absent one for the phone and the AI Receptionist. So Google Ads and Facebook Ads only learn from web bookings, the bidding optimises for the wrong audience, attribution is broken, and the high-intent caller who phones at 7pm to book a free intro stays invisible. AnyCRM closes that gap by running BOTH surfaces through a single conversion pipe.
1. Capture
A lead arrives either through your website booking widget / class schedule embed OR through the AI Receptionist on phone / chat. Either way, AnyCRM produces the same clean lead-event shape, tagged at source with either AI Receptionist Call, AI Receptionist Web, or your website's booking-widget identifier. One vocabulary across both surfaces.
2. Deliver to your CRM
AnyCRM sends the lead event straight to your CRM, into the receiving flow we wired up for you at onboarding. Your business logic decides what happens next: which welcome series, which intro pack offer, which contract template, which location workflow, which front-desk channel. You don't have to maintain two sets of rules. Web bookings and AI Receptionist bookings both arrive through the same door.
3. Fire server-side conversion to your ad platforms
The same lead event fires server-side into Google Ads, Facebook Ads, and your analytics platform, using the origin of the domain you registered with AnyCRM. Server-side means the conversion can't be blocked by ad-blockers, doesn't degrade under iOS / Safari tracking restrictions, and lands with full attribution context.
4. Optimise, attribute, report
Because website bookings AND AI Receptionist bookings flow through the same pipe with the same source taxonomy, your Google Ads bid strategy now optimises against real revenue (not just web-widget noise), your Facebook Ads campaigns see the high-intent traffic that picks up the phone, your analytics platform sees a single unified funnel, and attribution stops fragmenting between web and voice.
- Higher ROAS. Ad bidding optimises against actual booked sessions and class enrollments, not against the noisy subset of leads that happen to make it through the widget.
- Lower ad costs. Once Google Ads and Facebook Ads learn what a real intro-pack buyer looks like, they stop spending against lookalikes of low-intent web-widget tyre-kickers.
- Enriched analytics. Every conversation surface (web widget, web chat, phone call, AI Receptionist chat) feeds the same event shape into your analytics, so funnels are complete instead of half-blind.
- Correct attribution. A caller who first saw a Google Ad for your studio, then visited the site, then phoned three days later to book a free intro gets attributed end-to-end. Voice traffic stops being invisible to your marketing stack.
- One source of truth for lead policy. Your CRM's flow owns membership creation, contract assignment, and intro-pack offers. AnyCRM doesn't drift out of date because AnyCRM never tried to own that policy in the first place.
Most competitor AI Receptionists try to maintain rules for when a membership is created, which contract template to apply, which late-cancel policy to fire, and which source tag to use. That approach breaks the moment your studio policy changes, and it ignores the conversion-tracking surface entirely. AnyCRM inverts the responsibility. AnyCRM stays focused on the conversation (capture, dedup, route, book, cancel) and delivers a clean lead event to the two destinations that matter: your CRM (for business logic) and your ad platforms server-side (for conversion optimisation, attribution, and ROAS). This is a custom service baked into the AI Receptionist package. We configure the lead-receiving flow inside your CRM AND the server-side conversion tracking at onboarding, matched to your specific studio configuration, ad mix, and analytics setup.
We'll be candid: as far as we can tell, none of our competitors have thought of this yet. They sell AI Receptionists as a phone-answering product for studios. AnyCRM treats the AI Receptionist as one of two equally weighted entries into a unified lead-event pipe, and that's where the real compounding value sits for a studio running Ads.
For your developer: how this wires into Mindbody
The AI Receptionist asks AnyCRM for availability against the staff on your roster and gets back open slots in the caller's timezone at the right location. No double bookings. Class capacity and waitlist policy are always respected. Every AnyCRM call prevents duplicate clients, resolves the right home location, matches the staff member to the requested session type, writes the appointment so the staff member's schedule and the client's account are both updated atomically, and sends the lead event straight into your CRM tagged with <code>AI Receptionist Call</code> or <code>AI Receptionist Web</code>. The same lead also feeds the AnyCRM Conversion Lift pipeline (covered in the next capability) so your Google, Facebook, and LinkedIn Ads start optimising against the call and chat leads that actually pick up the phone.
{
"invitee_timezone": "America/New_York",
"start_time": "2026-05-15",
"end_time": "2026-05-17",
"event_type_uuid": ["b050bcf6-b5b0-42a8-9359-aba11e711311"],
"multi_day": true,
"include_scheduling_url": false
}
{
"date_range_label": "Friday, May 15, 2026 – Sunday, May 17, 2026",
"event_types": [{
"event_type_uuid": "b050bcf6-b5b0-42a8-9359-aba11e711311",
"total_slots": 15,
"available_times_by_date": {
"Friday, May 15, 2026": [
{ "start_time": "2026-05-15T10:00:00-04:00", "status": "available" },
{ "start_time": "2026-05-15T10:30:00-04:00", "status": "available" },
{ "start_time": "2026-05-15T11:00:00-04:00", "status": "available" }
]
}
}]
}
{
"name": "Jane Doe",
"email": "jane@example.com",
"phone": "+14155551234",
"scheduled_datetime": "2026-05-15T11:00:00",
"invitee_timezone": "America/New_York",
"event_type_uuid": "b050bcf6-b5b0-42a8-9359-aba11e711311",
"questions_and_answers": []
}
{
"event_uuid": "a7c1f4e9-...",
"start_time": "2026-05-15T11:00:00-04:00",
"start_time_utc": "2026-05-15T15:00:00Z",
"invitee_timezone": "America/New_York",
"reschedule_url": "https://...",
"cancel_url": "https://..."
}
Turns every call and chat into a real conversion event your Google, Facebook, and LinkedIn Ads can actually optimise against. So Cost per Lead drops, ROAS goes up, and CAC stops being a guess.
If you run paid Ads on Google, Facebook, or LinkedIn to fill classes, here is the uncomfortable truth: those platforms only get smarter when they see real conversions. Today, a web-widget booking counts. A real phone call from a high-intent buyer asking about your intro-pack at 7pm does NOT count. So Google bids harder on the audience that uses the widget (often the cheaper, lower-intent one) and ignores the audience that actually calls. Cost per Lead looks fine. CAC quietly creeps up. ROAS looks misleading. AnyCRM fixes this. Every call and chat the AI Receptionist handles is sent as a real conversion event to Google Ads, Facebook Ads, AND LinkedIn Ads. The bidding algorithm finally sees what's actually working.
Every phone call and every chat becomes a tracked conversion. Not just web-widget bookings.
Today, Google Ads and Facebook Ads probably think your only conversions are web-widget bookings. That's why your Cost per Lead looks low but your front-desk team complains the leads are weak. The high-intent traffic is calling you to ask about pricing and intro packs instead of clicking through your widget, and the Ad platforms have no idea. AnyCRM sends every call and every chat the AI Receptionist handles into your Ad platforms as a real conversion event. Suddenly Google, Facebook, and LinkedIn can see the FULL picture of who is converting from your Ads.
Lower Cost per Lead. Better ROAS. Smaller CAC.
Once your Ad platforms can see the phone calls and chats as real conversions, they re-train on a better signal. Bidding shifts toward audiences that actually pick up the phone, not just the audience that loves clicking through booking widgets. In practice this means: Cost per Lead drops because you stop overpaying for low-intent web traffic; Return on Ad Spend goes up because the Ads now find people closer to ready-to-buy; and Customer Acquisition Cost shrinks because more of your Ad budget reaches buyers who will actually convert into members.
The same pipe carries your website widget too. One source of truth across Ads, CRM, and Analytics.
AnyCRM doesn't just track AI Receptionist conversions. It also runs your existing website booking widget and class-schedule embed through the same pipeline. So a lead from a Google Ad that books through your widget AND a lead from a Facebook Ad that called the AI Receptionist three days later both end up tagged, attributed, and counted in exactly the same way. Your Ads platform stops double-counting, your analytics stop fragmenting, and your CRM stops being half-blind to where your members actually came from.
- Cost per Lead drops. Because Google, Facebook, and LinkedIn stop wasting your Ad budget on lookalikes of low-intent widget clickers, and start finding the audience that picks up the phone to ask about your intro pack.
- Return on Ad Spend (ROAS) goes up. Because the Ads now optimise toward conversations that actually convert into memberships, not toward whichever cheap audience generates the most widget visits.
- Customer Acquisition Cost (CAC) shrinks. Because a higher share of every Ad dollar reaches buyers ready to walk into your studio.
- Analytics get a complete funnel. Web and voice leads sit side by side, with the same source taxonomy. You stop seeing "50% of new members: unknown source."
- Attribution stops fragmenting. A buyer who first clicked a Google Ad, then called the studio three days later, finally shows up correctly attributed. Today, that buyer is invisible to your Ads stack.
- You finally know if Ads are working. Most studios cannot honestly tell you whether their Google or Facebook spend is profitable. With AnyCRM's Conversion Lift, you can.
Imagine you spend $3,000/month on Google Ads to fill classes at your studio. Today, you see 40 web-widget bookings and assume that's the full picture. With AnyCRM running, you'll also see (say) 55 phone calls and 30 web chats the AI Receptionist handled, all flowing into Google Ads as real conversions. Suddenly Google sees 125 conversions a month instead of 40. It re-trains on that bigger, better signal. Within weeks, the bidding finds you more of the right kind of buyer (the one who phones at 7pm to ask about your intro pack, not just the one who clicks the widget). Same $3,000 spend, more real members, lower Cost per Lead, higher revenue per ad dollar. That is what "AI Receptionist with AnyCRM" actually means for the bottom line. Not just "it answers the phone."
For your developer: how the Conversion Lift pipeline works with Mindbody
Every client-create and booking fires through AnyCRM's Conversion Lift pipeline. The lead event lands inside your CRM for business logic, AND fires a real conversion event server-side into Google Ads, Facebook Ads, and LinkedIn Ads using the verified origin of your registered domain. Server-side means the conversion can't be blocked by ad-blockers, doesn't degrade on iOS or Safari, and arrives with full attribution context so the Ad platforms' bidding algorithms can re-train on it. Your existing website booking widget runs through the same pipeline, so Web and Voice conversions feed the SAME training signal.
Manages the full appointment and class-visit lifecycle inside Mindbody.
Every "can we push the Tuesday massage?" or "actually, cancel tonight's vinyasa" lands with the AI Receptionist instead of at the front desk. AnyCRM reschedules update the existing Mindbody record in place. Cancellations follow Mindbody's own idiom (status change, not deletion) and your studio's late-cancel policy fires through Mindbody's own engine. So you get crystal clarity on what changed, when, and why, instead of a deletion that strips the visit history.
Finds the booking by email in a single step without needing an appointment ID
Customers DO NOT quote appointment IDs over the phone. We've tested with hundreds of callers and each time they were asked 'Can you tell me the appointment id from your email?', the response was the same: 'Why can't you find it yourself?'. AnyCRM gives the AI Receptionist an easy way to find the soonest upcoming booking (appointment OR class visit) for the matching client. And the AnyCRM response forces the AI Receptionist to be human. It reads back the service, staff, location, and time before changing anything.
Reschedules in place and keeps the booking record clean
Rescheduling updates the existing appointment in a single confirmation. No cancel-then-rebook round-trip means the client's visit history, the staff assignment, and any deposit all stay intact. Failed reschedules leave the original appointment untouched.
Cancels without erasing the audit trail, and honours late-cancel policy
When a caller cancels, AnyCRM flags the booking cancelled the Mindbody-native way (status change, not delete) so it stays queryable in reporting and on the visit history. The caller's reason is written onto the client's account, and the studio's late-cancel-fee policy fires automatically through Mindbody's own engine when the cancellation falls inside the window. So the right policy fires every time instead of being argued about later.
For your developer: reschedule & cancel by email
AnyCRM's search, reschedule, and cancel all accept just an email. The soonest upcoming Mindbody booking (appointment OR class visit) for that client is resolved inside AnyCRM and returned as a single chronological list. No appointment IDs at the AI Receptionist layer.
{
"email": "jane@example.com"
}
{
"meetings": [{
"event_uuid": "a7c1f4e9-...",
"event_type_name": "Haircut Only | $50",
"start_time": "2026-05-15T11:00:00-04:00",
"status": "active"
}]
}
{
"email": "jane@example.com",
"scheduled_datetime": "2026-05-16T14:00:00",
"invitee_timezone": "America/New_York",
"reason": "Customer asked to move 1 day later"
}
{
"cancelled_event_uuid": "a7c1f4e9-...",
"new_event_uuid": "f0e22c91-...",
"new_start_time": "2026-05-16T14:00:00-04:00",
"new_start_time_utc": "2026-05-16T18:00:00Z"
}
{
"email": "jane@example.com",
"reason": "Customer is unwell"
}
{
"cancelled_event_uuid": "a7c1f4e9-...",
"status": "cancelled",
"reason": "Customer is unwell"
}
Routes every caller to the right staff member and the right service. Across every location.
Mindbody studios run on staff, session types, and locations. At setup AnyCRM imports your Mindbody staff roster into its database and enriches each staff member with expertise, languages, timezone, and the locations they actually teach at. The AI Receptionist then routes each caller to the staff member who actually offers that service at that location. Existing client-to-staff preferences in Mindbody are honoured as the source of truth.
Routes by service: massage vs personal training vs yoga private
"I want a 60-minute deep tissue with someone who does prenatal" routes to staff whose bookable services include 60-minute deep-tissue AND whose expertise tags include prenatal. "I want a private vinyasa with Sarah" routes to Sarah's private-yoga service at the location she teaches it.
Honours the existing client and their home location
If the caller is already a Mindbody client with a home location and a preferred staff member, the AI Receptionist doesn't reassign them. The appointment and any new note attach to the existing client at the existing home location. No orphaned duplicate at a sister studio.
Respects class capacity and waitlists
When a caller wants a class that's full, the AI Receptionist offers the waitlist instead of inventing capacity. Capacity, waitlist policy, and pricing-option requirements come from the class definition in Mindbody, not the LLM.
For your developer: specialist roster & per-service routing
Team details live in AnyCRM's database, pulled once from Mindbody at setup, enriched with expertise, languages, timezone, and per-location assignments (valuable context for the AI Receptionist that Mindbody's staff object doesn't carry by default). Each staff member's Mindbody record is kept on the record as the bridge for the booking write. At runtime, one read of the team roster matches caller intent → service → staff member → location → bookable slot. AnyCRM does NOT cache your contract templates, your pricing options' business rules, or your membership pipelines. That policy stays inside your CRM, where it belongs.
{}
{
"total_members": 3,
"members": [
{ "user_uuid": "3d2ed2c0-...", "name": "Michelle Arcona", "role": "user", "timezone": "America/New_York" },
{ "user_uuid": "2b00d6f3-...", "name": "Casey", "role": "user", "timezone": "America/New_York" },
{ "user_uuid": "1809c459-...", "name": "Cielona Boco", "role": "owner", "timezone": "America/New_York" }
]
}
{
"user_uuid": "3d2ed2c0-a8fc-45d7-9f67-fc3e6b898bb2"
}
{
"user_name": "Michelle Arcona",
"user_timezone": "America/New_York",
"services": [
{ "event_type_uuid": "b050bcf6-...", "name": "Haircut Only | $50", "duration": 50 },
{ "event_type_uuid": "9a858539-...", "name": "Fine Density Haircut & Finish | $70", "duration": 60 },
{ "event_type_uuid": "c1f70bb1-...", "name": "Full Head + Gloss + Finish | $335", "duration": 210 },
{ "event_type_uuid": "3c01fa3d-...", "name": "All Over Keratin Treatment | $300", "duration": 240 }
]
}
Setup in 3 steps. Battle-tested on real Mindbody studios.
You activate AnyCRM on your Mindbody site once. AnyCRM imports your staff, your session types, your locations, your classes, and your pricing options. AnyCRM also wires up the receiving end inside your CRM so lead events from the AI Receptionist land where your business logic can act on them. Then the AI Receptionist starts capturing inquiries and booking sessions the same afternoon. No middleware. No front-desk transcription.
Connect Mindbody (Public API source credentials + activation, ~5 minutes)
AnyCRM is a Mindbody-approved API partner with our own source credentials. You activate AnyCRM from your Mindbody site's Integrations panel (which generates a one-time activation code), confirm the sites we're allowed to read and write, and approve the scopes we requested. Authorization is per-site and revocable from the Integrations panel at any time. Every write AnyCRM does is signed with AnyCRM's partner credentials, so it's easy to track what the AI Receptionist did when you audit.
Import staff, session types, locations, classes and pricing options. Wire up your CRM's lead-receiving flow.
AnyCRM imports every active Mindbody staff member as a bookable team member with expertise, languages, timezone, and per-location assignments. AnyCRM also reads your session types, your locations, your class schedule, and your pricing options, and freezes them so the AI Receptionist can only book services you actually offer, and locks inbound-call source attribution (always AI Receptionist Call or AI Receptionist Web) so reporting stays consistent. During onboarding we set up the receiving flow inside your CRM so the lead events from the AI Receptionist land where your business logic can act on them. AnyCRM does NOT replicate your contract templates, your pricing-option logic, or your membership pipelines. Your CRM decides what happens after a lead is captured. AnyCRM just delivers a clean event.
Drop the AI Receptionist on your phone line and your site
Forward your studio's number to the AI Receptionist's number and paste the chat widget into your site. The same AI Receptionist (same staff, same Mindbody site, same lead-event pipe into your CRM and your ad platforms) answers both voice and web. Live the same afternoon.
Why not just use Mindbody's Messenger[ai] + Online Booking widget + Branded Web?
Mindbody's own Messenger[ai] is a chat-based AI assistant that responds to missed calls with a text-back conversation, plus webchat and SMS on the studio's behalf. It is excellent at the post-miss recovery step, but it does not actually pick up the live phone call as a voice agent. The Online Booking widget and Branded Web are excellent at the steps AFTER a client has chosen to come to you via your website. None of them pick up the phone in real time. A new caller at 9pm gets a missed call followed by a text-back, not a live booking conversation. A form sits in the submissions queue until someone reads it. The AI Receptionist is the layer BEFORE all of that. It picks up the call (on voice, not via SMS), asks the right qualifying questions, books the session as a native Mindbody appointment on the right staff member's calendar at the right location, writes a clean, attributed client (with the source set to AI Receptionist Call or AI Receptionist Web and a call summary as the first note), AND sends the same lead event straight into your CRM's downstream business logic plus your ad platforms server-side. So your Mindbody workflows, your analytics, and your Google / Facebook Ads bidding all start optimising on a real conversation, not a missed call recovered via text.
For your developer: the enrichment layer (raw Mindbody API vs our MCP tools)
Every tool the AI Receptionist calls is an opinionated wrapper inside AnyCRM. AnyCRM does the messy work for you. Dedup, home-location resolution, session-type-to-staff matching, timezone math, association labels, error handling, lead-event delivery into your CRM, and server-side conversion tracking into your ad platforms. All of it happens before the LLM ever sees a response. So the AI Receptionist reasons over clean, AI-aligned payloads instead of raw Mindbody internals.
Capturing a new inquiry
createOrUpdatesMindbodyContact accepts name, email, phone, note, plus the inferred home location. AnyCRM searches Mindbody on the full email first, then on the full mobile, filters to exact matches, and only creates a new client when no match exists, with the right home location attached. The note is appended to the client's account after creation so the studio's front desk sees the call summary on the client's profile. AnyCRM also sends the lead event straight into your CRM (with source AI Receptionist Call or AI Receptionist Web), AND fires a server-side conversion event into your ad platforms using the origin of your registered domain. All in one AnyCRM call.Booking the session
createMindbodyContactAppointment takes email, scheduled_datetime (a naive date and time, no offset needed), invitee_timezone, and session_type_id. AnyCRM resolves the right staff member from our roster (filtered by which staff members actually offer that session type at that location and are currently active), converts the naive datetime to studio local time, snaps it to the session-type increment, builds the payload with all required fields, links the matching pricing option if the studio runs pay-at-booking, sends the same lead event straight into your CRM with the booking context, fires the server-side conversion event into your ad platforms, and returns both local and UTC start times in the response.Cancelling with a reason
cancelMindbodyAppointment takes email and reason. AnyCRM resolves the soonest upcoming booking (appointment OR class visit), picks the correct endpoint based on the booking type, writes the reason as a note on the client's account, applies the studio's late-cancel-fee policy automatically through Mindbody's own engine if the booking is inside the window, and returns the cancelled booking and the recorded reason so the AI Receptionist can read it back to the caller. All in one AnyCRM call. No deletion, full audit trail, booking stays in the visit history and in the staff member's reporting.Every AnyCRM tool for Mindbody follows the same AI-alignment contract, so the AI Receptionist never has to think about transport:
- Naive datetimes in, Mindbody-native shape out. The AI Receptionist passes
2026-05-15T11:00:00and a timezone string. AnyCRM converts it to studio local time and snaps to the session-type increment. - Email is the identity. Cancel and reschedule never need an appointment ID at the AI Receptionist layer. Email and soonest-upcoming resolves inside AnyCRM, across appointments AND class visits.
- Session types, staff, locations, and pricing options come from setup, not the LLM. The AI Receptionist can't book a session a staff member doesn't offer, can't invent a location, can't override a session type's duration, and can't promise a pricing option that doesn't exist for that client. The values are frozen at setup.
- Existing clients are sacred. If the caller already exists in Mindbody, AnyCRM preserves their client record and home location. New clients only get created when no match exists by email or mobile.
- Cancellation is a status change, not a deletion. Mindbody's idiom is preserved so reporting, late-cancel policy, and the studio's visit-history view all stay accurate.
- Every lead event leaves AnyCRM in two places at once. Your CRM gets the lead event so your business logic can run. Your ad platforms get the server-side conversion event so bidding optimises against real conversations. Both happen on the same AnyCRM call. No race conditions, no missing events.
- Flat, deterministic shapes. Every AnyCRM response has the same top-level keys across every tool, so the AI Receptionist's prompt never grows with edge-case branching.
- Errors are messages, not codes. An error from Mindbody becomes a one-sentence reason the AI Receptionist can repeat to the caller without translation.
- Idempotent reschedules. If a reschedule fails mid-flight, the original Mindbody appointment is preserved. The customer never ends up with nothing.
Multi-staff setup. Team roster, services & system-prompt assembly
If you run more than one staff member on Mindbody, AnyCRM imports the team roster once, you link each staff member to the session types and locations they actually cover, and AnyCRM bakes the result into the AI Receptionist's system prompt at setup time. Not at runtime. The AI Receptionist doesn't query your team roster on every call. It already knows who teaches what at which location.
- Team roster import. AnyCRM imports your Mindbody staff once and writes each one into its database keyed by
crm_user_id(with name, role, expertise, languages, timezone, Mindbody staff record, and per-location assignments). - Per-staff session types and classes. For each staff member AnyCRM resolves the session types they actually offer, the classes they teach, and the duration per session type. One call per person, cached.
- Service visibility. Each session type is flagged Public, Private or Ignored. The AI Receptionist only routes to and books on Public services. You toggle this in the AnyCRM dashboard without re-deploying.
- Lead-event receiving flow inside your CRM. During onboarding we wire up the flow inside your CRM that receives lead events from AnyCRM. That's where your membership-creation and contract-assignment policy lives. AnyCRM doesn't try to own it.
- System-prompt assembly. The cached team roster, session-type, and class JSON is prepended to the AI Receptionist's system prompt before the humaniser splits (personality, etiquettes, tone, speech style). So the AI Receptionist reads the studio before it reads its own instructions.
- Runtime stays minimal. On a live call the AI Receptionist makes at most one availability call and one booking call. Never a team roster lookup. Updates to staff, services, or classes re-run the cache. The AI Receptionist picks them up on its next deploy.
The end result: the AI Receptionist can match "I want a 60-minute prenatal massage with someone who has Wednesday evenings" → the staff whose bookable services include prenatal-massage-60 and whose expertise tags include prenatal → that staff member's availability at the right location → a booked Mindbody appointment on that staff member's schedule → a lead event delivered straight into your CRM → a server-side conversion event in your ad platforms. Without a single team roster query during the call.
Currently running for yoga and pilates studios, boutique gyms, massage and wellness spas, personal-training studios, and martial-arts schools. Anyone whose schedule is in Mindbody but whose front desk can't pick up every phone call.
How most AI Receptionists built on Smith.ai, My AI Front Desk, or Goodcall fail for yoga and pilates studios, boutique gyms, wellness spas, and personal-training studios that use Mindbody. And why AnyCRM can't.
Most AI Receptionists fail on Mindbody in the same handful of ways. Duplicate clients, partial-match search collisions, session-type-to-staff mismatches, invented session types and locations, wrong-schedule bookings, deletions that bypass the late-cancel policy, appointment-vs-class confusion, hardcoded intro-pack and membership rules that drift away from your real policy, and conversion data that never reaches your ad platforms server-side. AnyCRM can't fail in any of these ways, because each failure was solved one layer down inside AnyCRM. And because AnyCRM delegates membership-creation and contract policy to your CRM's own flow rather than trying to encode it, AND runs web and AI Receptionist conversions through a single unified conversion pipe instead of two disconnected stacks.
Duplicate client records
Partial-match search returning the wrong client
Booking a session type the staff member doesn't offer
Inventing session types, locations, or pricing options that don't exist
Booking the wrong staff member's schedule
Cancelling by deletion instead of by status change, bypassing the late-cancel policy
Mixing up appointments and class visits
Encoding your membership and intro-pack policy in the prompt or in middleware
Web bookings and AI Receptionist bookings run on two separate conversion-tracking stacks
The AI Receptionist is honest because AnyCRM doesn't let it lie. And AnyCRM is sophisticated because it doesn't pretend to own policy that belongs inside your CRM, while quietly fixing the conversion-tracking gap nobody else has thought to close.
AnyCRM vs Smith.ai, My AI Front Desk, Goodcall on Mindbody
| Capability | AnyCRM | Smith.ai | My AI Front Desk | Goodcall |
|---|---|---|---|---|
| Live Mindbody appointment or class enrollment booked DURING the call | Yes. Native Mindbody appointment or class visit, staff-matched, location-correct. | Partial. "Share your Mindbody calendar link" — human receptionist books on your calendar. | Partial. Code-by-Zapier + Webhooks Custom Request (own docs admit "no official Zapier app"). | Partial. Connector hop against the Mindbody API, not a guaranteed native write. |
| Dedup-before-write on email and mobile (with exact-match filtering) | Yes. Always. | Manual. Receptionist discipline, not an API invariant. | No. Single Custom Request with no published search-then-write step. | No published guarantee. |
| Partial-match search resolves to the right client (no first-result-wins) | Yes. Full email / mobile, exact-match filtered. | Manual. Receptionist picks from the result list. | No. Custom Request takes first result. | No structural guard. |
| Preserves existing Mindbody client and home location on returning callers | Yes. Existing client is sacred. | Implicit, not guaranteed. | No. Can overwrite or duplicate. | Depends on the underlying connector's defaults. |
| Routes by service / specialist (session type + expertise + location) | Yes. Service-and-location matching is part of AnyCRM's team roster. | Manual, depends on the receptionist. | No. | No. |
| Session types, locations, pricing options frozen from your real Mindbody site | Yes. Read at setup, baked into the prompt as a frozen table. | Not API-enforced. | No. Writes can fail on invented values. | No structural guard. |
| Cancellation preserves the audit trail (status change, not deletion) | Yes. Mindbody-native cancellation. | Manual. | No. Deletion strips the visit history. | No. Cancellation happens in the scheduler, not the Mindbody booking. |
| Late-cancel-fee policy fires through Mindbody's own engine automatically | Yes. Policy parameter applied when the cancellation is inside the window. | Manual. | No. Custom Request bypasses the policy parameter. | No. |
| Reschedule in place (no cancel-then-rebook) | Yes. | Manual. | No. | No. |
| Appointments AND class visits merged into one chronological view | Yes. Both endpoint families queried in parallel. | Manual UI scrolling. | No. Zap picks one family at design time. | No. |
| Membership / intro-pack policy delegated to YOUR CRM's own flow | Yes. Lead event delivered straight into your CRM, into the receiving flow we wire up at onboarding. | No. Policy lives in the receptionist's playbook. | No. Hardcoded "Create Member / Sell Intro Pack" action in Zapier. | No. Connector-default behaviour. |
| Unified conversion pipe: web widget AND AI Receptionist → CRM + ad platforms server-side | Yes. Same shape, same source taxonomy, same server-side delivery to your CRM and your ad platforms. | No. Web and voice run on separate stacks. | No. Web and voice run on separate stacks. | No. Web and voice run on separate stacks. |
| Server-side conversion events sent to Google Ads, Facebook Ads, and analytics (origin = your registered domain) | Yes. Every call and chat lead lands server-side. | No. | No. | No. |
| Source attribution stays consistent across web and voice | Yes. AI Receptionist Call, AI Receptionist Web, plus your web widget identifiers. | Manual / inconsistent. | No standardised taxonomy. | Whatever the underlying connector defaults to. |
| Scale ceiling | Bounded by Mindbody API limits, not by staffing. | Bounded by human receptionist staffing. | Bounded by Zapier rate limits and Custom Request contracts. | Bounded by the connector-and-sync hop. |
Your Mindbody data passes through AnyCRM. It doesn't stick.
AnyCRM processes your Mindbody data to answer the call. Then forgets it. The only thing AnyCRM persists is a conversation history ID so the AI Receptionist can recognise a returning caller. Clients, appointments, class visits, staff schedules, pricing options. All of it stays in Mindbody, owned by your Mindbody site.
What AnyCRM stores
Conversation history IDs only. So the AI Receptionist can pick up where it left off if a caller hangs up and rings back. No call audio, no transcripts of client records, no caller PII.
What AnyCRM doesn't
Caller names, emails, phone numbers, Mindbody client identifiers, your staff roster, your session types, your class schedule, your pricing options, your visit history. None of it. AnyCRM reads what it needs, hands it to the LLM, fires the events, and discards the payload.
Where data lives
In your Mindbody site and in whatever systems your CRM's flow forwards lead events to. Clients, appointments, class visits, notes all live in Mindbody. Source-attributed (always AI Receptionist Call or AI Receptionist Web), attributed to AnyCRM in the audit log, revocable. AnyCRM does not build a shadow scheduler alongside yours.
Revocation
Revoke AnyCRM's integration from your Mindbody site's Integrations panel and the AI Receptionist loses access immediately. There is no "export your data" step because there is no data to export. It was never AnyCRM's to hold.
For your developer: OAuth scopes & the smallest-surface principle
Mindbody's Public API uses per-site activation with scoped endpoint access. AnyCRM only touches the smallest set of endpoints required for the booking lifecycle. Nothing for payments beyond pricing-option checkout, nothing for analytics, nothing for marketing campaigns.
- Clients (read + write). Search, create, and annotate clients (the lead-capture work).
- Appointments (read + write). Read availability and write appointments on the routed-to staff member's schedule (the booking work).
- Classes (read + write). Enroll clients into classes and resolve class visits for the lifecycle endpoints.
- Staff, session types, locations, pricing options (read-only). Roster, services, locations, and pricing options at setup time.
- Not requested: payment-method tokenization beyond the studio's existing pricing-option checkout flow, contract management, autopay schedules, marketing campaign data, retail inventory, your other integrations.
Same Mindbody-approved partner credentials any approved integration uses. Just a smaller surface. AnyCRM holds the partner credentials and per-site activation tokens (every write is signed with AnyCRM's partner credentials, so each booking and client change is attributable to AnyCRM in Mindbody's audit trail). The LLM never sees the credentials, and every tool call is logged with the operation name, never the raw payload.
$36 to get started. No monthly subscription. No commission on voice minutes. Ever.
The AI Receptionist industry has settled into a quiet little racket: wrap a public voice provider (usually Eleven Labs) and a public chat platform in your own UI, sell it back on a monthly subscription with a metered minute allowance, and pocket a 3–5× markup on every minute your customer's caller spends on the phone. The customer never sees the underlying price. We did not want to build that business.
The Transparency Ladder — you choose how far up you climb.
Most AI Receptionist products sell one thing: a monthly plan with a minute cap. AnyCRM sells five things, ordered by how much we do for you. Start at $36 with a prompt-and-pasted DIY agent. Stop there if it's enough. Or keep climbing through the upgrades to a full custom implementation with MCP tools, conversion tracking, and a CRM-side flow we configure for you.
A prompt pack and a deployment guide. You wire up a basic AI Receptionist on web chat and voice using OUR humanizer prompts and OUR step-by-step videos.
- Two humanizer prompts (warmth, pacing, filler words)
- Web chat + voice setup videos
- Same-afternoon live deployment
- No MCP tools (no booking writes into your CRM)
- No conversion tracking
- No CRM-side lead-event flow
Add this at checkout. We walk through your setup together so the Quickstart lands faster, without you reading the docs alone.
- Live setup walkthrough
- Humanizer prompt tuning to your voice
- Q&A about your industry's quirks
Adds the first round of MCP tools so the AI Receptionist actually books appointments into your CRM (not just talks about booking them).
getAvailability+createContactAppointmentMCP tools- Live booking into your CRM
- Dedup-before-write on email and phone
- Still DIY — you wire the tools yourself with our videos
Adds search, reschedule, and cancel MCP tools. Now the AI Receptionist owns the whole appointment lifecycle — the same one we describe in the Availability and Lifecycle sections above.
- Search + reschedule + cancel MCP tools
- Audit-preserving cancellation
- Specialist / team-member routing if your CRM supports it
- Still DIY — conversion tracking and CRM flow not included
We build it for you. The whole stack: MCP tools wired, web forms unified into the same lead-event pipe, server-side conversion tracking into Google / Facebook / LinkedIn Ads, AND the lead-receiving flow inside your CRM tuned to your industry and your client configuration.
- Everything in Steps 1–3, done for you
- Unified conversion pipe (web + AI Receptionist)
- Server-side conversion tracking with your domain origin
- CRM-side lead-event flow we configure at onboarding
- One-time custom quote — no monthly subscription
How AnyCRM stacks up against the monthly-subscription crowd.
Here is what you would pay each provider to handle 500 voice minutes a month — a fair mid-volume number for a service business that picks up after hours. Sourced directly from each vendor's published pricing page.
| Cost & structure | AnyCRM | Smith.ai | My AI Front Desk | Vocaly AI |
|---|---|---|---|---|
| Pricing model | One-time fee ($36 → $850+) + you pay Eleven Labs directly | Monthly subscription, billed per call | Monthly subscription, billed per minute | Monthly subscription, billed per minute |
| Entry tier | $36 one-time | $300/mo (30 calls) | $99/mo (200 voice min) | $399/mo (2,500 min) |
| Cost for ~500 voice min / month | $0 to AnyCRM + ~$25–85 paid directly to Eleven Labs | ~$2,100/mo (Pro tier, ~300 calls) | $99 + 300 overage min @ $0.25 = $174/mo |
$399/mo (2,500 min cap) |
| Commission / markup on voice minutes | 0%. You pay Eleven Labs directly. | Bundled (per-call pricing hides minute markup) | ~3–5× markup on Eleven Labs' published rate | Bundled (rate not disclosed) |
| Hard monthly minute cap | No cap. Eleven Labs scales with your traffic. | Yes, by call count | Yes (200 min on $99 tier) | Yes (2,500 min on $399 tier) |
| Underlying voice provider disclosed | Yes — Eleven Labs. We say it openly. | N/A (human receptionists) | Not disclosed | Not disclosed |
| CRM-side lead-event flow built for you | Yes (Custom Implementation, tuned to your industry) | No | No (Zapier action list only) | No (custom tier only, opaque) |
| Server-side conversion tracking to Google / Facebook / LinkedIn Ads | Yes (Custom Implementation) | No | No | No |
| Cost over 12 months at ~500 min/mo | $36–$850 one-time + ~$300–$1,020 paid to Eleven Labs | ~$25,200 | ~$2,088 | ~$4,788 |
Pricing as listed on each vendor's published pricing page (Smith.ai, My AI Front Desk / Frontdesk, Vocaly AI, Eleven Labs) at time of publication. Eleven Labs Conversational AI is currently $0.05–$0.17/min depending on plan; "$25–85 paid directly" assumes you sit on the Free, Starter, or Creator plan for low-volume usage. Smith.ai is human-staffed; My AI Front Desk & Vocaly AI are AI-only.
One backend. Six channels. Stacked ROI.
Indicative monthly numbers based on what service businesses already see from a single channel — multiplied by the channels you switch on. Update the agent once; every channel reflects it.
Four steps. One afternoon.
No Zapier. No n8n. If you can copy and paste, you can do this.
Open the Quickstart
You get the prompt pack, the humaniser prompts, and the deployment guide.
Connect Mindbody
One API key. The agent reads contacts and writes appointments — both ways.
Pick your channel
Web chat, voice line, or both. Same backend, same brain.
Go live
Test five calls yourself. Send the number to your team. Done.
Live by tonight. Booking customers by tomorrow.
$36 once. If it doesn't work for your business, you've lost less than dinner.