We're moving away from our current VoIP provider and switching to a major wireless carrier. The plan is to issue smartphones to more than 100 employees and use a receptionist or call-center setup for incoming calls. Management says the carrier will configure the phones, but we don't know which mobile-device-management platform will be used yet, and I'm concerned about provisioning, security, support, and ongoing administration. What are the most common problems with a deployment like this, and what policies or technical decisions should we make before rollout?
4 Answers
Get the MDM and acceptable-use policy sorted out before ordering or handing out phones. You need clear procedures for enrollment, lost or stolen devices, terminations, replacements, damaged hardware, app installation, personal accounts, international roaming, and after-hours expectations. The carrier may activate SIMs and ship devices, but that is not the same as designing or managing the fleet. Ask for a test device and validate the entire enrollment and wipe process first.
The biggest operational headaches are lost and broken phones, users delaying reports, forgotten PINs or account credentials, and employees connecting personal Apple or Google accounts. Some people will treat the work phone as their only personal phone, while others will refuse to carry two devices. Decide in advance whether personal use is allowed, who owns the number and data when someone leaves, and how personal content is handled during a remote wipe. Use strong cases, screen protectors, spare chargers, and a documented replacement process.
Expect people to leave phones in cars, hand them to their kids, take them overseas, or install games and social apps. A fast app-approval process and a clear travel policy will save a lot of tickets.
Billing can become its own full-time problem: roaming, international calling, premium services, insurance, early upgrades, usage limits, and replacement costs. Establish the carrier contract and support boundaries before deployment. Apple Business Manager with automated enrollment is generally straightforward for iPhones; Samsung Knox can help with Android. Whatever platform you choose, verify that devices can be locked, located, reset, and reassigned even after an employee leaves. A phased pilot with several users is much safer than giving out 100 phones at once.
Do not overlook the phone-system design. Confirm how receptionist transfers, queues, hunt groups, call parking, voicemail, shared numbers, texts, and number reassignment will work when an employee changes roles or leaves. Heavy callers will probably need headsets. Test Wi-Fi calling at the office and document that IT supports the corporate service, not every employee's home Wi-Fi or local cellular dead spot. Make sure emergency calling procedures and office-location information are accurate too.
Also make sure management, not IT alone, decides what happens when someone repeatedly loses or damages a phone. Otherwise every hardware complaint becomes an IT escalation.