Many companies today have implemented a BYOD (Bring Your Own Device) for their employees and more than 50% of businesses have implemented as of the end of 2017 according to Gartner. Lots of decisions need to be made when putting into a place a BYOD company policy, including security concerns, data ownership, and possible loss of productivity with personal applications mixing with business. While many solutions exist to support large enterprise rollout of BYOD policies, the small and medium business tend to form ad hoc policies to address their most pressing issues. According to SecureEdge Networks, 80% of all BYOD is completely unmanaged. Here is a good starting point for a BYOD best practices checklist.
Potential BYOD Issue
An often overlooked consequence of a BYOD policy is one of the most basic: an employee-owned device has an employee-owned phone number and in many client-facing roles, especially in the field, eg, sales, that number is the one employees give out and many times, is also on their business cards. That phone number often becomes the way clients and customers contact your company and is under the ownership of your employee. When that sales rep that has been with your company for 6 years leaves and takes a position at your largest competitor, clients calling to place their order with their favorite sales rep reach them, AT THEIR NEW COMPANY.
HOW UNIFIED COMMUNICATIONS SUPPORTS BYOD
Unified Communications can solve this issue with some very simple best practices. At the most basic, you can assign a DID or direct inward dial number and forward that number to the employees mobile and print that number on business cards. A feature common to many UC services and may be called different things, but is commonly referred to simultaneous ring or sim-ring. So a DID assigned to a user's desk phone can also ring their mobile or any other specified numbers so a user can be reached at their desk or away from the office. So what about when users want to make an outbound call, won’t their mobile number be displayed? The simple answer is yes, but many UC providers provide a soft phone application for iOS and Android smartphones and for those that don’t, a third party soft phone applications such as Bria or Zoiper may be supported. When using a soft phone application, calls from a mobile number will display their work DID number and not the employees mobile number. So if you follow these best practices, your BYOD policy and company communications can successfully coexist.
INTERESTED IN LEARNING MORE?
➡️ Also visit our "Ultimate Guide To UCaaS".
Level365 offers a complete Unified Communications as a Service (UCaaS) solution with enterprise voice that is customized and scalable for your business. Our service seamlessly integrates communication among desk phones, computers and mobile devices to support remote teams and provide flexibility for on campus staff. The UC platform extends beyond voice communications with Unified Messaging, Analytics, Presence, Chat/SMS, Cloud Faxing, Business System Integration and more.