New features
Choose whether a step waits for a reply with Fast Response. A new Fast Response item in the step menu decides whether the step waits for the caller to answer. Auto, the default, decides from the line itself: a question mark waits, no question mark moves on. Force always moves on, Disable always waits, and Variable lets an earlier step decide per call from a variable such as{{custom.fast_response}} holding force or disable. It’s handy for a rhetorical question that shouldn’t wait, or a statement that should. See Fast Response.
Post-call analysis can fill in a caller’s name. A new Update contact name switch under Post-Call Analysis → Call Analysis uses the name an inbound or web caller gave to fill in a contact whose name is empty or unknown. It only acts when the caller clearly stated their name, and existing names are never overwritten. A web caller gets their own new contact rather than renaming the shared web contact. Every analysed call now also records the caller’s given name, family name, how confident the analysis is and the words they used. See Post-call analysis.
Calls that need a follow-up are flagged on the Dashboard. When a connected call ends with a message taken, an unresolved request, a request for a person that wasn’t transferred, or a callback that hasn’t been booked, an Action required item appears in the Dashboard’s Activity panel with Mark done and View call buttons. The panel’s filters are now Needs attention and All activity. See Dashboard.
Branch on call direction and channel. Two new variables are set as every call starts: {{call.is_inbound}} (true or false, for example True on an inbound call) and {{call.is_web}} (true on a browser or embedded web call). Conditions, prompts and Code Steps can use them to handle inbound, outbound and web calls differently. See Variables.

