Automatic Model Selection and Responsive Dialogue Defaults

v26.7.14

Published: July 14, 2026

This week's update to the Syllable Agentic Platform removes manual LLM version selection so agents automatically use the latest model version and turns on Responsive Dialogue by default for automatically created Syllable Voice/SMS channels. It also fixes custom-role permission errors when creating or editing users, corrects folder links in workflows, refines the Sessions transcript view, keeps pronunciation overrides out of transcript text, adds finer-grained SIP call-failure statuses, and improves step tool configuration.

Agents

• Removed manual LLM version selection from Console, the API, and the SDK so agents automatically use the latest available model version instead of a pinned one.

Channels

• Enabled Responsive Dialogue by default on Syllable Voice/SMS channels created automatically so new organizations match the Console default instead of running in classic turn-based mode.
• Added SIP response-code mappings (404, 480, 482, and 604) and an UNEXPECTED_ERROR catch-all status so outbound call failure reasons are reported with more granularity instead of a generic failure.

Sessions

• Improved the Sessions transcript view with larger speaker labels and timestamps and evenly aligned summary and turn-highlight cards so conversation details are easier to read.
• Fixed pronunciation overrides altering session transcript text so the transcript now shows the original written word while the override affects only spoken audio.

Workflows

• Fixed assigned-folder links on the workflow session conditions page so they now open the correct folder instead of a workflow URL.

Tools

• Added an Auto/Manual "Tool start" option to the step tool form and fixed the start value not persisting on save so step tool trigger timing can be configured directly in Console.
• Fixed a brief "Tool not found" message that flashed after renaming a tool so the editor now navigates directly to the renamed tool.

Roles and permissions

• Fixed the Users: Edit permission so it now requires and automatically selects the Roles: View and Organizations: View permissions, letting custom roles create and edit users without permission errors.