Integrate SmartBot with guest profiles
SmartBot integrates with Zenoti's guest management system to identify returning guests, verify identities, create new guest profiles, and manage guest access during conversations.
Audience: Administrators understanding how SmartBot interacts with guest profiles.
Before you begin
- SmartBot must be provisioned and active for your organization.
- Mandatory field requirements for new guest creation are configured in Zenoti center settings.
Steps
Understand how guest identification works
When a guest interacts with SmartBot for a task that requires account access (such as booking or appointment management), SmartBot collects the guest's phone number and searches for matching guest profiles in Zenoti across centers. If multiple guests share the same phone number, SmartBot presents the list so the guest can select the correct profile.
Verify a guest's identity with OTP
SmartBot uses one-time password (OTP) verification to confirm the guest's identity before accessing booking history, existing appointments, or saved payment cards.
- SmartBot sends an OTP to the guest's phone number via SMS.
- The guest types the OTP in the conversation.
- SmartBot verifies the code. If the code is valid, the guest's identity is confirmed and the conversation continues.
Note: OTP verification is required before SmartBot can access any guest account data, including booking history and saved payment cards.
Create new guest profiles
When no existing guest profile is found for the verified phone number, SmartBot creates a new profile in Zenoti automatically. During the conversation, SmartBot collects all fields that your center has marked as mandatory before creating the profile.
Fields that can be configured as mandatory at the center level include:
- Email address
- Mailing address (street, city, state, country, PIN code)
- Date of birth
- Gender
- Nationality
- Primary provider
- Referral source
New guests created through SmartBot are automatically tagged with SmartBot as the referral source. You can track how many guests were acquired through the SmartBot channel in your Zenoti reports.
Note: The set of mandatory fields is configured in Zenoti center settings, not in the SmartBot admin console. Contact your Zenoti administrator to review or update mandatory field requirements for your center.
Manage the guest block list
Administrators can block specific phone numbers from interacting with SmartBot. When a blocked number sends a message or initiates a call, SmartBot does not respond and no conversation is created.
Availability: Guest block list management requires the block list feature to be enabled for your organization. Contact your administrator if this option is not available.
When adding a phone number to the block list, you must include the country code in E.164 format (for example, +12025550100). Numbers submitted without a country code are rejected with a validation error.
When removing a phone number from the block list, SmartBot matches both the E.164 format and the national-number format. This ensures that numbers added before country-code enforcement was introduced can still be removed successfully.
To manage blocked numbers, use the guest management settings in the SmartBot admin console.
Worked example: To block a US number, enter it in the block list field in E.164 format, with the +1 country code before the 10-digit number. To remove the same number, you can enter either the E.164 form or the 10-digit national number without the country code β SmartBot will find and remove the matching entry.
Manage saved payment cards
SmartBot can retrieve a guest's saved payment cards from Zenoti to facilitate deposit collection during booking. When a deposit is required and the guest has a card on file, SmartBot presents the saved card for confirmation. Guests can also save a new card during the booking flow for future use.
SmartBot does not store payment card details directly β it reads from and writes to Zenoti's secure card storage only when required for a booking with a deposit.
For full details on how deposits are collected, see Deposit collection.
Review guest interaction events
SmartBot logs key interaction events to the guest's Zenoti profile for tracking and analytics purposes. These events are visible in the guest's activity history in Zenoti and support downstream reporting on guest engagement through the SmartBot channel.
Tips
- Tag guests for channel attribution. Because SmartBot automatically assigns itself as the referral source for new guest profiles, you can filter your guest acquisition reports by referral source to measure the impact of the SmartBot channel without any manual tagging.
- Review mandatory fields before go-live. If your center requires fields such as date of birth or address, guests will be prompted to provide those details during their first SmartBot conversation. Keep required fields to the minimum needed for your business β every additional mandatory field adds steps to the new-guest flow and may reduce conversion.
- Use E.164 format consistently for block list entries. Entering numbers with the country code from the start prevents the format mismatch that can make legacy entries harder to remove later.
- OTP delivery depends on SMS channel availability. If a guest reports not receiving an OTP, confirm that the SMS channel is enabled for the relevant center in the SmartBot admin console and that the guest's phone number is correctly formatted.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Guest reports they never received an OTP | SMS channel is not enabled for the center, or the phone number is formatted incorrectly | Confirm the SMS channel is enabled for that center in the SmartBot admin console. Ask the guest to verify their phone number includes the correct country code. |
| Multiple guest profiles are returned for the same phone number | Two or more Zenoti guest records share the same phone number | SmartBot presents the list to the guest for selection. To prevent future confusion, merge or deactivate duplicate guest profiles in Zenoti. |
| Block list validation error when adding a number | Phone number was submitted without a country code | Re-enter the number in E.164 format, beginning with + and the country code (for example, +12025550100). |
| A previously blocked number is still receiving responses | The number was stored in national format before country-code enforcement and the E.164 removal attempt did not match | Use the national-number format (without + or country code) when removing the entry, or try both formats. SmartBot matches either format during removal. |
| New guest profile is not created at end of booking flow | One or more mandatory fields were not collected during the conversation | Review the mandatory field configuration for your center in Zenoti settings. If a required field is preventing profile creation, contact your Zenoti administrator to adjust the configuration. |