PBX Provisioning
Extensions, devices and users, provisioned consistently.
This application is in development. Ask to be notified when it becomes available, or tell us what your operation needs from it.
Overview
What PBX Provisioning does
Provisioning is repetitive work that punishes inconsistency. PBX Provisioning applies templates so every extension, device and user profile is created the same way, and records who changed what.
It operates against the telephony platform you already run through its connector; it is not a replacement for your PBX.
- Provisioning templates
- Bulk operations
- Change history
Key Benefits
Why operations adopt it
Consistency by default
Templates remove the variation that manual provisioning introduces.
Onboarding at speed
Provision a full team in one operation instead of one record at a time.
Traceable changes
Every provisioning action is attributed and reversible.
Capabilities
Capabilities
Configured by your own administrators — not hard-coded into the application.
Profile templates
Define standard configurations per role, site, department or client.
Bulk provisioning
Create, update or retire many records in a single controlled operation.
Device management
Track device assignment, model and configuration state per user.
Directory synchronisation
Align users with LDAP or Active Directory as staff join and leave.
Change history
A full audit trail of provisioning changes with the ability to revert.
Platform connector
Apply changes to the telephony platform already in production.
Use Cases
Where it is used
Rapid team onboarding
Bring a new campaign team into production in a single provisioning run.
Multi-site standardisation
Apply one configuration standard across every location.
Integrations
Connects with
Integration availability is confirmed for your environment before any commitment is made.
Connector for Asterisk-based telephony environments — one of several supported platforms.
Authenticate users and synchronise directory attributes from an LDAP service.
Directory synchronisation for user provisioning and group-based access.
Every application exposes a documented REST API for reading and writing its own data.
Scheduled import and export of structured files for systems without an API.
Architecture
How it is built
This application runs as a multi-tenant SaaS product with its own data isolation, role model and API. It can operate entirely on its own, or exchange data with your existing systems through the connector layer.
Multi-tenant isolation
Each customer operates inside an isolated organisational environment. Data, users, configuration and reporting are scoped to a tenant at the application layer.
Role-based access control
Permissions are granted by role, and roles are scoped to the tenant, team and function that requires them.
API authentication and scoping
Integrations authenticate with issued credentials limited to specific endpoints and data, and can be revoked independently.
In development
Tell us what you need from it
This application is in development. Ask to be notified when it becomes available, or tell us what your operation needs from it.
An honest note
We do not publish demos or screenshots of applications that are still in development. If timing matters to your decision, ask us for the roadmap position directly.
Related Products