ZenotiHelp

Service Search β€” Multi-Phrase Search and Variant Handling

ZTZenoti Docs Team Updated November 3, 2026 8 min readGuide

SmartBot's service search uses an array of search phrases β€” rather than a single keyword β€” to find the right service even when a guest uses terminology that differs from how your center has named it. This article explains how to write effective search phrase arrays, when to use the variant flag, and how the catalog filter prevents parent variant containers from appearing as bookable services.

Audience: SmartBot administrators and prompt authors who configure or tune the AI agent's booking behavior.

Before you begin

  • Your organization must have SmartBot enabled with at least one center configured for conversational booking via the web chat widget or SMS channel.
  • You must have access to the SmartBot admin console to review or adjust prompt and booking configuration.
  • Familiarity with how SmartBot handles the booking flow is recommended. For background, see How SmartBot AI agents work.

Steps

Understand the search phrase array

When a guest asks to book a service, SmartBot searches the Zenoti service catalog using an array of search phrases rather than a single text string. This array allows the AI agent to cast a wider net across alternate names, common misspellings, trade names, and singular or plural forms of a service name β€” so a service is found even when your center uses different terminology than the guest does.

Each array represents one service. The array contains:

  • The service name as it appears in your center's catalog (primary phrase)
  • Synonyms and alternate names guests commonly use
  • Trade names or brand-specific names for the treatment
  • Alternate spellings, abbreviations, or shorthand
  • Singular and plural forms where they differ meaningfully

The array supports up to 6 phrases per service.

Note: A single search phrase array must not mix phrases for different services. If a guest mentions two services in the same message, SmartBot makes a separate search call for each service, each with its own array.

Important: Keeping each array scoped to one service is essential for accurate search results. Mixing phrases from different services in a single array will cause irrelevant matches and degrade booking accuracy.

Worked example: A guest says "I'd like to book a deep tissue and a hot stone." SmartBot makes two separate search calls:

  • First call β€” search phrases: ["deep tissue massage", "deep tissue", "deep muscle massage", "firm pressure massage"]
  • Second call β€” search phrases: ["hot stone massage", "hot stone therapy", "lava stone massage", "heated stone massage"]

Each call targets exactly one service. The arrays do not share phrases.

Construct effective search phrase arrays

Follow these guidelines when authoring or reviewing the phrases the AI agent uses:

  1. Start with the catalog name. The first phrase in the array should match or closely approximate the service name in your Zenoti service catalog. This maximizes the chance of an exact match on the first attempt.

  2. Add guest-facing synonyms. Think about how guests describe the service when they call or message β€” not how it is labeled internally. For example, guests may say "facial" when the catalog lists "Advanced Skin Treatment."

  3. Include trade or brand names if relevant. If your center offers services associated with a product line or technique with a well-known name, include that name as a phrase.

  4. Account for singular and plural forms. Include both "eyebrow wax" and "eyebrow waxing" if guests use both.

  5. Limit the array to 6 phrases. Beyond 6 phrases, coverage gains are minimal and the array becomes harder to maintain.

  6. Keep each phrase concise β€” typically 2 to 5 words. Very long phrases are less likely to match catalog entries.

Handle multiple services in one guest message

When a guest mentions more than one service in a single message, SmartBot issues a separate service search call for each mentioned service. Each call uses its own independent search phrase array.

Do not combine phrases for Service A and Service B into one array. The search engine matches across all phrases in an array as though they all describe the same service; mixing services produces ambiguous or incorrect results.

Tip: When reviewing conversation logs in the inbox, look for bookings where a guest requested multiple services. If one service was not found, check whether the search array for that service was scoped correctly and whether the phrases reflect how the guest described it. See Review conversations in the inbox.

Use the variant flag correctly

SmartBot's booking tool exposes an option to include service variant details alongside a search result. This flag controls whether variant sub-options are returned for a given search call.

Set this option to true only in these situations:

  • The guest has already selected a specific service and that service has variants (for example, a "Massage" service with "60-minute" and "90-minute" sub-options), and SmartBot needs to present those variant options to the guest.
  • The search result contains variant IDs in the service's variant list and SmartBot needs to confirm which variant applies to the guest's preference.

Keep this option false in all other situations, including:

Situation Setting
Browsing the service catalog without a specific selection False
Displaying popular services False
Listing services by category False
Name-based search without a selected service False
Guest has selected a service with known variant IDs True

Important: Enabling variant details during catalog browsing or category listings returns extra data that is not meaningful to the guest at that stage and may slow response times. Reserve the true setting for the point in the booking flow when a specific service variant must be confirmed.

Understand how variants are filtered from the catalog

The service catalog filter excludes any service marked as a child variant β€” that is, one of the individual sub-options of a parent service. This means child variant entries are not presented to guests as independently bookable services during a catalog browse or category listing.

For organizations on the current service catalog structure, the filter uses the is_variant indicator on each service entry. For organizations on the legacy catalog structure, the filter instead uses a has_variant indicator, preserving the behavior those organizations rely on.

When the catalog is set to promote child variants as top-level bookable items, the system additionally removes parent variant container entries and promotes each child variant to appear as a top-level service, inheriting the parent's category and sub-category classification.

The practical effect for your guests is that:

  • A parent service such as "Facial" appears in catalog results as a single bookable entry.
  • Its child variants (for example, "Facial β€” 30 min" and "Facial β€” 60 min") do not appear as separate standalone entries in browse results under normal conditions.
  • When a guest selects the parent service and SmartBot needs to confirm the preferred duration or sub-option, it fetches variant details at that specific step.

This keeps browse results clean and prevents guests from accidentally booking a variant entry that was never intended to be a standalone appointment type.

Retrieve service details with the updated tool

When SmartBot needs to retrieve detailed information about a specific service β€” such as description, duration, price, or recovery time β€” it uses the service details tool. This tool accepts the same search phrase array format described above.

Key changes from the previous version of this tool:

Parameter Previous behavior Current behavior
Search input Single text string Array of strings (up to 6 phrases)
Description included Controlled by a separate flag Always included
Recovery time Not returned Returned in the service detail response

Note: Recovery time is now always available in the service detail response. If your center offers services such as chemical peels or laser treatments where guests need to plan around recovery, SmartBot can surface this information during the booking conversation without a separate lookup.

Tips

  • Keep phrase arrays current. If your center renames a service, update the corresponding search phrase array so the primary phrase still matches the catalog. Guests who use the old name will still be found via the synonym phrases.
  • Use recovery time to set guest expectations. Since recovery time is now included in service detail responses, consider whether your booking flow prompt acknowledges recovery time for services where it is significant. This reduces no-shows caused by guests who did not anticipate downtime.
  • Test multi-service searches in the inbox. After enabling or tuning multi-phrase search, use the inbox to review recent multi-service booking conversations and verify that each service resolved correctly. If a service search returned no results, check the phrase array for that service and add the phrasing the guest used.
  • Do not reuse phrases across different services. A phrase such as "relaxation treatment" could describe multiple services. If it appears in the arrays for both a massage and a facial, SmartBot may return ambiguous results. Keep phrases specific to one service.
  • Set the variant option at the right stage. The variant detail option is most useful immediately after a guest selects a parent service and before the booking is confirmed. Enabling it earlier in the flow adds unnecessary overhead.

Troubleshooting

A service is not found even though it exists in the catalog.

Check whether the search phrase array contains at least one phrase that closely matches the catalog service name. If the catalog name is highly specific (for example, "Hydradermabrasion Pro Treatment") and all phrases in the array use colloquial shorthand, no phrase may be close enough for the search to match. Add the exact catalog name as the first phrase in the array.

Child variant entries are appearing as bookable standalone services.

Verify that the variant indicator is set correctly on those entries in the Zenoti service catalog. Entries marked as child variants are excluded from catalog browse results by the service catalog filter. If a variant is appearing as a standalone service, it may have been created without the indicator set. Review the service configuration in Zenoti.

A multi-service booking resolved only one of the two requested services.

The search call for the missing service may have used a phrase array that mixed terms from two different services, or the array for the missing service may not have contained any phrase matching the catalog. Review the conversation in the inbox, identify the phrasing the guest used for the missing service, and add that phrasing to the correct service's phrase array.

Variant details are returning during catalog browsing when they should not.

Confirm that the option to include variants is set to false for catalog browse, popular service, and category listing calls. It should only be set to true when a specific service has been selected and its variant IDs are known. If variant data is appearing during browse, the option may have been inadvertently enabled for those call types.

The service details tool is not returning a description.

In the current version of the service details tool, descriptions are always included β€” you do not need to configure this explicitly. If descriptions are not appearing in the response, confirm that descriptions have been entered for those services in the Zenoti service catalog. If a service has no description in the catalog, there is nothing for the tool to return.

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