← Blog

AI & Automation

AI Receptionist for Pilates Class Package Inquiries Setup

Configure an ai-receptionist-for-pilates-class-package-inquiries workflow with routing rules, data fields, booking steps, scripts, and a launch checklist.

··9 min read
Pilates owner configuring an AI receptionist for package inquiries and intro bookingsWatch · 20s

A Pilates prospect asking, “How much are classes?” rarely needs a price list alone. They may need to know whether beginners can join group reformer classes, whether an intro is required, how credits expire, or whether private sessions would be a better starting point.

If your AI receptionist cannot resolve those questions and advance the inquiry, it is only a searchable FAQ. A useful system identifies the client type, applies your package and location rules, offers an eligible next step, and hands exceptions to staff with enough context to act.

The setup matters. An AI receptionist connected to incomplete package data can confidently give the wrong answer faster than a busy front desk.

See how Fitty can be configured around your Pilates inquiry workflow →

Define the outcome before configuring the AI

Start with the result you want from each inquiry. For Pilates package questions, the acceptable outcomes are usually:

  1. An eligible prospect purchases a package.
  2. A new client books the required intro, assessment, or private session.
  3. An existing client receives the correct package link for their location.
  4. A policy, medical, payment, or accessibility question reaches a person.
  5. The prospect consents to a later follow-up because no suitable time is available.

“Answered the question” is not enough. The workflow should record which outcome occurred and prevent the AI from pushing a purchase when a prerequisite has not been satisfied.

Build the package records the receptionist will use

Create one structured record for every public package. Do not ask the AI to infer current terms from website copy, old emails, social posts, or staff notes.

Each record should contain these required fields:

Field What to enter
Package ID Stable internal identifier that does not change with the display name
Public name Exact name shown in checkout and booking
Location Specific studio or clearly marked all-location eligibility
Service type Group reformer, mat, private, duet, intro, or another defined service
Client eligibility New clients, existing clients, or both
Prerequisite Intro, assessment, prior experience, instructor approval, or none
Included uses The sessions or credits included in the purchase
Validity Activation, expiration, renewal, and rollover rules
Restrictions Class level, location, instructor, sharing, or transfer limitations
Cancellation policy Approved short explanation plus the full policy URL
Purchase URL Direct link for the correct package and location
Booking action Eligible appointment or class type after purchase
Escalation owner Role responsible for exceptions or unresolved questions
Last reviewed Date and staff member who approved the record

Use separate records when two locations have different prices, expiration terms, or prerequisites. A location field buried inside a paragraph is easier to miss than a dedicated routing value.

Example package configuration

The following is a configuration pattern, not a suggested package policy. Replace every value with your studio’s actual terms.

package_id: intro_reformer_location_a
public_name: Reformer Introduction
location: location_a
service_type: intro_private
client_eligibility: new_clients
prerequisite: none
included_uses: defined_by_studio
validity_rule: approved_policy_reference
purchase_url: location_specific_checkout_url
booking_service_id: booking_system_service_id
medical_questions: human_handoff
refund_or_extension_requests: manager_handoff
owner: studio_operations
last_reviewed: YYYY-MM-DD

A practical implementation lesson is to keep descriptive answers separate from transactional identifiers. Staff may rename “Beginner Reformer Intro,” but the internal package and service IDs should remain stable. Otherwise, a copy edit can break booking or send prospects to the wrong checkout item.

Configure routing logic for Pilates inquiries

The routing tree should use the fewest questions necessary to determine eligibility. Do not disguise a long lead form as a conversation.

1. Identify the inquiry.

Classify the message as pricing, package comparison, expiration, beginner eligibility, booking, payment trouble, account policy, or health-related guidance.

2. Confirm the location.

Ask only when packages or schedules differ by studio. If there is one location, assign it automatically.

3. Determine client status.

Ask whether the person is new to the studio. Do not assume that being experienced in Pilates makes someone eligible to skip your studio’s required orientation.

4. Determine the desired format.

Separate group reformer, mat, private, duet, and intro services. These should map to service categories in the booking system rather than rely on keyword matching alone.

5. Check prerequisites.

If the package requires an intro or instructor approval, do not show direct purchase or class-booking actions until the prerequisite is verified.

6. Route the next action.

Use explicit logic such as:

IF health_or_injury_question = true
  THEN stop recommendation and create staff handoff
ELSE IF payment_dispute_or_policy_exception = true
  THEN create manager handoff
ELSE IF client_status = new AND intro_required = true
  THEN offer eligible intro appointment times
ELSE IF package_match = one
  THEN explain terms and offer approved purchase link
ELSE IF package_match = multiple
  THEN ask expected attendance or preferred format
ELSE
  THEN collect contact details and create unresolved-inquiry task

Define fallback states

Every branch needs a safe fallback. Configure at least these states:

  • Missing package data: Do not estimate; tell the prospect staff will confirm.
  • No booking availability: Offer another eligible location, a staff callback, or approved follow-up.
  • Booking connection unavailable: Preserve the lead and requested service instead of repeatedly sending a broken link.
  • Unrecognized package name: Ask for the page or offer shown, then route for review.
  • Conflicting records: Suppress the answer and alert the package-data owner.
  • Human requested: Stop qualification and hand off promptly.
  • Opt-out received: Stop automated promotional follow-up.

These states prevent the most damaging failure mode: an authoritative answer based on missing or stale information.

Connect the workflow to your booking system

An AI receptionist should not claim a time is available based on a static schedule page. Booking requires current data and a confirmed write-back to the system of record.

Use this integration sequence:

  1. Map locations. Match each conversational location value to the corresponding booking-system location ID.
  2. Map services. Connect intro, private, duet, mat, and reformer options to their exact service or class IDs.
  3. Map staff and resources. Include instructor eligibility, reformer capacity, rooms, and any equipment resources represented by the booking platform.
  4. Apply client rules. Pass new-versus-existing status and verified prerequisites where the booking system supports them.
  5. Read live availability. Return only currently eligible times, using the studio’s timezone.
  6. Collect required fields. At minimum, capture the fields your booking system requires, which commonly include name, contact method, location, service, and selected time.
  7. Create the booking. Require a successful response from the booking platform before confirming the appointment.
  8. Send confirmation. Include the service, location, time, preparation instructions, and cancellation-policy link.
  9. Handle failure. If creation fails, retain the conversation data and route a task to staff. Never tell the prospect they are booked without confirmation.

Fitty is positioned as an AI agent for lead response, booking, follow-up, and dues collection. The exact actions available depend on your WTF Go setup, connected systems, package rules, and supported integrations. Confirm your booking and payment requirements with WTF Go before treating any workflow as fully automated.

Ask WTF Go how Fitty would connect to your current Pilates booking flow →

Complete sample conversation with routing notes

Below is a full example for a studio that requires new clients to complete an intro before joining group reformer classes. It demonstrates structure, not a policy every studio should adopt.

Prospect: How much are your reformer class packages?

AI receptionist: We have reformer options for eligible group clients, plus an introduction for people who are new to our studio. Are you a current client, and which location would you attend?

Routing note: The AI answers the category question, then requests the two fields that control package eligibility.

Prospect: I’m new. Downtown. I’ve done Pilates before.

AI receptionist: Thanks. The Downtown studio requires new clients to complete its introduction before booking group reformer classes, even if they have prior experience. After that, you can choose from the approved group options. Would you like to see available intro times or review what the group packages include first?

Routing note: Prior Pilates experience does not override the studio-specific prerequisite.

Prospect: What do the packages include, and do they expire?

AI receptionist: The studio currently lists these eligible group options after the introduction: [approved package names and inclusions]. Their validity terms are [approved expiration language]. Credits are subject to the studio’s cancellation policy: [policy link]. Would you like help comparing them based on how often you expect to attend?

Routing note: Package names, inclusions, and validity must be inserted from approved records, not generated.

Prospect: Probably twice a week. I also have lower-back pain. Which class should I take?

AI receptionist: I can explain the studio’s packages and help with scheduling, but I cannot determine which class is appropriate for pain or a medical concern. I can send your question to the studio team before you book. What is the best phone number or email for their reply?

Routing note: The health question stops package recommendations and creates a human handoff.

Prospect: Email is fine.

AI receptionist: Please provide your email address. I’ll include that you are new, prefer Downtown, expect to attend about twice weekly, and want guidance before booking because of lower-back pain.

Routing note: The handoff carries the useful context so staff do not make the prospect repeat the conversation.

This example also shows what the AI should not do: declare a class safe, recommend exercise for pain, waive the intro requirement, or keep pushing checkout after a health concern appears.

Follow up based on the actual state

Use different follow-up messages for different outcomes:

  • Package discussed, no action: Offer to clarify the two relevant options.
  • Intro selected, not booked: Provide eligible times or ask whether scheduling is the obstacle.
  • Checkout started, not completed: Offer help with a technical issue without implying payment failed.
  • No availability: Notify the prospect only when an approved opening or alternative becomes available.
  • Human handoff created: Confirm receipt, then pause automated sales prompts.
  • Purchase or booking completed: Stop acquisition follow-up and move to confirmation or onboarding.

Any automated messaging should follow applicable consent, channel, and opt-out requirements. Fitty can support follow-up workflows as configured, but channel availability and triggers should be verified for your specific setup.

Pilates package inquiry launch checklist

Before going live, verify each item:

  • Every active package has an approved structured record.
  • Retired offers and old checkout links are removed.
  • Location-specific terms are separated.
  • New-client prerequisites are explicit.
  • Group reformer, mat, private, duet, and intro services map correctly.
  • Purchase links open the intended package and location.
  • Booking service IDs create the correct appointment or class.
  • Live availability respects staff, capacity, resource, and timezone rules.
  • A booking is confirmed only after a successful system response.
  • Medical, pain, pregnancy-related, refund, freeze, transfer, and exception questions escalate.
  • Failed bookings preserve lead details and create a staff task.
  • Follow-up stops after booking, purchase, handoff, decline, or opt-out.
  • Confirmation messages include location and cancellation information.
  • Staff know who owns package updates and escalations.
  • Test conversations cover misspellings, incomplete questions, and conflicting requests.

Run the checklist again whenever packages, prerequisites, policies, locations, or booking systems change.

Turn package questions into controlled workflows

The right AI receptionist for Pilates class package inquiries is not the one with the most human-sounding small talk. It is the one that uses approved package data, recognizes studio-specific prerequisites, books only eligible services, and stops when staff judgment is required.

WTF Go and Fitty are designed around fitness and wellness operations, including lead response, follow-up, booking, and dues workflows. Because exact automation depends on your connected systems and configuration, validate the supported integration path before launch.

Review your Pilates package inquiry workflow with WTF Go →

Frequently asked questions

Can an AI receptionist recommend a Pilates class package?

Yes, when the recommendation uses approved criteria such as location, client status, service format, prerequisites, and intended attendance. Medical concerns and policy exceptions should go to staff.

What happens if the booking-system connection fails?

The AI should avoid confirming the booking, preserve the prospect’s details and requested time, explain that scheduling could not be completed, and create a staff follow-up task.

What data does a Pilates package inquiry workflow need?

It needs structured package, location, eligibility, prerequisite, validity, policy, purchase-link, booking-service, escalation-owner, and review-date fields.

Should the AI answer questions about pain, injuries, or pregnancy?

It should not diagnose, prescribe, or decide whether a class is appropriate. It should stop the recommendation and route the question to qualified studio staff or an appropriate professional.

Can Fitty work with any Pilates booking system?

Integration support can vary by system and configuration. Confirm your booking, payment, messaging, and data-sync requirements with WTF Go before planning the final workflow.

Run your gym on autopilot with WTF Go

Fitty — your AI receptionist — answers calls and DMs, fills classes, follows up with every lead, and collects dues while you coach.