Booking workflow guide

AI appointment booking for medspas

AI appointment booking can mean two different things: placing an appointment directly into an approved calendar, or capturing a request for staff to confirm. The right model depends on the service, schedule rules, and risk of booking the wrong visit.

Direct booking versus request capture

Direct booking

The system checks approved availability and creates a calendar event. This needs reliable access, exact service durations, buffers, provider rules, and duplicate-booking protection.

Request capture

The system records the caller's preferred time and contact details, then staff confirm. This is often safer for consultations, unclear requests, or calendars that are not yet connected.

Information the workflow needs

Define bookable appointment types, durations, locations, providers, working hours, buffers, lead time, cancellation rules, and what happens when no suitable slot exists. Keep treatment suitability and clinical screening with qualified staff.

What good testing looks like

  1. Book a normal request into an available time.
  2. Try a time outside business hours and a fully booked day.
  3. Test ambiguous service names and multiple locations.
  4. Test rescheduling, cancellation, duplicate callers, and poor audio.
  5. Confirm that medical questions and emergencies are escalated rather than answered.

Agenzo AI integration status

Google Calendar is the first calendar connection planned for early access. Calendly, Vagaro, Mindbody, Jane, and Acuity are planned rather than currently available. The public demo does not connect to any calendar or create real appointments. See the current integrations page for a dated status.

Data boundary

Agenzo AI does not currently offer a BAA and must not receive, store, or transmit PHI. Proposed live workflows require review before activation. Read the security page.