Extension Mobility Usability aspects
extension mobility

Extension Mobility Usability aspects

Is Extension Mobility userfriendly? In principle yes, but in practice not always. In our articles, we often refer to the complexity when using Extension Mobility. But what exactly do we mean by this? It isn’t so complex to log in using a short (numeric) username and PIN code, is it? It is not ideal because we have to remember yet another combination, but typing a username like 462 and a PIN 4872 is doable.

However, this is not the issue. The problem is when Extension Mobility is used in a business environment where often the email address or some other long username is used for all enterprise applications, including Extension Mobility. For example, when Active Directory is used. In that case, the user has to enter this long username string + PIN code via the telephone keypad. It makes the use very inconvenient.

Example of the Extension Mobility login procedure

Let’s look at the example of John Doe. He is an employee with ACMECorp and his e-mail address is john.doe@acmecorp.net. The ACMECorp’s Communications Manager is synced with Active Directory (AD) and therefore staff has their e-mail address as their Extension Mobility login names. So to get access to their contacts and be reachable by phone, John and his colleagues need to login by typing their email address and PIN code. Every day, manually, on the little keypad of the phone.

To give you a better understanding of what John needs to enter on his telephone keypad, do it yourself:

services globe, arrow down, arrow down, select, 5, 6, 6, 6, 4, 4, 6, 6, *, 3, 6, 6, 6, 3, 3, *, *, 2, 2, 2, 2, 3, 3, 2, 2, 2, 6, 6, 6, 7, 7, 7, 7, *, 6, 6, 3, 3, 8, arrow down, 1, 2, 1, 2, 1, 2, submit

50 clicks every morning!

More than 50 clicks. Over 50 buttons that John needs to press every time he wants to log into his Extension Mobility enabled phone. It shows how complicated it is to use a potentially very powerful feature like Extension Mobility.