Skip to main content

Selling to Indian SMEs

The other day, I saw a post from one of our competitors on how they never visit a customer and do the sale on the phone or over email. In fact they were wiling to let go of a customer if the customer insisted on a visit.

Well, to each his own. But being a bootstrapped company, we cannot afford that pleasure. For us, customer is king and if he wants us to visit him to close the deal, we will gladly do that.

I can write about how cool it is to sell over the phone and give some anecdotes on how quickly we closed some deals on the phone using some innovative techniques. They make for good stories. Stories that we want to listen. Stories that VCs want to listen.

Nobody wants to listen to the story of the hard working sales guy, who made 4 visits to a single customer across the town through the traffic in peak hour.

But thats the story that is getting us the money. And we live that story everyday.

That is exactly the reason we have a sales team in almost 10 locations across India. We have the Feet on Street because we want to be near to our customers. Because we understand that every region in India has their own issues and requirements.

So, my advice is simple. Go ahead and read the innovative startup stories and try to emulate them. But also be ready to invest in a good sales team in case the innovations dont work out. Sometimes, the tried and tested things work out. Especially in B2B space.

And for businesses in India, in case someone is not willing to visit you, you can call us at 1-800-200-0820 or email us at sales@ozonetel.com. We will gladly come visit you anytime of the day and explain how our products can help your business :)

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