Location Selection β Call-Center Location Validation Gate
When a guest contacts your organization through a call-center SmartBot channel, SmartBot requires the guest to select a physical center before it can retrieve availability, services, or other center-specific information. This article explains how that location validation gate works during a conversation and what guests and staff can expect at each stage.
Audience: Organization administrators and SmartBot operators who configure or monitor call-center conversations.
Before you begin
- Your organization must have SmartBot configured with at least one center whose channel type is a call-center channel.
- You must have access to the SmartBot admin console to review conversation behavior and settings.
- Center-level channel enablement must be active for the relevant call-center center. Channel enablement is configured per center, so confirm the target center has its channel active before testing the gate behavior.
Steps
Understand how location validation works in call-center conversations
SmartBot handles call-center conversations differently from standard web chat or SMS conversations. In a standard channel conversation, the center context is typically known when the conversation begins β for example, the guest opens the web chat widget embedded on a specific center's page. In a call-center channel conversation, the guest reaches a shared number that may serve multiple physical centers, so the center context is not automatically established.
Until a guest selects and confirms a physical center, SmartBot withholds any tools or responses that depend on center-specific data. This includes:
- Fetching available appointment times
- Retrieving service details and pricing
- Any other operation that requires knowing which center to query
This prevents SmartBot from returning inaccurate or mismatched information before the guest's intended center is known.
Recognize the location-selection step in a conversation
When a guest's conversation requires center-specific information and no physical center has been confirmed yet, SmartBot presents a location-selection step. This step appears as a dedicated overlay in the conversation interface β visually distinct from the standard option-list overlay used for other selection steps such as service or provider selection.
The location-selection overlay uses the locationSearch overlay type, which allows guests to search for a center rather than scrolling through a static list. This is particularly useful when the organization operates many centers.
The guest's location is considered validated once they have actively selected a physical center from this overlay. Until that selection is complete (location_validated is set to true internally), SmartBot will not execute any location-specific operations on behalf of the guest.
What happens after a guest selects a location
Once the guest selects a physical center through the location-selection overlay:
- SmartBot marks the guest's location as validated for the current conversation.
- Center-specific tools become available β SmartBot can now fetch availability, service details, and other information scoped to the selected center.
- The conversation continues normally from the point where the guest left off (for example, completing an appointment booking flow).
The location selection is scoped to the current conversation. If a guest starts a new conversation, the location-selection step will appear again as needed.
Monitor location-selection behavior in the inbox
You can review call-center conversations in the SmartBot inbox to confirm that the location validation gate is functioning as expected.
- In the SmartBot admin console, select inbox from the navigation.
- Open a conversation from a call-center channel.
- Review the conversation transcript to confirm that the location-selection step appeared before any center-specific responses were delivered.
If you see center-specific responses (such as availability or service details) appearing before a location was selected, contact your organization's SmartBot administrator to review the channel configuration for that center.
Note: The inbox shows all conversations across channels. Use the channel filter to view only call-center conversations when auditing location validation behavior.
Worked example
Example: A guest calls your organization's shared booking line. The call-center SmartBot answers and asks the guest what they would like to do. The guest says they want to book a facial. Because no physical center has been confirmed yet, SmartBot does not fetch service details or availability. Instead, it presents the location-selection overlay, prompting the guest to search for and select their preferred center. The guest types their ZIP code, selects "Downtown Center," and SmartBot confirms the selection. SmartBot then retrieves the available facial services and appointment times at the Downtown Center and presents them to the guest.
Tips
- Test the gate before go-live. Before enabling a call-center channel for guests, initiate a test conversation and confirm that the location-selection overlay appears before any service or availability information is shown.
- Keep center names clear and consistent. Guests search for centers by name in the location-selection overlay. If center names in Zenoti are ambiguous or abbreviated, guests may have difficulty finding the right center. Use recognizable, full center names.
- Use the inbox to spot validation failures. Periodically review call-center conversations in the inbox to verify that location validation is completing successfully before center-specific data is returned. A pattern of conversations where guests drop off at the location-selection step may indicate that the overlay is not presenting correctly or that the center list is confusing.
- Coordinate with your regions and zones configuration. If your organization uses regions and zones to group centers geographically, ensure the call-center channel's center list reflects the intended geographic scope so guests are presented with relevant options in the location-selection overlay.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| SmartBot returns service or availability details before the guest selects a center | The center's channel type may not be configured as a call-center channel, so the location validation gate is not triggered | Verify the center's channel configuration in SmartBot settings and confirm the channel type is set to the call-center channel type |
| The location-selection overlay does not appear during a call-center conversation | The location_selection_flow intent is not being recognized, possibly due to a prompt or configuration issue |
Review the center-level prompt settings and confirm the call-center channel is active for the center; contact your SmartBot administrator if the issue persists |
| Guests cannot find their center in the location-selection overlay | Center names may be unclear or the center may not be included in the SmartBot configuration for this channel | Confirm that all intended centers are enabled for this call-center channel and that center names in Zenoti are clear and searchable |
| A guest's location appears unvalidated even after they selected a center | The conversation may have timed out or restarted, clearing the validated state | Inform the guest that location selection applies to the current conversation only; they will need to select their center again in a new conversation |