Skip to main content

Virtual Number and Number Masking models

Number masking has become popular now a days because of its adoption by the new startups like Uber, Ola and others.

Though its been talked about now, its not new. In fact when we launched KooKoo in 2010, this was one of the first application of the cloud telephony platform along with missed call applications. And a lot of startups including Zomato used KooKoo to build their own virtual number solutions.

Since it has become popular now, a lot of customers are asking for this. And since number masking can be achieved in many ways, I thought I will do a blog post on the different models and their pros and cons.
Photo Credit:Flickr
Multiple models of number masking
1. DID:
This is the most popular model. Just take landline numbers and map them to your customer numbers.
Advantage: Its simple to implement and works well.
Disadvantage: Its harder to get local numbers in Tier 2 and Tier 3 cities as a lot of cloud telephony players dont have presence there. Though we have the best coverage among all players, even we can give local numbers in only 20 cities in India. Cost may also be a factor.
2. Mobile numbers:
This is similar to the DID model. Only difference is that instead of landline number, you get a mobile number.
Advantage: There is a perception that mobile number pick rates are better than landlines.
Disadvantage: Its a little harder to implement and quality is not as good as landline.
3. Extensions:
Another model which can be tried is to assign extensions to the customer numbers instead of full phone numbers.
Advantage: You dont need to buy phone numbers and it is a huge cost saving if you need a lot of virtual numbers. Your customers also get used to a single phone number and that becomes your identity.
Disadvantage: The user experience is not as smooth as a direct phone number. The caller has to first dial a phone number and then dial an extension.

4. Click to call:
This is also an innovative way in which you can hide the phone number of the user. The user just clicks a button and he will receive a call. Once he picks up, the system dials the other end of the call and connects them both.
Advantage: This is an accepted user interface.
Disadvantage: You will need to bear the call cost on both sides.

For each of these models, I will discuss the best practices in the next blog post. meanwhile, if you want to get started, please sign up.

Popular posts from this blog

Integrating Arborjs with Angular to create a live calls dashboard

Arborjs  is a cool graph visualization library. Angular  is one of the best JavaScript frameworks and we have been using Angular in a lot of our front end development. When you handle millions of calls, proper visualization becomes very important. Without proper visualization, you can get lost in the mountains of data. So we spend a lot of time to come up with good visualizations to represent the data. Since we loved the cool way in which Arbor represented graph data, we could not wait to hook it up with Angular. Because of Angular's two way data binding, when you hook up Angularjs with Arbor.js you can get a dynamically updated visualization of graph data with cool animations. To give back to the community, we have put up the code online at Github . Basically we have created an Angularjs directive for Arborjs. Please feel free to fork the code and add extensions and use it for your own visualizations. The code is self explanatory with comments inline. Best way to get s

First Post

In this blog, I will be talking about my experiences in trying to build a cloud telephony platform , KooKoo . Along the way I will also be talking about different design choices I made, good programming practices and the IVR domain in general. For technoratti: NNFJW8EW86C3

KooKoo Contact Center integration with WhatsApp

WhatsApp announced the launch of their business API yesterday. This is a big deal. A lot of businesses have been asking for WhatsApp integration and now its a possibility. Twilio has already launched an integration . Won't be long before we see a lot more integrations pop up. The most obvious use case is for support chat bots, alerts and reminders. But we at Ozonetel believe one other use case will become the dominant use case, WhatsApp as a support channel with human agents. We believe WhatsApp will become a dominant channel in contact centers world wide. There are multiple reasons for this: WhatsApp is ubiquitous. Everyone has the app. WhatsApp interface is well known to all customers. It is feature rich. You can share audio, video, location etc in the app itself. You can integrate bots for repetitive tasks. Being the leaders in cloud contact center solutions, we at Ozonetel knew that we had to integrate with the WhatsApp channel as early as possible.