Launch controls no longer reroute test chats
Testing an AI Agent from the Ada dashboard now always opens the Agent being edited, even when launch controls set its rollout to 0% and direct traffic to a second Agent.
What changed
Previously, launch controls applied to test chats as well as end-user traffic. An AI Agent at 0% rollout with a second Agent configured would open that second Agent when tested — or show a domain error if the dashboard was not in its list of allowed websites. This blocked testing the Agent before rolling it out.
Rollout percentages for end users are unchanged.
Who it affects
Anyone testing an AI Agent that has launch controls configured. The *.ada.support allowed-websites workaround is no longer needed.
On the legacy web embed, sessions started with testMode are no longer redirected to the second Agent either. Rollout percentage still governs whether the widget appears — below 100% it shows only to the browser’s rollout group — so set rolloutOverride to 1 to always show a test-mode embed. See Launch options.
Reuse images across Playbooks
Playbook authors can now reuse an image that was already uploaded instead of uploading it again.
What’s new
The image picker in a SEND step now includes a library of previously uploaded images.
- Browse or filter the library by an image’s alt text from the Search tab.
- Select one or more images and insert them together, each as its own inline attachment.
- Images already used in the Playbook being edited are marked In use.
Uploading a new image from the Upload tab works as before.
Limitations
A few constraints apply to the reuse library. The Search tab shows and searches the 100 most recently uploaded images, so once an Agent has more than 100 images the older ones can’t be found by searching.
See Media for details.
Conditional language menus for Voice
Voice AI Agents can now present different language-selection menus based on the end user’s context, so end users only hear the language options relevant to how they reached the Agent.
What’s new
Previously, the language-selection menu offered the same list to every end user. You can now configure this from Config > CHANNELS > Voice > Language selection:
- Default menu — the languages every end user hears when no conditional menu matches.
- Conditional menus — present a different set of languages when conditions match the end user’s context, such as the number that was dialed. Menus are evaluated top to bottom, and the first match is played.
Learn more about setting up the language selection menu.