SmartBot overview
SmartBot is Zenoti's AI-powered conversational platform that lets guests book appointments, get answers to common questions, and manage their bookings through web chat, SMS, and IVR/voice channels. SmartBot uses specialized AI agents to handle guest interactions automatically and transfers conversations to human agents in ezConnect when needed.
On this page
- Before you begin
- Getting started
- How it works
- Supported channels
- AI agents
- Appointment booking
- Guest identification and profiles
- Multi-location routing
- Abandoned booking recovery
- HyperConnect voice integration
- Key features
- Configure SmartBot β Prompts, FAQs, Bot Settings
- Inbox
- Analytics
- Usage metrics
- Call logs and voicemail
- Restricted word alerts
- Agent handover
- Manage upcoming appointments
- Admin console panels and access
- Related articles
Before you begin
To use SmartBot, you need:
- An active Zenoti organization with SmartBot provisioned.
- A SmartBot admin role: Org Admin (Owner or Admin with organization view) or Center Admin (Owner, Admin, or Manager with center view) for settings access.
- Staff roles (Receptionist, Studio Coordinator, Therapist) can view the Analytics, Inbox, and Call Logs panels but cannot change settings.
- SmartBot panel access follows your Zenoti security role. The SmartBot panels are security objects within those roles, and Zenoti grants them by default to the standard roles. For existing organizations, the role permissions SmartBot needs are added for you; see SmartBot Role Permissions β Existing Organization Back-fill.
Getting started
The SmartBot admin console is a separate web application provided by Simplified, a Zenoti technology partner. The customer-facing chat widget is delivered as a JavaScript embed that you place on your business website β these are two different surfaces.
Sign in to the admin console
- In a browser, go to https://smartbotneo.simplified.io.
- Enter the Account name that appears in your Zenoti URL (the same string you use to log in to Zenoti).
- Sign in with your Zenoti credentials.
You do not need a separate SmartBot password β authentication reuses your Zenoti login.
What you can configure in the admin console
The SmartBot admin console lets you configure and monitor all aspects of the SmartBot experience:
- General Settings β Enable booking, cancellation, and rescheduling flows; configure center-level SmartBot behavior including Quick Book activation, multi-service flow, and call center number support.
- FAQs β Build and maintain the knowledge base that SmartBot draws on to answer guest questions. Accessible via the Settings icon in the left panel navigation.
- Prompts β Customize the conversational text that drives the bot through booking, cancellation, and rescheduling workflows. Accessible via the Settings icon in the left panel navigation.
- Web Bot Settings β Configure the customer-facing chat widget appearance (colors, logos, position, display mode) and generate the embed script. Accessible via the Settings icon.
- SMS / IVR channel configuration β Enable SMS and voice/IVR channels per center and configure deployment scenarios (missed-call SMS, IVR redirect, direct distribution).
- Inbox β Review all guest conversations across channels; monitor agent handovers and abandoned conversations.
- Analytics β Track booking, cancellation, and rescheduling trends across locations and channels.
- Call Logs β View inbound call records and voicemail transcriptions (when call center flow is enabled).
- Usage Metrics β Monitor daily SMS and message usage per center.
For organization-level communication settings, see the Configurations category.
Recommended setup order
Once signed in, work through configuration in this order so each step has the inputs it needs from the prior step:
- General Settings β Enable the booking, cancellation, and rescheduling flows and configure center-level behavior.
- FAQs β Build the knowledge base using the Settings icon to access FAQ Management.
- Prompts β Customize conversational text via the Settings icon β Prompt Management.
- Web Bot Settings β Configure widget appearance via the Settings icon and generate the embed script for your website.
- Test β Send a test conversation through the live SmartBot to verify flows end-to-end before publishing.
Optionally, also configure:
- Call Center Number Support if you operate multiple centers and want a single phone number.
- SMS Bot trigger scenarios (missed-call SMS, IVR redirect, direct distribution) that fit your communication strategy.
How it works
When a guest starts a conversation on any supported channel, SmartBot classifies their intent and routes the request to the appropriate specialized AI agent. Each agent handles a specific task β booking, cancellation, rescheduling, appointment management, service browsing, or FAQ answers. If the AI cannot resolve the request, or if the guest asks to speak with a person, SmartBot transfers the conversation to a human agent in ezConnect with full context preserved.
Settings operate at two levels. Organization-level settings control the FAQ knowledge base, default prompts, and geographic regions. Center-level settings control which channels are active, booking flow behavior, and center-specific prompt overrides.
Supported channels
SmartBot supports three communication channels. You can enable any combination per center.
- Web chat widget β A JavaScript widget embedded on your website. You generate the embed script in the Web Bot Settings panel and paste it into your site. You configure the widget appearance (theme color, header logo, chat logo, header text, font family, font color, position) and choose between three display modes: Minimized (collapsed with a greeting), Expanded (full chat window open), or Icon-only (a floating button only). For Minimized mode you can additionally configure the Widget button text and Widget greeting text.
- SMS β Two-way SMS. Responses stay within a 1,600-character limit, and long lists are paginated at five items per page with a See More option. The first SMS SmartBot sends a guest in a new conversation carries an opt-out notice telling the guest to reply STOP to unsubscribe from the bot's messages; later messages in the same conversation do not repeat the notice. If a guest sends another SMS while SmartBot is still preparing a reply, SmartBot asks them to wait for the previous response before continuing. Failed outbound SMS deliveries are retried up to two times. The SMS Bot supports three deployment scenarios β see Supported channels β SMS Bot scenarios below.
- IVR / Voice β Phone-based interactions where guests call a dedicated number. The IVR system handles inbound calls through a phone tree and can fall back to SMS for tasks that require typed responses. Voicemails are recorded and retained for one year.
Each center uses one of three call-handling options:
| Option | What it does |
|---|---|
| IVR only | Inbound calls are answered by a phone tree. Unanswered calls do not start an SMS conversation. |
| Missed call only | No phone tree. When an inbound call goes unanswered, SmartBot starts an SMS conversation with the caller. |
| IVR with missed call | Combines both β the phone tree answers the call, and an unanswered call also triggers the SMS conversation. |
For session-related timers β including the abandoned-booking inactivity threshold β see the channel-specific values listed under Abandoned booking recovery below. SmartBot keeps a conversation's state for a 30-minute conversation window across all channels; this is separate from the abandoned-booking timer.
Supported channels β SMS Bot scenarios
The SMS Bot can be deployed in three scenarios. They are not mutually exclusive β many businesses use a combination.
- Scenario A β Missed-call SMS. When a guest calls your business and the call goes unanswered (out-of-hours or busy staff), an automatic SMS is sent to the caller's number. No setup beyond enabling the missed-call flow type is required.
- Scenario B β IVR redirect. A guest calls your business and is offered an option to receive an SMS with the SmartBot. Your business's main phone number forwards to a Twilio number provisioned by SmartBot; an IVR prompt offers the SMS option; the caller is redirected to text the SmartBot number. Setup includes call forwarding, IVR prompt recording, and redirect configuration.
- Scenario C β Direct distribution. You publish the SmartBot number directly via appointment confirmations, reminders, QR codes at the front desk, on product displays, and on receipts. QR codes also enable per-surface usage tracking.
AI agents
SmartBot uses six specialized AI agents that work together through an orchestration layer:
- Booking Agent β Guides guests through the full appointment booking flow, including service selection, provider preferences, date and time selection, and deposit collection.
- Cancellation Agent β Processes appointment cancellations, presenting available cancellation reasons from your organization's configuration.
- Reschedule Agent β Handles date, time, or provider changes for existing appointments.
- Manage Appointments Agent β Lets guests view their upcoming appointments and take action on them.
- View Services Agent β Provides information about available services, pricing, and durations.
- Support Agent β Answers guest questions using the knowledge base and handles general inquiries.
SmartBot classifies every guest message and routes to the correct agent automatically. If a guest asks an unrelated question while a booking is in progress, the Support Agent answers and then returns control to the Booking Agent to continue where it left off.
Appointment booking
The appointment booking flow identifies the guest, helps them select services and providers, finds available time slots, and collects deposits when required. Identity verification varies by channel: on the SMS Bot, the channel itself supplies the guest's phone number, so no extra step is needed for guest lookup; on the Web Bot, SmartBot prompts the guest to enter their phone number for guest-management flows that require identification.
When the guest picks a time, SmartBot holds that slot while it finishes collecting any remaining details, then confirms the appointment.
The booking flow supports:
- Quick Book β Offers returning guests the option to rebook the same service with the same provider. Quick Book is offered whenever Quick Book is activated for the organization and the guest has a previous booking pattern to repeat. It is not gated by per-service catalog availability or per-provider availability at the point the offer is made. Guests who accept skip service and provider selection and proceed to date and time selection.
- Multi-service bookings β Guests can add multiple services to a single appointment in the same conversation. SmartBot handles this natively when the multi-service flow is enabled β guests are not redirected to the Webstore for multi-service single-guest bookings.
- Add-on suggestions β After service selection, SmartBot suggests complementary add-ons and matches a provider for the combined booking. Add-ons are handled natively; no Webstore redirect.
- Service prerequisites β When a service has a prerequisite, the center setting Allow Prerequisites to be Booked with the Service controls SmartBot's behavior. If the setting is checked, SmartBot offers the prerequisite service so it can be booked in the same conversation. If the setting is unchecked β or if the guest declines the offered prerequisite β SmartBot redirects the guest to the Webstore with a message explaining that both appointments must be booked together.
- Provider gender preference β Guests can request Any, Male, Female, or a Specific provider.
- Group / couple service redirection β Services that require multi-guest booking (group or couple) are redirected to the Webstore. (This is different from multi-service: a single guest booking multiple services is handled natively by SmartBot.)
- Deposit collection β When a service requires prepayment, SmartBot prompts the guest for payment inline. Guests can securely input their credit card details through SmartBot's interface, or pay with a saved card on file. Deposits use Zenoti's existing payment processing system.
Payment checks before confirmation
After SmartBot holds the slot, it checks what payment details the appointment needs before it confirms:
- A deposit is due β SmartBot collects the deposit. The guest can pay with a card already saved on their profile, or use a secure link to enter card details.
- No deposit is due, but the center requires a card on file β SmartBot checks whether the guest already has a saved card. If they do not, it sends a secure link so the guest can add one.
- Neither applies β SmartBot goes straight to confirming the appointment without asking the guest for payment.
Booking flows 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:
| Trigger | Why redirect happens |
|---|---|
| Guest selects the Multiple services booking option in the service-selection prompt | Native multi-service booking is enabled per center; when it is off, SmartBot routes the guest to the Webstore. |
| Guest types two or more service names in one message | Same routing logic β SmartBot recognizes the multi-service intent and offers the Webstore URL. |
| Guest selects a group or couple service | Multi-guest bookings always redirect; SmartBot does not support multi-guest natively. |
| Guest's chosen service has a prerequisite, and Allow Prerequisites to be Booked with the Service is unchecked | The two appointments must be booked together on the Webstore. |
| Guest declines an offered prerequisite (Allow setting is on) | Same outcome β SmartBot routes to the Webstore. |
Add-on selection (post-service-selection upsell) is not a redirect β SmartBot handles it natively.
Deposit collection β what it does and why
Deposit collection is a no-show / last-minute-cancellation prevention mechanism. Three business benefits:
- Secures client commitment with an upfront deposit.
- Minimizes revenue loss from no-shows and cancellations.
- Improves cash-flow predictability.
You configure two deposit models on the underlying Zenoti service: flat-rate (a fixed monetary amount) or percentage-based (a percentage of the service price). SmartBot reflects whichever model is configured on the service.
SmartBot does not run a payment gateway of its own. Deposit charges go through the same payment processing that handles center-side appointments and Webstore checkouts.
SMS service-list pagination
The SMS Bot lists services and slots five items per page. Web Bot lists show five items with a Show All option. If you have a long service catalog, order it so that the most commonly booked services appear in the first five SMS results β most guests will not page through multiple screens.
Guest identification and profiles
Most SmartBot flows need to know which guest they are talking to. SmartBot works with Zenoti guest profiles directly β it searches, retrieves, creates, and updates them as the conversation progresses.
- Phone number verification β SmartBot sends a one-time password to the guest's phone number and asks the guest to enter the code before it shows or changes appointment information.
- Profile lookup β SmartBot searches for a matching guest profile by phone number across your centers. If more than one profile shares the same number, SmartBot lists the matching profiles and asks the guest to select theirs.
- New guest creation β If no profile matches, SmartBot collects the guest's details and creates a profile. Each center decides which of these details are mandatory: email, address, date of birth, gender, country, state, city, pin code, nationality, primary employee, and referral source.
- Referral source β Guests created through SmartBot are recorded with SmartBot as the referral source, so you can report on how much new-guest volume the bot brings in.
- Saved cards β When a service requires a deposit, SmartBot checks for a card already saved on the guest's profile before asking for card details.
Availability: Blacklist handling is enabled per deployment. When it is on, phone numbers can be checked against, added to, and removed from a blacklist, and SmartBot ignores incoming messages from a blacklisted number without replying.
When you add a phone number to the blacklist, enter it with its country code β for example, +14155550142. A number submitted without a country code is rejected with a validation error. Removal accepts both formats, so numbers saved before the country-code requirement was introduced can still be cleared from the list.
Multi-location routing
SmartBot offers two distinct mechanisms for routing guests across multiple centers. They serve different purposes:
- Call Center Number Support (CCNS) β A single phone number that serves all of your centers. After a guest contacts the number, SmartBot lists centers and the guest selects their preferred location via SMS. CCNS supports two configuration modes:
- Without regions β guests select a center directly from the list.
- With regions β guests first select an admin-defined region (e.g., New York or Vancouver β these are arbitrary geographic labels you choose, not proximity calculations), then select a center within that region. CCNS supports up to 25 centers per configuration. If a guest selecting a center has an existing appointment with that center, SmartBot automatically adds a Reschedule option to the menu. Configure CCNS from Settings β General Settings.
- ZIP-code search proximity β A separate mechanism used by the Booking Agent to identify the closest center to a guest based on their ZIP code. The default search radius is 30 miles (configurable; supports miles or kilometers). This is proximity-based center selection and is independent of CCNS.
You choose which strategy fits your organization: named regions when your centers map to recognizable areas that guests will know by name, or ZIP-code proximity when you want SmartBot to pick the nearest center for the guest. Regions support the full set of maintenance actions β create a region, assign centers to it, add or remove centers later, and delete the region when it is no longer needed. Zones are a separate geographic grouping mechanism that you can maintain alongside regions.
Abandoned booking recovery
When a guest starts a booking but goes inactive, SmartBot sends an SMS recovery message containing a link to your Webstore and instructions to restart the conversation. This feature is enabled by default for all SmartBot deployments β no setup required.
The inactivity threshold is channel-specific:
| Channel | Default inactivity threshold |
|---|---|
| Web Bot | 10 minutes |
| SMS Bot | 30 minutes |
Both defaults are environment-configurable per deployment, so your tenant may use different values.
The recovery message tells the guest they can reply Hi to restart the conversation, or use the included Webstore URL to book online. A booking abandoned on the Web Bot receives a distinct message that first introduces the assistant by your organization name and bot name, notes that the guest tried to book on the website, and then offers the same two options. Recovery messages are sent only when the conversation has a valid phone number to reply to; abandoned booking conversations are also flagged in the Inbox under the corresponding filter.
If your organization routes guests through a shared call center number, SmartBot sends the recovery message only after the guest has selected their center. A conversation abandoned before center selection is skipped without a message, because SmartBot has no center Webstore to point the guest to.
Note: The 30-minute conversation window is a separate concept β that is how long SmartBot keeps the conversation's state, and it applies to all channels. The 10-minute (Web) / 30-minute (SMS) values above govern when the SMS recovery message is sent, not when the conversation state expires.
HyperConnect voice integration
If your organization uses HyperConnect, its AI voice agent can bring SmartBot into a live call. When the caller wants to book an appointment, the voice agent checks whether SmartBot is enabled for the center and starts a SmartBot interaction for that call. Because the interaction started from a call rather than from a guest-initiated SMS, it is not counted against your SMS usage.
For HyperConnect voice and messaging features, see HyperConnect overview.
Key features
- Three channels, one assistant β Web chat widget, SMS, and IVR/voice, enabled per center in any combination.
- A specialized AI agent for each task β Booking, cancellation, rescheduling, appointment management, service browsing, and FAQ answers, with automatic routing between them.
- End-to-end booking β Guest identification, service and provider selection, slot search, Quick Book, multi-service bookings, add-ons, prerequisite handling, and deposit collection.
- Knowledge base answers β FAQ entries with related questions and per-center publishing scope, so guests get an answer without waiting for staff.
- Agent handover β Transfers the conversation to a human agent in ezConnect with full context when the guest asks for a person or the AI cannot resolve the request.
- Conversation review β The Inbox shows every conversation across channels, filtered by user type, channel, and handover status.
- Reporting β Analytics for booking, rescheduling, cancellation, user, and conversation trends, plus usage metrics for SMS and voicemail volume.
- Multi-center routing β Call Center Number Support and ZIP-code proximity search direct guests to the right center.
- Recovery and safety β Abandoned booking recovery SMS, restricted word alerts, and personal-information redaction in analytics.
Configure SmartBot β Prompts, FAQs, Bot Settings
The admin console exposes three primary customization areas, each accessible from its own panel.
Prompts
Prompts are the conversational text that drives the bot through its workflows. They are organized by:
- Workflow β Book, Cancel, and Reschedule, each maintained separately.
- Channel β SMS and Web prompts are configured independently within a workflow, selected via a channel dropdown.
- Language β Each channel keeps a prompt set per language, so an organization that serves guests in more than one language maintains one set per language.
Prompts are maintained at the organization level as defaults, and a center can override them with its own text.
Within a workflow, each step exposes one or more fields:
- Editable (white) fields β admin-customizable text.
- System-controlled (gray) fields β disabled in the UI because SmartBot needs their literal values to advance the guest through subsequent steps.
Prompt text can include variables written in curly braces, which SmartBot replaces with the live value when it sends the message. Zenoti checks the variables you enter against the default prompt text and rejects a prompt that contains a variable it does not recognize.
When you edit a prompt step, two save actions are available:
- Save β commits the change and previews the interaction at the current step. The preview area does not auto-scroll to the step you edited; locate it manually in the preview.
- Save & Next β commits and advances to the next step.
You can jump to a specific step within a workflow from the left-panel workflow list.
FAQs
The FAQ panel manages the bot's knowledge base. Each FAQ entry has these fields:
- Category β used for browsing and category-based sorting.
- Question β the phrasing.
- Same answer for Web Bot and SMS Bot β checkbox. When on, the answer applies to both channels. When off, you author a separate Web answer and SMS answer.
- Related questions β up to five synonyms or alternative phrasings (for example, Group bookings, group appointments, and group services can all map to the same FAQ). The bot treats these as semantically equivalent for retrieval.
- Publish scope β This center (visible only to guests of the current center) or All centers (visible to guests across all your centers).
You can add, edit, and delete entries one at a time, or upload a batch of FAQs from an XLSX file β Zenoti validates the file against the required fields before importing it. At the organization level, you can also generate a starter set of FAQs automatically, then review and edit them before publishing.
FAQ changes are not live until you deploy them. After adding, editing, or deleting entries, deploy the FAQ set to publish it to the knowledge base SmartBot answers from.
Note: Your organization's answer engine determines how the FAQ panel matches guest questions to entries. Organizations on the knowledge base engine β the current engine β match a guest's question to an entry by meaning rather than by exact wording, which is why Related questions improve how often the bot finds the right entry.
Inbox-to-FAQ feedback loop
Conversations that end in agent handover (because the bot could not answer) are surfaced in the Inbox under the Agent Handover filter. Reviewing those conversations periodically gives you a stream of real questions you can convert into new FAQ entries β closing the loop between unanswered questions and the knowledge base.
Bot Settings (Web Bot appearance)
The Web Bot Settings panel configures the chat widget your guests see on your website:
- Theme color (palette or hex code), Font color (palette or hex), Font family (dropdown of Google Fonts).
- Header logo and Chat logo uploads.
- Header text β your business name or custom text.
- The bot's display name β the name guests see for the assistant in the conversation, and the name used in the Web Bot abandoned booking message.
- Widget position β left or right.
- Widget mode β Minimized, Expanded, or Icon-only.
- For Minimized mode only: Widget button text and Widget greeting text.
You can also turn the widget's notification sound on or off. Whichever display mode you choose, guests can expand the widget to open the full chat window and collapse it again during the conversation.
When you save these settings, the panel generates a JavaScript embed script. Copy the script into your website to publish the widget. The widget then renders on your site.
Note: Bot Settings access requires both admin privileges AND that the web channel is enabled on at least one of your centers. If the web channel is not enabled on any center, the Bot Settings panel will not be reachable. The check recognizes the web channel whether it is turned on for the organization as a whole or only for individual centers, so an organization that runs the chat widget at center level still reaches the panel.
Inbox
The Inbox is a single view of all conversations across all SmartBot channels. Use it to triage active conversations, monitor handovers, and drill into past conversations.
You can search the Inbox by guest name or phone number. Two filter dimensions narrow the list:
| Dimension | Values |
|---|---|
| Users | New (no Zenoti profile yet) Β· Existing (matched Zenoti profile) Β· Unknown (web-channel guest who did not provide contact information) |
| Conversations | SMS Β· Web Β· Agent Handover Β· All |
Org Admins can also narrow the Inbox to a single center. Each conversation row shows the guest's name, the phone number, the channel, the most recent message, whether the conversation was handed over to a human agent, and whether the guest is new to your organization. Rows are ordered by most recent interaction, and the Inbox loads up to 50 conversations at a time.
When SmartBot transfers a conversation to a human agent, the Inbox shows an Agent Handover popup with an option to switch to ezConnect (where the human agent picks up the conversation with full context).
Analytics
The Analytics dashboard gives you cross-location, cross-channel, cross-timeframe performance visibility in a single view. Two tabs:
| Tab | Sub-tabs | What it shows |
|---|---|---|
| Scheduling | Bookings Β· Reschedules Β· Cancellations | Time-series trend data for the three primary booking-flow KPIs. |
| Conversations | Users Β· Conversations | Time-series trend data for unique users and total conversations. |
Three filter dimensions apply across both tabs:
- Location β per-center or all-centers.
- Date range β Last 7 days / Last 30 days / Last 60 days / Custom.
- Platform / Channel β SMS / Web / All.
For example, to compare a single center's performance on the SMS Bot versus the Web Bot last month, set Location to that center, Date range to Last 30 days, then toggle Channel between SMS and Web on the Conversations tab.
Alongside the trend charts, analytics reports total users, total conversations, total utterances (individual guest messages), and the keywords guests used β split into keywords SmartBot matched to an answer and keywords it could not match.
Act on those numbers rather than reading them alone:
- Unmatched keywords are your FAQ backlog. Track the same keyword across two consecutive periods; if its unmatched count is rising, add an FAQ entry for it (or add it as a Related question on an existing entry) and deploy.
- Utterances per conversation shows how much back-and-forth a task takes. If utterances rise while bookings stay flat, review the prompts for the step where guests get stuck.
- Bookings versus cancellations on the same date range tells you whether the bot is generating net new appointments or churning existing ones.
Note: Analytics is computed from conversation data with personal information removed. Guest names, phone numbers, one-time passwords, service types, dates, times, and prices are redacted before the data is aggregated, so analytics figures cannot be traced back to an individual guest. Use the Inbox when you need to review a specific conversation.
Usage metrics
Usage metrics record SmartBot volume per center per day, so you can see how much traffic the bot handles and where that volume is concentrated. The following counts are tracked:
- Incoming SMS
- Outgoing SMS
- Voicemails recorded
- Total call duration, in seconds and in minutes
- Voicemail email notifications sent
Query usage by date range, filter to a single center, or view the organization total with a per-center breakdown.
Use the ratio between the counts, not the counts alone. If outgoing SMS is climbing much faster than bookings, review your prompt lengths and the order of your service catalog β paginated lists cost extra messages per conversation. A center with high call duration and high voicemail counts is a candidate for enabling the missed-call SMS option so callers are answered instead of queued.
Call logs and voicemail
When a center handles calls through SmartBot and missed-call handling is configured, SmartBot records the voicemail left by callers it cannot answer live and lists those recordings in the Call Logs panel.
- Recording β Each voicemail is stored with its call details and kept for one year, after which it is deleted automatically.
- Transcription β Voicemails are transcribed automatically. Each record shows the recording, its duration, the caller's details, the recording status, and the transcription status. If transcription fails, the record still holds the recording; only the transcript is missing.
- Email notification β When voicemail email notification is turned on for the center, SmartBot emails the recipients you configure with a link to the recording and the transcript, if one is available.
- Direct links β Call Logs supports opening a specific voicemail record directly from a link, so you can share a record with a colleague.
- Center and organization views β View voicemail records for one center or across the organization, and export the list.
Availability: The Call Logs panel appears only when the call center flow is enabled and missed-call handling is configured for the center.
Restricted word alerts
SmartBot watches conversations for restricted words. When it detects one, Zenoti sends an alert notification so the conversation can be reviewed. The alert identifies the restricted words that were detected, the message text they appeared in, the guest's phone number, and the organization and center the conversation belongs to. Use the Inbox to open the flagged conversation and decide whether to hand it to a human agent.
Agent handover
Agent handover transfers an in-progress conversation from SmartBot to a human agent in ezConnect. Two trigger conditions:
- Explicit guest request β the guest asks to speak to a person ("speak to staff", "agent please", or similar).
- AI-judged repeat question β the guest asks the same complicated question a second time without the bot having resolved it (a signal that the FAQ knowledge base did not answer the question).
When handover is triggered, two things happen at once:
- ezConnect receives a handover notification so the assigned human agent can pick up the conversation with full context preserved.
- The SmartBot Inbox displays a handover popup with an option to switch to ezConnect.
The guest sees one of two messages β either a Sorry message informing them of the transfer, or a confirmation that a staff member has been notified β depending on the configured handover prompt. After the handover, the guest can continue using SmartBot for unrelated questions in the same conversation.
For organizations without ezConnect, SmartBot provides a fallback in which it returns the business's contact information instead of transferring the conversation in-product.
For details on handling conversations handed over from SmartBot, see Handle SmartBot handover.
Manage upcoming appointments
The Manage Appointments Agent lets returning guests view and act on their upcoming appointments. The entry point is different on each channel:
- SMS Bot. The guest selects Manage upcoming appointments directly from the menu options. The SMS channel already knows the guest's phone number, so no extra phone-number capture is needed before showing appointments.
- Web Bot. The option is not on the initial menu. The guest first asks an appointment-related question in natural language ("What is my upcoming appointment?", "When is my next appointment?"). SmartBot then prompts for phone-number validation before displaying appointments β because the web channel does not inherently know the guest.
Each upcoming appointment is listed with its service, date, and time. After the guest sees their appointments, the bot offers to cancel or reschedule them (depending on whether the corresponding flows are enabled at the center) and offers a Manage another appointment option if more than one appointment is upcoming. If the guest has no upcoming appointments, the bot says so and offers to book a new one; if no guest profile matches, it offers the booking flow instead.
For appointment management in the front desk, see the Appointment Book category.
Admin console panels and access
SmartBot panels are organized into distinct work areas. Your access depends on your role:
| Panel | Org Admin | Center Admin | Staff |
|---|---|---|---|
| Analytics | Full access | Full access (own center) | View only |
| Inbox | Full access | Full access (own center) | View only |
| General Settings | Full access | Full access (own center) | No access |
| Bot Settings (Web Bot appearance) | Full access (web-enabled centers) | Full access (own center, web-enabled) | No access |
| Prompts | Full access | Full access (own center) | No access |
| FAQs | Full access | Full access (own center) | No access |
| Call Logs | Full access | Full access (own center) | View only |
| Usage Metrics | Full access | Full access (own center) | View only |
| SMS / IVR channel configuration | Full access | Full access (own center) | No access |
Note: Bot Settings access additionally requires that the web channel is enabled on the center. This is a real prerequisite β if the web channel is off, the Bot Settings panel will not be reachable even for admin users.
Role is not the only factor. Some panels appear only when the matching capability is configured for your organization or center:
| Panel | Additional condition for the panel to appear |
|---|---|
| Analytics | None β available to every signed-in user. |
| Inbox | None β available to every signed-in user. |
| General Settings | Admin privileges. |
| Bot Settings | Admin privileges, and the web channel enabled for the organization or on at least one of your centers. |
| Prompts | Admin privileges. |
| FAQs | Admin privileges. |
| Call Logs | The call center flow is enabled and missed-call handling is configured for the center. |
Note: For organizations on the current SmartBot version, the Prompts panel opens in a reduced view focused on the AI agent prompts, so fewer individual workflow steps are exposed for editing than in the step-by-step editor described under Prompts.