A new hire starts Monday. Somebody has to make a phone work on their desk. Traditionally that means a technician visit, a laptop, and someone reading a MAC address aloud over the phone.
What happens instead
The handset ships to the desk. Somebody plugs it into the network. It contacts our provisioning server, authenticates, pulls its own configuration, and comes up with the right extension, the right directory and the right buttons. Nobody visits, and nobody types an IP address.
Why it matters more than it sounds
The saving is not really the initial install — it is everything afterwards. Staff turnover, desk moves, a new branch opening, a firmware update across two hundred phones, a handset that dies on a Friday. All of it becomes a change pushed remotely rather than a visit scheduled for whenever someone is free.
For multi-site businesses this is usually the difference between a phone system that stays current and one that quietly drifts out of date because updating it is too much hassle.
What we handle
Provisioning templates per role, so a warehouse phone and a front-desk phone come up differently. Firmware managed centrally. Configuration changes pushed to one phone or all of them. Replacement handsets that inherit the old extension by being plugged in.
Common questions
Does this work with phones we already own?
Usually. Supported models from the mainstream manufacturers can be redirected to our provisioning server. Send us the model list and we will confirm.
Is it secure?
Provisioning is authenticated and encrypted in transit, and configurations are tied to specific devices rather than being available to anything that asks.
What about people working from home?
A home phone provisions the same way. Note that a station moving to a new address needs its emergency service address updated — see our VoIP Service Terms.