ZenotiHelp

Twilio Flow Configuration β€” Studio Flow Migration

ZTZenoti Docs Team Updated September 8, 2026 3 min readGuide

Migrating a center's Twilio configuration from a Studio Flow to the Lambda-handler flow type consolidates your voicemail settings, welcome greeting audio, and email notification addresses into SmartBot's centralized voice channel configuration. This article describes how to perform that migration in the SmartBot admin console.

Note: For conceptual background on SmartBot's voice channel, see Ivr and voice channel.

Before you begin

  • Your organization must have SmartBot enabled and at least one center configured with an active Twilio Studio Flow.
  • You need administrator access to the SmartBot admin console.
  • Confirm that the center's current Twilio configuration uses a Studio Flow before starting the migration. Migrating a center that is already on the Lambda-handler flow type has no effect.
  • The welcome greeting audio file attached to the Studio Flow must be accessible at the URL stored in the flow definition. If the audio URL is no longer reachable, the migration completes without importing the audio; you must upload a replacement greeting after migration.

Steps

Open the voice channel configuration for the center

  1. Sign in to the SmartBot admin console.
  2. In the left navigation, select settings.
  3. Locate the center you want to migrate and open its configuration.
  4. Navigate to the voice channel settings for that center.

Start the Studio Flow migration

  1. In the voice channel settings, locate the option to migrate from a Studio Flow to the Lambda-handler flow type.

  2. Select the migration action.

    The system reads the center's current Studio Flow definition and extracts the following:

    Extracted element How it is used after migration
    Voicemail settings Applied to the center's Lambda-handler flow configuration
    Welcome greeting audio (MP3) Downloaded and re-hosted; the flow configuration is updated to reference the new URL
    Email notification addresses Imported into the center's notification address list, with filtering applied (see below)
  3. Review the confirmation prompt and confirm the migration.

Verify the migrated configuration

  1. After the migration completes, review each of the following in the center's voice channel settings:
    • Voicemail settings β€” Confirm the voicemail options match what was configured in the Studio Flow.
    • Welcome greeting β€” Play back the welcome greeting audio to confirm it transferred correctly.
    • Email notification addresses β€” Review the imported list and confirm it contains the expected addresses.

Important: Email addresses from the implementations@simplified.io domain are automatically excluded during migration and will not appear in the imported notification address list. This exclusion is applied by the system and cannot be overridden. If a legitimate notification address uses that domain, add it manually after migration.

Tips

  • Run the migration during off-peak hours. The migration downloads and re-hosts the welcome greeting audio file, which may take a few moments depending on file size.
  • After migration, test the voice channel end-to-end by placing a test call to the center's configured phone number. Confirm that the welcome greeting plays correctly and that voicemail recordings are delivered to the expected email addresses.
  • If the center had multiple email addresses in the Studio Flow, review the imported list carefully after migration. The system excludes internal implementation addresses automatically, but verify that no legitimate guest-facing addresses were omitted.
  • Keep a record of the Studio Flow's original settings before migrating. Take a screenshot or export the Studio Flow definition so you have a reference if you need to compare configurations post-migration.

Troubleshooting

Symptom Likely cause Resolution
Welcome greeting does not play after migration The audio URL in the Studio Flow was unreachable at migration time, so the file could not be downloaded Upload a replacement MP3 audio file for the welcome greeting in the center's voice channel settings
Expected email addresses are missing from the notification list The addresses belonged to the implementations@simplified.io domain, which is automatically excluded Add the required addresses manually in the voice channel settings after migration
Voicemail settings appear blank or incorrect after migration The Studio Flow definition did not contain extractable voicemail configuration Enter the voicemail settings manually in the center's voice channel settings
Migration option is not visible in the settings panel The center is already using the Lambda-handler flow type, or the voice channel is not enabled for this center Verify that the voice channel is enabled for the center and that its current flow type is Studio Flow
Was this article helpful?
Your feedback helps us improve our documentation.