We're moving away from our current VoIP provider and switching to a major mobile carrier. The plan is to issue company phones to more than 100 users and set up a receptionist or call-center function. Management says the carrier will handle phone setup, but we haven't even chosen an MDM platform yet, so I'm worried about provisioning, security, support, and day-to-day administration. What are the most common problems with a rollout like this, and what policies or technical details should we settle before deployment?
4 Answers
Don’t treat this as just a phone purchase. Confirm how receptionist queues, hunt groups, transfers, call parking, voicemail, shared numbers, text routing, directories, and number reassignment will work. Decide what happens when someone changes roles or leaves. Heavy-call users will probably need Bluetooth or wired headsets, and the office network needs to support Wi-Fi calling without firewall or quality problems. Test cellular coverage in the office and at common employee locations as well.
The biggest operational headaches are usually lost, damaged, and unreturned phones. Buy durable cases, screen protectors, spare chargers, and headsets up front. Track every device and SIM, keep replacement procedures simple, and make management—not the help desk—decide whether repeated damage or loss is chargeable. People will leave phones in cars, forget them at home, give them to their kids, drop them in water, or return them without remembering the passcode.
Have a process for employees who leave unexpectedly. Delayed reporting gives someone time to access company email, saved credentials, and other data, so remote lock and wipe should be tested before launch.
Account management causes a lot of trouble, especially with iPhones and Android devices. Avoid tying company devices to personal Apple or Google accounts where possible; use the relevant business enrollment and zero-touch provisioning systems. Otherwise users forget passwords, sync personal photos and cloud storage, install games, or factory-reset a phone that remains locked to their personal account. Restrict international roaming and premium services, establish a single source for the corporate directory, and plan for billing surprises such as roaming, data prioritization, repairs, and early upgrades.
Ask for the exact phone models, carrier services, MDM, enrollment method, and support responsibilities now. Get a test device before the contract is finalized—if the carrier says they’ll set everything up, verify exactly what that includes.
Get the MDM, enrollment process, and acceptable-use policy sorted out before handing out devices. You need clear rules for lost or stolen phones, offboarding, replacements, upgrades, personal accounts, app installation, international usage, after-hours contact, and who supports home Wi-Fi or poor cellular coverage. Run a pilot with a few users first and make sure you can remotely lock and wipe devices, especially after an employee leaves.
Also define the support boundary in writing. IT shouldn’t automatically become responsible for someone’s home internet, charger, headset, personal apps, or weak signal.
Emergency calling deserves attention too. Make sure users know what address or location information is transmitted and that the receptionist workflow doesn’t interfere with emergency calls.