Skip to main content

Missed Call Services

Ozonetel, a Telco grade cloud communications platform enables businesses to run “Missed call campaigns” on its platform. Ozonetel has created a world record by handling a billion Missed calls in the last one year for its customers.
Missed Call Service has become an effective way to engage and involve customers by any brand/business. The missed call service is targeted and a cost effective means for businesses to reach out to its target audience. The target audience could be in regions where internet penetration is low or when you want to give a call to action to an online customer who needs to engage with you offline.
What can a business do with Missed call Service?
  • Lead Capture –Marketers who advertise across mediums still find a challenge to judge ROI’s. Missed calls help to capture 100% of the leads coming from across different mediums which allow businesses to make strategic and cost effective decisions.
  • Survey/Feedbacks – Businesses can get real time feedback on customer experience on service/product and if required alerts can be built on SLA’s and action can be taken.
  • New user activations – Generate interest and get new users engaged with the brands via different kinds of campaigns
  • Run Contests – Incentivize users / target audience to engage with the brand
  • Content on Demand – Bring content on demand to users on information like help material, new offers, new products etc
Ozonetel has been supporting Missed calls on its platform for the past four years. Some of the clients using the platform are Hindustan Unilever (HUL), Redbus, Zipdial who run creative campaigns for a large number of their end customers.
Ask for a free demo




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