ZenotiHelp

Multi-environment support

ZTZenoti Docs Team Updated April 10, 2026 1 min readGuide

SmartBot is available across multiple geographic regions, each with configuration tailored to local requirements. This ensures that guests and staff in different parts of the world receive a consistent, locally appropriate experience.

Audience: Organization administrators with centers in multiple geographic regions.

Before you begin

  • Multi-environment configuration is managed during SmartBot provisioning by your provisioning team.
  • Individual organizations and centers access SmartBot through their assigned environment. You do not need to switch environments manually.

How multi-environment support works

SmartBot operates across several deployment regions to support global organizations:

  • Sandbox β€” Testing and development environment.
  • Beta β€” Pre-production testing environment.
  • QA β€” Quality assurance environment.
  • Production β€” Standard production environment for most organizations.
  • Production (Canada) β€” Production environment for Canadian organizations, compliant with Canadian data requirements.
  • Production (Asia-Pacific) β€” Production environment for Asia-Pacific organizations.

Each environment has its own configuration, including country and timezone metadata, default prompts, and logging settings. When SmartBot is provisioned for your organization, it is assigned to the appropriate environment for your region.

Country and timezone data

SmartBot maintains country code, phone prefix, and timezone mapping data per environment. This data ensures that:

  • Guest phone numbers are correctly validated and formatted for the local region.
  • Conversation timestamps are displayed in the correct timezone.
  • IVR and scheduling features respect local business hours.

Configuration per environment

Default configurations β€” including FAQ engine settings, default prompts, and system settings β€” are maintained per environment and applied at provisioning time. Changes to your organization's configuration are stored in the environment where your organization is provisioned.

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