Skip to main content

Virtual Numbers and Gatekeeping services

Recently I saw a post on the Rise of GateKeeping services

The author makes valid points from a customer perspective. But as they say, there are always two sides to a story :)

Since a lot of companies are using KooKoo to provide a telephony experience to their customers, I thought I will list out a couple of reasons why gatekeepers may be good, especially if done correctly.

Disclaimer: This will be a little biased post as we provide services to a lot of these "Gatekeepers" :)

1. Monetization: As Sinha mentions in the comments of the above post, in India, lead monetization is very very hard. Businesses in general do not want to pay up for leads and these numbers provide a provable lead generation model for these businesses. The more money the companies make, the better service they can provide for you.

2. Quality control: The example given in the above article takes an example of a clinic. If we take personal examples, most of the times I call a clinic I end up just getting either a busy tone or no one picks up the call. Same is the case with restaurants. Thanks to new services, I am now able to reach them more reliably and they are able to reach back to me. In fact, these gatekeepers can go one step further and rate the clinics and restaurants on their responsiveness also. That will give a better experience to the end customers.

3. Extra service: Not all businesses have the wherewithal to run a support center. So these gatekeepers provide add on services to these businesses which will help in improving customer experience.

That said, I agree with the above article that customer experience is paramount. The gatekeepers have to be extra careful and think through their interaction mechanisms and make them as much meaningful as possible to the customers. In this case, I think Zomato does a good job as they clearly state that this service(the extension number) is provided by Zomato so that the customer knows that the phone number is not the restaurant's number.

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 ...

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

Cloud Telephony-History and state of the art

Well, its been 11 years since Twilio launched their voice API in November 2008. I would say that was a major turning point in the cloud telephony industry. Before that, for people to build telephony applications, you either had to depend on proprietary platforms like Avaya dialog designer or build on arcane technologies like VXML which again was supported at varying degrees by the incumbents. Enter Twilio with their voice API and the industry changed for the better. Since it's been almost 11 years now I thought now might be a good time to do a comprehensive review of the cloud telephony industry as a whole in general and in India in particular. The Beginning Twilio was undoubtedly the startup which ushered in the era of cloud telephony. They started in November 2008. At that time in India, we at Ozonetel had launched a hosted VXML platform. There were no takers. After all who coded in VXML :) So when Twilio launched and we saw them take off, we immediately realized tha...