Skip to main content

IVR Payments

Rant start:

Have been seeing and hearing a lot about digital payments in India and how it will make us the best country in the world and how it will solve all our problems.

And the path chosen by our tech brethren to move payments in India along the digital path is through apps. Because you know, apps are sexy. Apps are the in thing. Apps are the next best thing since sliced bread. Apps allow you to track the customers. Profile them. Make money out of them.

Only problem, majority of India does not have a smartphone and those who have, do not want to install too many apps.

The funny thing is, if you really want to enable consumers to transact digitally, there is a ready made channel available. It does not even need an Internet connection. It does not even need a user to be literate. Its the lowly voice channel on the telco networks. And on that channel we can build the original apps, also known as IVRs.

But IVRs are not sexy. They just get the job done. And marketing teams hate IVRs. They are so old school.

We have worked with HUL in building the biggest IVR based content system(KKT) with 50 million users. Callers can select bollywood songs, like or dislike them, skip some songs etc. All on an IVR. Most of the consumers are from rural areas.

Rural people want choice. Rural people want to use new things. They want to go digital. But on their terms. Not what we think they want. And I am sure they dont want apps now.

And if they are able to select bollywood content from an IVR,I am sure, its not that hard to help them make and receive payments too.

Rant End:
p.s: I know I know, security and other things. Will cover in other posts. Suffice to say that we can provide the current level of security in IVRs too.

Popular posts from this blog

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

Google's approach to business communication

 Google has been making silent moves in the business communication space. Google has mostly lost the instant messaging wars. But it does not want to lose the business communication war. WhatsApp, Instagram, Twitter and Facebook have been making their own moves to enable businesses to reach their customers through their channels. Its all about who has control over the communication channels. Especially communication which leads to business. That's where the money is. Currently, Google is the king of search and most online transactions start with a Google search. FB, Amazon, Apple and others want to change that. They want the search to start on their properties. And they have started making the moves. WhatsApp business allows small businesses to conduct their transactions on WhatsApp. FB and Instagram have long supported small businesses to manage their business on their channels. Apple has also made some nice moves with Apple business chat. They have integrated a whole shopping expe

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