The Problem: First-Time Configuration Is Where Mistakes Start
You’ve built a policy. It catches drift after the fact. But what about the moment an extension or phone is first created? That’s when someone picks the wrong codec, skips a recording toggle, or leaves a default in place that doesn’t match your standard.
Policies fix drift. But wouldn’t it be better if the drift never happened in the first place?
What Templates Do
Templates are the little brother to Policies. Where a Policy continuously enforces configuration across your 3CX systems, a Template applies once — at the moment of creation.
Create an extension? The Template makes sure every field is set to your standard before anyone touches it. Provision a phone? Same thing. The settings are right from the start, every time.
No process docs. No hoping your tech remembered the checklist. The Template handles it.
How They Work
Define Once, Use Everywhere
Build a Template the same way you build a Policy — pick the settings, set the values. The difference is when it runs: a Template fires once on creation, then gets out of the way.
- Extensions — Nearly all fields are now available during creation and edit. Your Template controls which values are pre-filled and locked in. You can even suffix a string to the Last Name — useful for tagging extensions with a department or location automatically.
- Phones — Provisioning and editing now support nearly all fields. Templates set them correctly on day one.
Convert Between Policies and Templates
Already have a Policy that covers the settings you want? Convert it to a Template with one click (it creates a copy — your original Policy stays intact). Going the other direction works too. And you can duplicate either type to speed up building new ones.
Templates Create, Policies Enforce
Think of it this way:
- Template — Sets the correct configuration when an extension or phone is created
- Policy — Monitors that configuration going forward, catching and remediating any drift
Together, they cover the full lifecycle: correct from day one, enforced from day two onward. This is how Controvo’s 3CX management platform eliminates configuration mistakes at every stage.
What Else Shipped
This release wasn’t just Templates. We also shipped:
- Kinde Authentication — Moved to a dedicated identity platform for more reliable login, 2FA, and password management
- Global Policies — Set a policy to apply globally across all phone systems
- Loading Skeletons — Replaced loading spinners with shimmering skeleton screens across many pages
- Pinned Save Buttons — Extension and phone edit pages now fix the Save button at the bottom of the screen so you don’t have to scroll
- Phone System Creation — Create a Customer at the same time as a new Phone System
- Bug Fixes — ConnectWise PSA sync, policy generation and application, and several UI fixes
Getting Started
Templates are available now to all Controvo users. Head to the Policies section, create a new Template, and start standardizing your extension and phone configuration from the moment of creation.
Already in the pilot? Log in and try it. Not yet? Apply for the pilot to get early access.
