Automated Provisioning
What Is Automated Provisioning in Telecom?
Automated provisioning is the use of software to create and configure telecom services, such as user accounts, phone numbers, calling features, call routing and devices, with little or no manual entry. It replaces repeated manual setup in a platform's admin portal with rules, templates and APIs, so services can be built faster and more consistently.
What is service provisioning?
Service provisioning is the work of setting up a communications service so a customer can use it. For a hosted voice customer, that typically includes:
Creating the customer account, often called a domain or tenant, and its users
Assigning phone numbers and inbound routing
Building call flows such as auto attendants, hunt groups and voicemail
Applying calling features, permissions and dial plans
Configuring phones and soft clients so they register and work
Provisioning can be done by hand, one screen at a time, or automated. The required service outcomes are similar, but automation changes how the work is executed, validated and scaled.
Manual vs. automated provisioning
Manual provisioning | Automated provisioning | |
|---|---|---|
How it is done | An engineer enters settings in the admin portal | Software applies settings from data, templates and APIs |
Effort at scale | Grows with the number of users and features | Typically grows more slowly with volume |
Consistency | Varies by person and by day | The same rules are applied each time |
Typical errors | Typos, missed settings, inconsistent naming | Errors in source data or rules, which validation helps catch |
Engineer time | Spent on repetitive entry | Spent on exceptions and review |
What is device auto-provisioning?
Device auto-provisioning is a common form of automated provisioning in VoIP. A desk phone contacts a provisioning server on startup, often identified by its MAC address or another device identifier, and downloads its configuration. That configuration can define its lines, registration details, button layout and, where applicable, firmware requirements.
During a migration, device auto-provisioning is how many phones move to the new platform: each device is redirected to the destination provisioning server and picks up its new configuration.
How does automated provisioning work in a platform migration?
In a migration, provisioning happens in bulk. A service provider moving customers from a legacy platform to NetSapiens may need to recreate thousands of users, numbers, call flows and devices. Done manually, that work grows with headcount. Automated, it becomes a repeatable process:
Extract available customer data from the source platform.
Transform it into the structure the destination platform expects.
Provision approved accounts, users, features and devices through the destination platform's APIs.
Validate that what was built matches the source and behaves as expected.
Otto™, Vox Matic's proprietary automated telecom migration framework, automates repeatable extraction, transformation and provisioning work for NetSapiens migrations, with automated validation checks that help identify discrepancies for review. In one Vox Matic example, a migration task that took approximately 60 minutes manually was completed in about 15 seconds using Otto, followed by approximately five minutes of verification. Results vary according to the source environment, data quality, configuration and scope. Read more about Otto.
Frequently asked questions
Is automated provisioning the same as zero-touch provisioning?
Zero-touch provisioning usually refers to devices configuring themselves on first boot. Automated provisioning is broader and also covers accounts, numbers, features and routing.
Does automated provisioning remove the need for engineers?
No. It reduces repetitive data entry. Engineers still design the rules, review exceptions and validate results.
What happens if the source data is wrong?
Automation applies whatever it is given, so poor source data can be reproduced quickly. That is why migrations review and standardize data before provisioning and validate it afterward.
Related terms
See how automated provisioning supports a NetSapiens migration
NetSapiens is a trademark of Crexendo, Inc. Metaswitch and BroadWorks are trademarks of their respective owners. Otto™ and Forge™ are trademarks of Vox Matic. Vox Matic is an independent migration services provider. References to third-party products are for identification and interoperability purposes only and do not imply endorsement, except where an authorized partnership is expressly identified.