We’ve written extensively about the different mobile deployment models and how to find the right fit for your business. Now that you know that there are so many options out there, you may be thinking about making a change.
But where do you start?
We sat down with our mobile experts to hear their top tips for transitioning to a new service provider or changing up a mobile deployment strategy. Here’s what they had to say about the process:
Discussing alternatives: Clients will approach Nebula to talk about their current challenges and discuss the possibility of changing their mobile deployment model, whether it’s BYOD, COPE or Corporate Sponsored, among others. Our team will offer advice on alternative mobile deployment models to see how a different approach may better suit their business needs and enable their workforce.
Negotiations and RFPs: Nebula will conduct a formal RFP process with different vendors. Our team will then assess and consolidate these offerings and present it to the client in an independent manner. In this way, we’re providing our client’s with enough knowledge to choose the best option. We’ll also have follow-up discussions with vendors to further negotiate better offerings to match the client’s unique needs.
At this stage, we’ll also analyse employee user profiles, which allows us to recommend appropriate packages based on different user needs.
Account transition: Once the client has chosen a vendor offering, Nebula will assist in the creation of a new corporate account; handling all the admin involved in creating an account with a new vendor. This stage requires the enterprise to comply with vendor specific account creation processes and to provide the required documentation.
This process also involves credit vetting, RICA and contract confirmation.
Mobile line transition: Once the client account has been created, mobile lines will be migrated and aligned with chosen packages. At this point, it’s important to remember to:
- Map the right number to the right employee. This information needs to be provided to the vendor.
- Identify lines that have not reached their term date at the time of migration as these will incur a buy-out fee. In some cases, it will be agreed that the new vendor will pay the buyout fees involved.
- Note that roaming numbers cannot be ported and can only be done once the user has returned.
Implementation: This stage encompasses the entire change management process that comes with transitioning to a new vendor or changing up your mobile deployment model. This involves handling all the logistics around new SIMs and mobile devices, ensuring these are delivered to right employees and that previous mobile devices are returned. This process must be handled meticulously to avoid employees receiving the wrong SIMs or devices or mobile administrators failing to flag devices that need to be returned.
Why Change Management is essential
According to our mobile pros, there are various change management procedures that businesses need to implement in order to ensure that these transitions happen without a hitch. Here’s their advice:
- Hold user group meetings with employees across different branches with presentations to outline the changes and explain the benefits of the new approach so you can garner employee support.
- Send all documentation to employees early so they can complete it prior to the user group meetings and ask questions they may have.
- Ensure that users are clear on the new policy being implemented and how it has changed from the previous approach.
- If your employees are frequent travellers, make sure they are aware of the activation process for their new roaming partner.
- Communicate new billing models to users where applicable. This is especially important when debit orders are involved.
- Mobile administrators must be trained around new vendor processes, such as activation of roaming or loading of new bundles.
How OneView can make the process stress free
Billing Verification: When switching to a new vendor or mobile deployment model, companies need to track whether their billing is in line with negotiated rates and monitor if employees were indeed switched to the correct packages. OneView makes it possible to pick up errors and keep track of employee contracts, allocated devices and billing information.
Keeping tabs on spend: Using OneView it’s easy to set up customised call limits and data usage thresholds, to create cost and usage awareness and prevent possible abuse.
Continuous optimisation: Where the transition has been from a BYOD/COPE environment to a Corporate Liable Environment, it can be especially overwhelming to keep track of costs and usage for each employee and cost centre, while also promoting healthy user behaviour. Using OneView to manage your mobile environment and optimisation makes this transition fuss free.
Keen to hear more about Nebula and OneView? Complete the form below.