ZenotiHelp

Twilio Flow Configuration β€” Studio Flow Migration to Lambda Handler

ZTZenoti Docs Team Updated September 8, 2026 4 min readGuide

Note: For conceptual background on SmartBot voice channel configuration, see Configure the voice channel.

When your organization has an existing Twilio Studio Flow, you can migrate it to the Lambda handler flow type through the SmartBot admin console. This process extracts your voice settings β€” including welcome greeting audio, voicemail configuration, and email notification recipients β€” and applies them to your center's SmartBot configuration automatically.

Before you begin

  • Your center must have an existing Twilio Studio Flow configured before starting this migration.
  • You must have admin access to the SmartBot admin console.
  • Confirm that the email addresses listed in your Studio Flow as voicemail notification recipients are correct, as they will be imported during migration.
  • The internal SmartBot implementation address is automatically excluded from the imported recipient list β€” you do not need to remove it manually.

Steps

Initiate the Studio Flow migration

  1. Sign in to the SmartBot admin console.
  2. Navigate to settings in the left navigation panel.
  3. Select the center for which you want to migrate the Twilio Studio Flow.
  4. Locate the Twilio flow configuration section and select the option to migrate your existing Studio Flow to the Lambda handler flow type.

Review and confirm the extracted settings

During migration, the system reads your Studio Flow definition and extracts the following settings automatically:

Setting Description
Call enabled Whether inbound calls are active for the center.
Missed call enabled Whether missed call handling is active.
Voicemail enabled Whether voicemail recording is active.
Transcription enabled Whether voicemail audio is transcribed to text.
Send voicemail email Whether email notifications are sent when a voicemail is received.
Customer email address list The list of email addresses that receive voicemail notifications, imported from the Studio Flow definition.
Twilio flow type The flow type assigned after migration (Lambda handler).
Voicemail recording URL The URL used to access recorded voicemail audio.
Welcome greeting URL The URL of the welcome greeting audio file, served through the SmartBot content delivery network after migration.

Review the extracted values displayed on screen before confirming the migration.

Important: If your Studio Flow contains an MP3 welcome greeting, the system downloads that file and makes it available through the SmartBot content delivery network. Verify that the welcome greeting URL displayed after migration plays the correct audio before going live.

Confirm email notification recipients

  1. Review the Customer email address list that was imported from your Studio Flow definition.
  2. Add or remove recipients as needed to reflect your current notification preferences.
  3. Confirm that all intended recipients are listed before saving.

Note: The SmartBot internal implementation address is excluded from this list automatically. You do not need to identify or remove it.

Save the migrated configuration

  1. Select Save to apply the migrated settings to your center's SmartBot configuration.
  2. The Twilio flow configuration for the center is updated to the Lambda handler flow type, with all extracted settings applied.

Worked example: A center previously used a Studio Flow with an MP3 welcome greeting at a Twilio-hosted URL, voicemail enabled, and three voicemail notification addresses: front-desk@example.com, manager@example.com, and the internal implementation address. After migration, the SmartBot admin console shows the welcome greeting URL pointing to the SmartBot content delivery network, voicemail enabled, transcription enabled, and only the two business-owned addresses in the customer email address list. The internal address does not appear.

Tips

  • After migration, play back the welcome greeting URL shown in the configuration to confirm the audio was transferred correctly before your center takes its next call.
  • If you manage multiple centers, migrate and verify one center first before repeating the process for others. Settings are applied per center, so a configuration error on one center does not affect others.
  • Keep a record of your original Studio Flow email recipients before migration so you can quickly verify the imported list is complete.
  • If voicemail email notifications are not arriving after migration, confirm that Send voicemail email is enabled and that the recipient addresses in the Customer email address list are correct.

Troubleshooting

Symptom Resolution
The welcome greeting does not play after migration. Confirm the welcome greeting URL in the Twilio flow configuration section points to the SmartBot content delivery network. If the URL still references the original Twilio-hosted location, the audio file may not have downloaded successfully. Contact your SmartBot administrator to re-trigger the migration for that center.
Email notifications are not being received after migration. Verify that Send voicemail email is enabled and that all intended recipients appear in the Customer email address list. Check that recipient email addresses are spelled correctly.
An email address is missing from the imported recipient list. The internal implementation address is excluded automatically. If a business-owned address is missing, add it manually to the Customer email address list and save.
The Twilio flow type still shows the original Studio Flow type after saving. Refresh the SmartBot admin console and navigate back to the Twilio flow configuration section for the center. If the flow type has not updated, re-save the configuration.
Was this article helpful?
Your feedback helps us improve our documentation.