Class and session booking

Booking a class or individual session sounds simple until the caller has constraints. The right option may depend on service type, location, instructor, duration, existing-customer status, or accessibility needs. A front desk can resolve those details, but it also has to serve people already on site. Voicemail shifts the work without completing it.

An AI phone agent can collect the booking criteria, use availability exposed through Cal.com or Google Calendar, offer matching openings, and confirm the selected appointment. The business defines what each class or session means and which rules the agent may apply. The agent should not invent capacity, override a prerequisite, or treat an unavailable slot as available.

A concrete booking call

Suppose a caller wants a beginner training session on a weekday evening.

Agent: I can help find an available session. Is this for an individual appointment or a group class?

Caller: An individual beginner session. I have not been there before.

The prompt requires a new-client session type, preferred location, and time window. The agent collects those details and asks whether the caller has an accessibility need the scheduling team should know about. It does not ask for a medical history or decide whether the activity is suitable.

The agent checks the availability that the business has made available through the scheduling connection.

Agent: I have an opening Tuesday evening and another Thursday evening at the downtown location. Which works better?

The caller chooses Thursday. The agent collects the required contact fields, repeats the location, date, time, and session type, then creates the booking. It sends the structured result to the chosen system of record. If the caller asks to join a full class, requests a discount, or needs an exception to a prerequisite, the agent follows the defined human route rather than promising an accommodation.

This is appointment setting with a class-specific decision path. It should end with an actual confirmed booking or a clear next step, not a message that staff must interpret later.

How to set it up on ThunderPhone

Map the booking catalog before writing the prompt. For each class or session, identify the caller-facing name, duration, location, eligibility rules, booking calendar, required fields, and exception owner. Then configure an outline that tells the agent to:

  • distinguish group classes, individual sessions, consultations, and other bookable types;
  • collect preferences before checking availability;
  • offer only openings returned by the approved scheduling connection;
  • repeat the final date, time, location, and service for confirmation;
  • handle no availability, duplicate bookings, and unclear requests; and
  • transfer prerequisites, accessibility questions, policy exceptions, and payment requests to a person.

Use Cal.com or Google Calendar as the booking connection that fits the business's existing workflow. HubSpot or Salesforce can hold an allowed customer or lead record alongside the booking. Google Sheets can support a simple reviewed roster when that is the chosen system, while Slack can notify staff about an exception. REST, webhooks, or an approved remote Zapier MCP server can connect a custom booking system. Expose only the operations the agent needs, and make one system authoritative for availability.

Attach current class descriptions, location details, preparation instructions, cancellation rules, and caller-safe prerequisites to the agent's knowledge base. ThunderPhone supports text, Markdown, CSV, PDF, and DOCX files, with documents selected per agent and searchable during the call. Avoid putting changing availability in a static document; the live scheduling connection should remain the source for openings.

Assign the agent a production number for live calls. Inbound demo U.S. numbers can be used for testing but are not intended for production. If an exception requires attended warm transfer, use an eligible production number that can place the outbound SIP leg. Otherwise, define a cold-transfer or structured follow-up fallback.

Test popular and unavailable times, similar class names, time-zone ambiguity, accessibility requests, prerequisites, minors, duplicate records, a scheduling outage, failed writes, and callers who change their mind mid-booking. Reusable scenarios and graded call logs can verify that the agent reads back the correct details.

What to measure

Track both booking completion and booking quality:

  • callers who complete a confirmed booking;
  • booking attempts that reach no availability;
  • bookings with the correct class, location, and time;
  • duplicate, failed, or manually corrected bookings;
  • exceptions transferred or delivered for follow-up;
  • calls later handled through rescheduling and cancellations; and
  • staff time spent repairing incomplete booking details.

Separate adjacent flows instead of overloading one prompt. Use waitlist management when no opening exists and event registration for one-time programs. Gyms and studios can apply their membership and safety policies in the fitness industry workflow.

Honest limits

The agent cannot determine whether a caller is medically fit for an activity, verify every prerequisite, collect a phone payment, or create capacity that the scheduling system does not expose. It should not promise instructor changes, discounts, refunds, child supervision, or accessibility accommodations that staff have not confirmed.

Keep a person available for sensitive eligibility questions, safeguarding concerns, billing, and exceptions. The booking flow should make routine access easier while leaving judgment and commitments with authorized staff.

Create your ThunderPhone account to configure and test class and session booking.