Call menus are built on the Auto Flow canvas
The separate Call flows page is gone. Build a call menu on the same canvas you use for every other automation, then point a number at it from the number's own screen.
Released 27 August 2026
Building a call menu no longer means learning a second editor — it happens on the Auto Flow canvas, alongside everything else you automate.
What's new
- One place to build. A call menu is drawn on the canvas like any other flow, so it can branch, check a condition, or do something other than speak — things the old menu form could never do.
- The separate Call flows page is gone, along with the menu form on each number's screen.
- Pointing a number at a menu has not moved. It is still on the number's own settings screen, under Call menu. Publishing a menu does not put it on a number, so this is the step that puts it in front of callers.
What this means for menus you already built
Nothing you built has changed and nothing has been switched off. Every menu you already have keeps answering calls exactly as it did.
Those menus are now read-only. To change what one says, build the new version on the canvas and point the number at it — the number keeps answering the old menu until you do, so there is no gap.
Worth knowing
- Switching a number to a shared menu still keeps the menu saved on the number itself, and switching back restores it.
- If a menu can't run on a particular number — carriers differ in what they allow — you're told which number and why before anything is saved.