SmartBot AI agent capabilities
SmartBot's AI agents perform actions on behalf of guests by calling Zenoti services. This article describes the capabilities available to each agent and what each capability does.
Audience: Administrators understanding SmartBot's capabilities to configure flows, set expectations, and diagnose unexpected behaviors.
Before you begin
- No configuration is required for AI agent capabilities. They are built into SmartBot and activated based on which flows are enabled.
- To enable or disable specific flows (booking, cancellation, reschedule, manage appointments), use General Settings.
Capabilities available to all agents
Every SmartBot AI agent has access to a core set of capabilities regardless of the active flow:
- Answer FAQ questions β Searches the knowledge base for answers to guest questions. The knowledge base is consulted whenever the answer is not already present in the conversation β it is used for general business facts such as policies and procedures, but not for center hours or a specific service's price, duration, description, or availability (which are handled by dedicated service and availability lookups).
- Find regions β Retrieves the geographic regions configured for the organization.
- Find locations β Retrieves center locations based on region or proximity.
- Transfer to human agent β Initiates agent handover to a human agent in ezConnect.
- Update conversation configuration β Updates the active session configuration mid-conversation.
- Get agent instructions β Retrieves context-specific instructions for the active agent.
- Provide Webstore link β Retrieves and shares the center's Webstore URL with the guest.
Booking Agent capabilities
In addition to the core capabilities, the Booking Agent can:
- Send OTP β Initiates a one-time password to the guest's phone number for identity verification.
- Verify OTP β Validates the OTP code entered by the guest.
- Retrieve guest details β Fetches the guest profile by phone number. If multiple profiles match the same number, the agent presents the list so the guest can select the correct one.
- Check for Quick Book β Checks the guest's previous booking history to offer Quick Book.
- Browse services β Retrieves the service catalog with category and subcategory filtering, paginated at five items per page.
- Check service prerequisites β Validates that required prerequisite services have been completed before booking.
- Retrieve service add-ons β Fetches available add-ons for selected services.
- Find available providers β Retrieves providers available for a service, date, time, and gender preference.
- Check available slots β Fetches available appointment time slots for the selected service, date, and provider.
- Create guest profile β Creates a new Zenoti guest profile with phone number, name, and any required fields.
- Update guest profile β Updates an existing guest profile (for example, adding a date of birth).
- Hold a slot β Places a temporary hold on the selected appointment slot.
- Check card on file β Verifies whether the guest has a saved payment card and whether a deposit is required for the selected service. This check runs after the slot hold is confirmed.
- Confirm appointment β Confirms the held slot and completes the booking.
Note: Deposit checking is performed as part of the card-on-file check after a slot hold succeeds. There is no separate deposit-checking step.
Cancellation and Reschedule Agent capabilities
The Cancellation and Reschedule Agents use a subset of guest and appointment tools from the Booking Agent, focused on:
- Verifying guest identity (OTP).
- Retrieving existing appointments.
- Processing cancellations with configured cancellation reasons.
- Rescheduling to new dates, times, or providers.
Manage Appointments Agent capabilities
The Manage Appointments Agent can:
- Verify guest identity β Uses OTP for identity verification.
- Retrieve guest appointments β Fetches the guest's upcoming appointments from Zenoti.
- Display appointment details β Formats and presents appointment information (service, date, time) to the guest.
- Route to cancellation β Hands off to the Cancellation Agent when the guest selects cancel.
- Route to reschedule β Hands off to the Reschedule Agent when the guest selects reschedule.
How the Booking Agent guides a guest through appointment booking
When a guest starts a booking conversation through the web chat widget or SMS, the Booking Agent moves through four phases. The agent uses the capabilities listed above at each phase to complete the booking.
Phase 1: Identify the guest
The agent asks for the guest's phone number, then sends an OTP to verify identity. Once the guest enters the correct code, the agent retrieves the guest profile. If the phone number matches multiple profiles, the agent presents the list so the guest can select the correct one.
If no profile is found, the agent asks for the guest's name and creates a new guest profile before continuing.
The agent also checks whether the guest has a previous booking on record. If so, it offers a Quick Book option that pre-fills the same service, provider, and time preferences β allowing the guest to skip service selection and proceed directly to date and slot selection.
Phase 2: Select a service
If the guest does not use Quick Book, the agent presents the service catalog. Services are displayed in groups by category and subcategory. The agent checks whether any selected service has a prerequisite (for example, a consultation that must be completed before a treatment). If a prerequisite has not been met, the agent informs the guest before continuing.
After a service is selected, the agent offers any available add-ons. The guest can choose to add them or decline.
Note: If the organization has multi-service booking enabled and the selected service qualifies, the guest can add more than one service to the appointment. When multi-service booking is not enabled, guests selecting a group service are redirected to the Webstore.
Phase 3: Select a provider, date, and time
The agent retrieves available providers for the selected service and any guest preferences (such as gender). The guest selects a preferred provider or requests any available provider.
The guest then selects a date, and the agent fetches available time slots. Once the guest selects a time, the agent places a temporary hold on that slot to prevent it from being taken by another booking.
Phase 4: Confirm and complete
If the selected service requires a deposit, the agent checks whether the guest has a saved payment card as part of the same step. If a card is on file, the deposit is collected automatically. If not, the guest is prompted to provide payment details.
Once any deposit is handled, the agent confirms the appointment. The guest receives a confirmation message with the appointment details.
Tip: At any point during the booking flow, if a guest asks an unrelated question β such as a question about services, pricing, or policies β SmartBot answers using the knowledge base and then returns to the active booking flow. For details on handling conversations handed over from SmartBot, see Handle SmartBot handover.
Agent handover
If a guest asks to speak with a person at any point in a conversation, any SmartBot AI agent can initiate agent handover. The conversation is transferred to a human agent in ezConnect, and the guest is notified of the transfer.
For details on handling conversations handed over from SmartBot, see Handle SmartBot handover.
Tips
- To help guests reach the right center quickly, configure regions and zones so the Booking Agent can present relevant locations based on the guest's area. See Regions and zones.
- If a guest reports that Quick Book is not being offered, verify that the guest has a completed booking in Zenoti. Quick Book is only available when a previous booking record exists for that guest.
- For services that require a prerequisite, ensure the prerequisite service is recorded in the guest's profile before the guest attempts to book the dependent service. If the prerequisite check fails, the agent will inform the guest and cannot proceed with that service.
- If your organization offers multi-service bookings through the web chat widget, confirm that the multi-service booking option is enabled in your center's booking configuration. When it is not enabled, guests selecting multiple services are redirected to the Webstore.
- Use the knowledge base to answer common guest questions automatically during any conversation, including mid-booking. Keeping FAQ answers current reduces the likelihood of a guest requesting agent handover for routine questions. See Manage FAQs in SmartBot.
Troubleshooting
The Booking Agent does not offer Quick Book even though the guest has booked before. Quick Book requires a completed booking record associated with the guest's phone number. Confirm that the guest's profile is linked to the phone number they used in the conversation, and that at least one previous appointment is marked as completed in Zenoti.
The agent is not showing add-ons after a service is selected. Add-ons are only offered when they are configured for the selected service in Zenoti. Verify that the service has add-ons defined and that the add-ons are active. If no add-ons are configured, the agent skips that step automatically.
The agent is not checking prerequisites before allowing a service to be booked. Prerequisite checks depend on the prerequisite being defined for the service in the service catalog. If a prerequisite service is not configured, the agent will not prompt the guest. Review the service's prerequisite settings in your Zenoti service catalog.
Agent handover is not completing β the guest reports the conversation was not transferred. Confirm that ezConnect is provisioned and active for your organization and that the center has agent handover enabled. If the transfer fails, the guest remains in the SmartBot conversation. See Agent handover for configuration requirements.
The guest receives no OTP during identity verification. Verify that the SMS channel is enabled for the center where the guest is interacting. OTP delivery depends on SMS being active. If SMS is disabled for that center, the agent cannot send the verification code. See SMS channel.