ZenotiHelp

How SmartBot delivers responses

ZTZenoti Docs Team Updated June 29, 2026 1 min readGuide

Understand how SmartBot formats and sends AI-generated responses to guests on the web chat widget and SMS channels.

Audience: Administrators and technical users who want to understand how SmartBot formats and delivers responses.

Before you begin

  • No configuration is required to use this article. It explains SmartBot's response delivery behavior to help you understand why responses appear differently across channels.

How response delivery works

Channel-specific formatting

SmartBot formats responses differently depending on the channel:

  • Web chat β€” Responses are formatted as structured JSON and delivered to the guest's active web chat session. The web chat widget renders the response with text, selectable option buttons, and any additional interactive elements.
  • SMS β€” Responses are formatted as plain text and sent via Twilio to the guest's phone number. Responses are limited to 1,600 characters. When a response exceeds this limit, SmartBot splits it into multiple messages.

Response structure

Every SmartBot response contains the following elements:

  • Message β€” The main text of the response.
  • Options β€” An array of selectable choices presented to the guest (for example, service names or time slots).
  • Intent β€” The current flow type (for example, booking or FAQ).
  • Status β€” Whether the conversation is complete or awaiting the guest's next input.
  • Detected language β€” The language SmartBot detected in the guest's messages.

Additional optional elements may appear depending on the context:

  • Waiting for β€” Indicates what input SmartBot is expecting next.
  • Footer message β€” Additional information displayed below the main response.
  • FAQ answered β€” Indicates whether the response resolved a FAQ question.
  • Has confirmed β€” Indicates whether a confirmation has been given.
  • Show all label β€” Indicates whether a "Show All" option is available for the current list.

Session cleanup

When a conversation session expires (30-minute TTL), SmartBot performs cleanup. If an abandoned booking is detected (the guest started booking but did not complete it), SmartBot sends an SMS recovery message to the guest's phone number with the center's Webstore link and instructions to restart. Abandoned conversations are flagged in the inbox.

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