ZenotiHelp

Book appointments with SmartBot

ZTZenoti Docs Team Updated November 3, 2026 7 min readGuide

Guests can book appointments through SmartBot on the web chat widget or by SMS. SmartBot's Booking Agent guides the guest through selecting services, choosing a provider, picking a date and time, and confirming the booking β€” all within a conversational flow.

Audience: Administrators and staff understanding how SmartBot handles appointment booking for guests.

Before you begin

  • SmartBot must be provisioned and the booking flow must be enabled for the center in General Settings.
  • The center must have at least one channel active (web chat, SMS, or IVR).
  • For deposit collection, the center must have deposit rules configured in Zenoti.

How appointment booking works

Starting the booking flow

When a guest indicates they want to book an appointment β€” by selecting the booking option, typing "book", or expressing the intent in natural language β€” SmartBot routes the conversation to the Booking Agent.

Identity verification

Identity verification differs by channel:

  • On the SMS channel, the guest's phone number is inherent to the channel β€” SmartBot already knows it from the message metadata, so no additional capture is needed for guest lookup.
  • On the web chat widget, SmartBot collects the guest's phone number and sends a one-time password (OTP) via SMS. The guest enters the OTP to verify their identity.

Identity verification ensures bookings are associated with the correct guest profile. OTP is invoked when phone-number verification is needed.

Quick Book for returning guests

After verification, SmartBot evaluates whether to offer Quick Book β€” an option for the guest to rebook the same service with the same provider as their previous appointment. Quick Book is offered when the organization has Quick Book enabled in the business configuration and the guest has a previous booking on file.

When offered and accepted, the guest skips service and provider selection and proceeds directly to date and time selection.

Service selection

Guests browse available services by category. SmartBot paginates results at five items per page:

  • On SMS, guests type See More to load the next five items.
  • On web chat, a Show All option is available to expand the full list.

Tip: Because SMS guests must page through long lists, order your service catalog so that the most commonly booked services appear in the first five SMS results. Most guests will not page through multiple screens.

Multi-service bookings

Guests can add more than one service to a single appointment. SmartBot handles multi-service bookings natively β€” when the multi-service flow is enabled in the business configuration, the Booking Agent allows the guest to choose more than one service in the conversation and does not redirect them to the Webstore. After selecting the first service, SmartBot asks whether the guest wants to add another, continuing until the guest indicates they are done.

Note: Multi-service (one guest, multiple services on the same appointment) is different from multi-guest (group or couple bookings). Multi-guest bookings are redirected to the Webstore β€” see Bookings that redirect to the Webstore below.

Add-ons

After service selection, SmartBot suggests complementary add-ons for the selected services and matches a provider for the combined booking. Add-ons are handled natively within the conversation β€” they are not redirected to the Webstore.

Service prerequisites

When a guest's chosen service has a prerequisite (a required prior service), SmartBot's behavior is governed by the Zenoti center setting Allow Prerequisites to be Booked with the Service:

Setting state What SmartBot does
Checked (allow booking together) SmartBot offers the prerequisite service in place of the originally requested service so it can be booked in the same conversation.
Unchecked (do not allow booking together) SmartBot redirects the guest to the Webstore with a message explaining that both appointments must be booked together.
Guest declines the offered prerequisite (Checked state) SmartBot redirects to the Webstore regardless.

Bookings that redirect to the Webstore

For deployment planning, here is the complete list of booking situations in which SmartBot directs the guest to the Webstore rather than completing the booking in the conversation:

  • Guest selects the Multiple services booking option in the service-selection prompt (when the multi-service flow is not enabled in the business configuration).
  • Guest types two or more service names in one message (same routing logic).
  • Guest selects a group or couple service (multi-guest bookings always redirect).
  • Guest's chosen service has a prerequisite, and Allow Prerequisites to be Booked with the Service is unchecked.
  • Guest declines an offered prerequisite (Allow setting is on).

Add-on selection is not a redirect β€” SmartBot handles add-ons natively.

Provider selection

Guests choose a provider preference:

  • Any β€” SmartBot selects any available provider.
  • Male β€” Filters to male providers.
  • Female β€” Filters to female providers.
  • Specific β€” The guest selects a specific provider by name.

For multi-service bookings, provider preference can be set per service, or a single provider can be selected for all services depending on the booking configuration.

Date and time selection

The guest selects a date. SmartBot retrieves available time slots from Zenoti and presents them for the guest to choose. For multi-service bookings, slots account for all selected services and the chosen provider preferences.

New guest profile creation

If no existing guest profile is found for the verified phone number, SmartBot collects the guest's name and any other required fields configured for the center, then creates a new guest profile in Zenoti. The profile is tagged with SmartBot as the referral source.

Deposit collection

When a service requires a deposit, SmartBot checks for deposit requirements and any saved payment card on file after the slot is reserved. The check evaluates both conditions together:

  • If a deposit is due, SmartBot prompts the guest for payment before confirming the appointment.
  • If no deposit is due but the center requires a card on file and the guest does not have one saved, SmartBot prompts the guest to add a card.
  • If neither a deposit nor a card on file is required, SmartBot proceeds directly to confirmation.

Two deposit configurations on the underlying Zenoti service are supported: a fixed monetary amount and a percentage of the service price. SmartBot reflects whichever model is configured. Guests can enter their card details inline through SmartBot during deposit collection; a previously saved card is not required. Deposit charges are processed through Zenoti's existing payment processing system. See Deposit collection for the full deposit flow, including no-show prevention rationale.

Confirmation

SmartBot holds the selected slot, collects any required deposit or card on file, and then confirms the appointment. The booking is recorded in Zenoti with SmartBot as the booking source. The guest receives a confirmation message.

Cancellation during booking

If a guest changes their mind and wants to cancel before confirmation, they can ask to cancel at any point. SmartBot can also cancel an existing appointment during the booking flow using the configured cancellation reasons from your organization.

Tips

  • Enable the Booking flow in General Settings to make this flow available to guests.
  • Configure service prerequisites in Zenoti so SmartBot can enforce them during booking.
  • Review the Inbox and Analytics panels to monitor booking completion rates and identify where guests drop off.
  • When multi-service booking is enabled, verify that provider availability spans the combined duration of all services a guest might select together β€” gaps in availability can cause the conversation to offer no slots.
  • For centers that require deposits, ensure that deposit rules are configured in Zenoti before enabling booking through SmartBot. Guests who reach the deposit step without a configured rule will not be able to complete their booking.

Troubleshooting

Guests report that Quick Book is not being offered even though they have a previous appointment. Quick Book is controlled by a business-configuration flag. Verify that Quick Book is enabled in your organization's business configuration. If the flag is enabled and the issue persists, confirm that the guest's previous booking is recorded against the same phone number they are using in the current conversation.

Guests are redirected to the Webstore for a service that should be bookable in the conversation. Check whether the service has a prerequisite configured in Zenoti. If Allow Prerequisites to be Booked with the Service is unchecked for that center, SmartBot will always redirect when a prerequisite is detected. Review the center setting and update it if the prerequisite should be bookable alongside the main service.

The deposit step appears but the guest cannot complete it. Confirm that the deposit rule for the service is configured correctly in Zenoti β€” both the amount or percentage and the payment method settings. Also verify that the center's payment processing is active. If the guest is entering card details inline and receiving an error, the issue is likely with the payment configuration rather than SmartBot itself.

No available time slots are returned after the guest selects a date. Ensure that providers are scheduled and available for the selected service on that date in the Appointment Book. For multi-service bookings, check that the combined duration of selected services fits within an available block. If availability exists in the Appointment Book but SmartBot returns no slots, check that the booking flow is enabled for the center and that the service is active in the Zenoti catalog.

SMS guests are not receiving the OTP for identity verification. OTP delivery depends on the SMS channel being active for the center and the guest's phone number being reachable. Verify that the SMS channel is enabled in the center's SmartBot settings. If the number is correct and the channel is active, the guest should attempt the flow again β€” delivery delays can occur due to carrier routing.

Was this article helpful?
Your feedback helps us improve our documentation.