Shared call menus can be created again
Building a call menu you can point several numbers at used to be refused the moment you named it. It now opens straight into the editor, and any refusal says what needs fixing.
Released 21 August 2026
A shared call menu — one menu several numbers can answer with — could not be created at all. Naming it and pressing New call menu was refused every time, with nothing on screen to say why. It works now.
What's new
- Naming a menu creates it. Channels → Call flows → New call menu, give it a name, and the editor opens on it. Every attempt before this was turned away at that first step. (Call menus have since moved to the Auto Flow canvas — the route today is Auto Flow → New call flow.)
- It starts small on purpose. A new shared menu begins as a greeting and a goodbye, rather than the fuller tree a single line starts with. A menu is saved the moment you name it — before you could have typed a number into it — and a keypad choice with nowhere to go, or a ring group with nobody in it, is not something we can save. Add both in the editor, which is the same editor a line's own menu uses.
- A refusal now names the problem. If a menu cannot be saved, the screen says which step needs attention — a keypad choice pointing nowhere, a ring group with no number in it — instead of a single "could not create" with the reason left unsaid.
Worth knowing
- Menus already built are untouched. This was only ever about creating a new shared menu; existing menus, and the menus attached to individual lines, were never affected.
- A new menu answers nothing until you attach it. Build it first, then point a number at it from that number's settings — so you can take your time over it without callers hearing a half-finished menu.