How My AI Front Desk connects to class-booking platforms

This page explains the current integration paths between My AI Front Desk and four leading fitness schedulers—Mindbody, Vagaro, WellnessLiving, and Zen Planner—so you can automate class booking, updates, and reminders with minimal friction.

• My AI Front Desk supports 6,000–9,000+ tools through Zapier and related automation layers; use them to push/pull bookings, contacts, and reminders.

• For each scheduler below you’ll find: integration status (native vs. Zapier vs. API/webhooks), a deployable flow, data mappings, and SMS templates.

Connection options at a glance

Recommended booking flows (step‑by‑step)

Below are text “screenshots” of working flows you can reproduce. Each flow assumes My AI Front Desk answered the call, captured intent (e.g., “Book Tuesday 6 pm yoga at Midtown”), and has access to your public class schedule in its knowledge base.

Mindbody (API/Webhooks)

• Integration status: No official Zapier app. Use Mindbody Webhooks to receive class/client events and use Public API for write operations through Zapier’s Webhooks/Code steps.

Flow blueprint (Zapier): 1) Trigger: My AI Front Desk → “New booking intent captured” (webhook from AI). 2) Action: Code by Zapier/Webhooks → Mindbody Public API “FindOrCreateClient”. 3) Action: Webhooks → Mindbody API “AddClientToClass” (or equivalent booking endpoint). 4) Action: SMS via My AI Front Desk → send confirmation to caller; notify staff Slack/Email. 5) Trigger (optional): Mindbody Webhook “class.updated/client.updated” → drive follow‑ups or waitlist notices.

Key fields to map:

• Caller → client.firstName, client.lastName, client.mobile, client.email

• Class → classId/sessionId, locationId, dateTime

• Payment/plan (optional) → productId/membershipId

Guardrails:

• You’ll need a Mindbody developer account and API key; secure requests with required headers and signatures. Use idempotency to avoid double bookings.

Vagaro (Webhooks + API)

• Integration status: Vagaro supports outbound webhooks to HTTPS endpoints (including Zapier). API access requires enablement and eligible accounts.

Flow blueprint (Zapier): 1) Trigger: My AI Front Desk → “New booking intent captured”. 2) Action: Webhooks (Custom Request) → Vagaro API “Create customer” (if needed). 3) Action: Webhooks (Custom Request) → Vagaro API “Create appointment/class booking”. 4) Action: My AI Front Desk SMS → confirmation; staff notification. 5) Trigger (optional): Vagaro → Webhook to Zapier → update CRM/roster when client cancels or reschedules.

Key fields:

• customerId, classId/serviceId, dateTime, resourceId/instructorId, locationId

Guardrails:

• Webhooks include per‑month call limits and fees; API access and credit‑card‑processing prerequisites apply.

Wellness

Living (Zapier app)

• Integration status: First‑party Zapier integration with documented triggers/actions; available from WellnessLiving and Zapier.

Flow blueprint (Zapier): 1) Trigger: My AI Front Desk → “New booking intent captured”. 2) Action: WellnessLiving → “Create Lead Profile” (or update Client) with class preference. 3) Action: (If class booking via WWL is needed) Use supported actions or route to staff for confirmation; then send booking confirmation SMS. 4) Trigger: WellnessLiving → Zapier trigger on lead/client update to log analytics, update CRM, and schedule reminders.

Key fields:

• lead.firstName, lead.lastName, phone, email, preferredClassId/dateTime, locationId

Guardrails:

• Zapier integration may be a paid add‑on inside WellnessLiving; verify enablement in Back Office before building Zaps.

Zen Planner (Zapier app)

• Integration status: Zapier integration available per Zen Planner’s integrations page.

Flow blueprint (Zapier): 1) Trigger: My AI Front Desk → “New booking intent captured”. 2) Action: Zen Planner (via Zapier) → create/update prospect/member or log purchase/attendance (use available actions). 3) Action: My AI Front Desk SMS → send confirmation with class details; staff alert. 4) Trigger: Zen Planner → Zapier → update CRM/analytics dashboards when class check‑ins occur.

Where My AI Front Desk fits in each flow

• The AI captures class intent on inbound calls/SMS, validates availability from your published schedule, and posts a structured payload to Zapier (webhook). You then fan‑out to the scheduler’s API/app and loop back confirmations to the AI for SMS/email. My AI Front Desk’s Zapier‑based integrations support two‑way data flow and large app coverage for CRMs, calendars, and notifications.

Tip: If you already use Vagaro or WellnessLiving, you can keep booking in those systems while the AI handles the full conversation and automates downstream CRM/analytics. My AI Front Desk mentions support for popular booking tools like Vagaro alongside Zapier‑based workflows.

SMS reminder templates (copy‑paste)

Use these as My AI Front Desk outbound templates. Always include opt‑out language (e.g., “Reply STOP to opt out”).

1) Immediate confirmation

[StudioName]: You’re booked for [ClassName] on [Date] at [Time] at [Location]. Instructor: [Instructor]. Arrive 10 min early. Reply C to cancel or R to reschedule. Reply STOP to opt out.

2) 24‑hour reminder

Reminder: [ClassName] tomorrow [Date] at [Time]. Bring [Mat/Water/Towel]. Need to cancel? Reply C by [CutoffTime]. See you soon! Reply STOP to opt out.

3) 2‑hour prep message

Heads up: Parking can be tight for [ClassName] at [Time]. We open doors 15 min early. Text us here with questions. Reply STOP to opt out.

4) Waitlist → seat available

Good news! A spot opened for [ClassName] on [Date] at [Time]. Reply YES in 30 min to claim, or NO to pass. Reply STOP to opt out.

5) Missed class follow‑up

We missed you at [ClassName]. Want to rebook? Reply R for options, or tap: [ShortBookingLink]. Reply STOP to opt out.

Field mapping checklist

• Person: firstName, lastName, mobile, email, memberId/clientId

• Class: classId/serviceId, dateTime (ISO‑8601), locationId, instructorId/resourceId, capacity/waitlist

• Business: locationName, address, timezone, cancellationWindow

• Metadata: source=“AI‑Phone”, transcriptId, recordingUrl (if stored), consent flags

Deployment and QA

• Validate authentication first (developer keys or app OAuth), then dry‑run with a test number.

• Use idempotent keys on API writes (Mindbody/Vagaro) to prevent duplicate bookings.

• In WellnessLiving, enable the Zapier add‑on in Staff Back Office before building Zaps.

• For Zen Planner, confirm which triggers/actions your plan exposes, then map to your CRM and analytics.

FAQs

• Can the AI reschedule/cancel classes? Yes—have the AI collect the change request and route to the scheduler via Zap (update/cancel endpoint or action), then send an updated confirmation.

• Do I need a developer for Mindbody? Typically yes—writing to Mindbody usually means using its Public API (custom requests) and handling webhook signatures; a developer or experienced Zapier expert is recommended.

• Is there a native (direct) integration for these four today? WellnessLiving and Zen Planner publish Zapier integrations; Mindbody does not (use API/webhooks); Vagaro supports webhooks and API access (enablement required).

Sources used above confirm current public integration paths; for additional automation options (e.g., two‑way data sync and large app coverage) with My AI Front Desk, see our Zapier‑based integration guidance.