DID to IVR to ring group to queue to extension, composed on a canvas. Review the exact objects that will be created, apply them one step at a time, and roll back if the customer changes their mind.
Four screens, one flow
A typical inbound flow for a clinic is an IVR with three options, a ring group for the front desk, a queue for billing with an overflow to voicemail, and a DID pointing at the IVR. In the 3CX console that is four objects in four screens, each needing a free extension number, plus the DID assignment on the trunk. Get the order wrong and the IVR has nowhere to send option two yet.
The builder puts the flow on a canvas. Each node shows the ports its type actually has (IVR keypresses, ring group no-answer, queue timeout) and you wire them. Sikurd picks free numbers from the PBX range the way the console would, and validates the graph before it will plan: no dangling options, no cycles that trap callers.
The plan is the contract
Plan review lists every object that will be created with the exact fields, in the order they will be written, and the DID route that goes last. It is frozen when you approve it. The payload shapes are the same ones the 3CX editors send, so what you see is what the PBX receives.
Apply, watch, roll back
Apply runs one step per click-through, each step claimed and recorded before the PBX is touched. A failure stops with the PBX's reason. When a build completes you can roll it back as a unit: the DID route first, then the created objects, with any changed existing object put back to its prior values. Everything lands in the instance audit log.
The builder sits beside the read-only call-flow map, which now also edits existing ring groups, queues and IVRs in place and can seed the builder with the live flow so you extend rather than rebuild.
Frequently asked questions
Does the builder change routing on live calls while it works?
Objects are created first and the DID is routed last, so callers keep hitting the old destination until the final step. If you roll back, the DID route is restored before the objects are removed.
Can I extend a flow that already exists on the PBX?
Yes. Open the instance's call-flow map and choose Extend this flow. The live objects appear on the canvas as existing nodes with their real wiring; add to them and the plan contains only the new objects and the exact fields that change on existing ones, with the prior values kept for rollback.
What happens if two people build on the same PBX at once?
Only one build can be applying on an instance at a time, and plans re-check their chosen extension numbers against the PBX before the first write. If a number was taken in the meantime the build stops and asks you to re-plan rather than creating a collision.
Can customers use it?
Customers with access to their own instance can edit their ring groups, queues and IVRs from the call-flow map and use the builder on that instance. Creating trunks, deleting objects and anything that touches other instances stays with your staff.
Build the next call flow on a canvas.
Open the live demo, drag a DID onto an IVR, wire the options and review the plan Sikurd would apply. No signup required.
