What's in the box

Everything between the DID and whoever answers.

Every feature is built for one job: understanding and modifying production call routing without breaking it.

01 / 20
All

Every route, rendered

IVRs, queues, ring groups, time conditions, call flow controls, announcements, dynamic routes, extensions and voicemail, all laid out for you. Announcements and recordings play right on the node. On FreePBX, admins and technicians edit a node from its details panel, or open that module's own edit screen in FreePBX without hunting through the admin menus.

02 / 20
All

Time travel

Simulate any date and time. The graph dims paths that wouldn't fire and highlights the one that would. "What happens during the company event next Tuesday afternoon?" Pick the time and the graph shows you, instead of tracing it by hand.

03 / 20
All

Replay a real call

A customer says yesterday's call went to voicemail. On that inbound route's call flow, pick the call from the last 50, looking back 3, 7 or 30 days, and the path it took lights up step by step, including the branch its time condition's schedule sent it down.

04 / 20
All

Hide any branch

Big call flows get unreadable. Collapse everything downstream of a node, from the node itself, and the diagram shrinks to the path you actually care about. A hidden branch is remembered by what it points at, so it stays hidden in every call flow that reaches it, not only the one you hid it from. Selections that share a destination hide and reveal together, so an IVR with six options pointing at one queue collapses as a single branch. Nothing is deleted, and you can reveal it any time.

05 / 20
All

What else points here

Select any node, a time condition, an IVR, a queue, and its detail panel lists everything that sends calls to it, so you know what a change would break before you make it. Turn on In-Use-By mode in Settings and open that node as the canvas's starting point, and the canvas draws everything that points at it, ready to export for a ticket or a customer.

06 / 20
All

Greetings in an AI voice

Type a greeting and hear it in a natural voice from your own ElevenLabs or OpenAI account. Numbers, addresses and times come out the way a person says them. On FreePBX it saves to System Recordings or a voicemail greeting, with undo; on VitalPBX you get a file to upload. It can also transcribe an old recording to start from. Nothing you type passes through us, and it keeps working without a license.

Hear a greeting it made, as callers hear it:
07 / 20
All

Export for humans

PNG or SVG, stamped with the destination and the time. Full quality, or sanitized: black boxes over PII for diagrams that travel beyond the PBX owner (a public doc, a vendor ticket, a training deck). One button from canvas to attachment. Every export carries a small credit line in the corner. Buy a license and you set what it says: your own company name for client-facing documents, or nothing at all.

08 / 20
VitalPBX

However many tenants you run

Search reaches every tenant at once. Start typing in the tenant you're in and Call Flow Studio offers to widen the search to all of them, groups the hits by customer, and lands you on that flow in that tenant when you pick one, instead of opening tenants one at a time until you find it. Switch tenants without leaving the graph, and give each login only the tenants it should see: a tech who handles three customers searches three, not the whole box.

09 / 20
FreePBX

CFC day/night toggle

Flip a Call Flow Control between day and night from the graph itself. It asks you to confirm first, and the Activity Log records who flipped it and when, so "who switched the phones?" has an answer. On VitalPBX, the graph shows which mode is set.

10 / 20
FreePBX

Build forward

Drop the inbound, drop the next node, wire it, save. The first forward-building dial-plan editor for the FreePBX family. No more starting at the queue and walking backward through dropdowns to make destinations exist before the routes that point at them.

11 / 20
FreePBX

Draft it before the PBX sees it

In your PBX admin UI, each piece of a new call flow is written to the PBX when you submit it, one module screen at a time, before you've seen the whole thing. Drafts and Publish (Beta) turns that around. Lay the flow out on the canvas, from blank or from a copy of an existing one, and the PBX doesn't change. Drafts save as you go and are shared with everyone who edits on that PBX. When it's ready, Publish asks piece by piece whether to build it new or use a queue, ring group or time group already there. What exists is routed to, never rewired. Then it shows you what it will create and flags any exit you left unwired, where a caller would be cut off. Nothing is written until you click Build, and if building a piece fails, Publish removes the pieces it already built. Apply Config and it's live.

12 / 20
FreePBX

Build it once, bring it to the next PBX

Export a draft as a template and import it on another FreePBX. It carries the flow, its layout and its sticky notes, minus who wrote them. On the new PBX, Publish goes piece by piece again: use what's already there, build it new, or skip it. If that PBX lacks a module the template uses (FreePBX 14 has no Dynamic Routes, for one), those parts are marked and not built. Templates are tested from each of FreePBX 14, 15, 16 and 17 onto each of the others, so a flow can move from an old 14 box to a new 17, or the other way. An MSP can build a flow once and import it on each customer's FreePBX. Both PBXs need a license or a trial running.

13 / 20
FreePBX

Undo isn't a feature in your PBX admin UI

It is in Call Flow Studio. Ctrl-Z reverts your last change while you're still working in that call flow; Ctrl-Y redoes. Apply Config surfaces automatically, so the correction goes live the second you're ready. Yes, even after an Apply Config. The Activity Log tab keeps the record: who changed what, and when, across every dial plan. Covers rewires and renames, IVR and Dynamic Route entries, details-panel fields, the settings dialogs, recordings and voicemail greetings.

14 / 20
VitalPBX

Grows with the box

Win a customer, add the tenant in VitalPBX, and it's on the canvas the next time Call Flow Studio loads. There's no second license to buy for tenant number twelve. One license covers that PBX for as long as it's in service, however many tenants end up on it.

15 / 20
FreePBX

Greetings and recordings, from the canvas

FreePBX's admin screens can delete a voicemail greeting, but they can't set one. Open an extension or voicemail card in Call Flow Studio and set its Unavailable, Busy or Temporary greeting, or the recorded name callers hear when there isn't one: upload a file, or type it in an AI voice. Ctrl-Z puts back the one it replaced. System recordings work the same way: Replace updates a recording everywhere it plays, after showing you where that is, with the same undo.

16 / 20
All

Live status, on every node

Extension nodes show a registration dot, green for registered and red for offline, with amber and purple chips beside it for DND and call forward. On queue and ring-group rows, each member gets its own status dot, and queue rows can also show each agent's P:N penalty, switched on in Settings. Read live each time the graph loads.

17 / 20
All

Runs on your PBX

Self-hosted. No cloud, and the app loads no third-party JavaScript. Installs on the FreePBX family or VitalPBX, auto-detected at install time. Your routing data never leaves your server. The PBX does talk to our server, over HTTPS: the license check (every night, and when someone signs in), trial registration, activation, update checks, password resets, new-user emails, sign-in codes, license release, optional feedback, and a notice when you uninstall. So it needs a route out to us. If you give it a text-to-speech key, what you type goes from your PBX straight to ElevenLabs or OpenAI on your own account, never through us.

18 / 20
All

Give access without giving the keys

CFS runs its own user system, separate from your PBX admin auth. Three roles: admins manage everything, technicians change dial plans, and users can pan, zoom, search, and reload the graph but never edit. On VitalPBX, where nothing is edited, there are just admins and users. On FreePBX, an admin decides what each technician gets, module by module: editing existing nodes, creating new ones, and the link that opens that module in FreePBX. A new technician starts with none of it until you grant it. Create a read-only login for a junior tech, a teammate, or a customer who can reach it, point them at https://<PBX_URL>/cfstudio, and troubleshoot together over the phone. They reload the graph as you make changes, no PBX admin UI required. No one, whatever their role, can change SIP trunks or system settings, or delete extensions. An editing login reaches your call routing and the modules and extensions in it, settings included, so it can also send calls to outside numbers over your trunks.

19 / 20
All

Speaks your language

CFS ships with a fully localized UI in 12 languages: English, Chinese (Simplified), Dutch (Netherlands), French, German, Italian, Japanese, Polish, Portuguese (Brazil), Portuguese (Portugal), Russian, and Spanish (Spain). Pick your language at install or per user.

20 / 20
All

Sticky notes & edge annotations

Paste context directly on the canvas. Markdown-style checklists, URLs, inline comments on edges. The reason a route is set up that way sits next to the route, where the next person to open the graph will see it.