Skip to main content

A proper call center flow

Website visitors are the first class citizens when it comes to customer service. UI/UX experts spend countless hours on optimizing the web design. Every pixel counts. A/B testing is done. The funnel is optimized to help the visitor find what he wants instantly.

Its not the same case when it comes to customers who call. They are played a welcome message and put in a queue :)

It need not be so. Both are customers who have the same green money. Both should have equal importance and that is understood by the best companies.

The other day my geyser malfunctioned and I called up the AO smith customer care. I was pleasently surprised by the experience. A call flow need not be complicated. It just needs to do the right thing.

1. Recognize the caller. The AO smith engineer greeted me by name and asked the problem. He verified my address and confirmed the ticket.

2. Give feedback. Immediately after the call, I received an SMS with ticket ID and phone number of the person going to attend the problem.

3. Follow up. I got regular calls from the engineer updating me where he was and when he will be reaching my house

4. Closure.  Once the problem was resolved I got information about the ticket closure and feedback SMS.

One extra thing which could have been done was to automatically identify if the caller had a ticket and give info about the ticket.

There really is no need to treat your callers as second class customers, especially when you can use the same web development tools to develop your call flows using platform like KooKoo and solutions like Cloudagent

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

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

Mashing up Freshdesk with KooKoo for customer support ticket management

Sorry for the delay in writing a blog post. I have been caught up in too many things since last month(we are growing, so its all good :)) Anyway, this week I thought I will look at how we can use the latest rockstar startup from India, Freshdesk . Freshdesk, as most of you know is one of the best "Social Helpdesk" systems out there. I am sure most of you are already using Freshdesk to support your customers. In this blogpost I will explain how you can add telephony to the mixture. In particular I will show some code which you can use to : Welcome the caller by name Ask him to enter his ticket id Play out the ticket status Connect the caller to the correct agent handling the ticket. Luckily for us, Freshdesk has a very well defined API and it was a pleasure to work with it. The engineers were also very supportive and answered all my queries quickly. So lets get into the code directly. 1. First we need to get the caller information. For this we need to a