Skip to main content

TRAI regulations-Move from Push solutions to pull solutions

So, the Indian government went ahead and did something which only it can do best. It setup a new regulation which certainly made it much harder for people running a honest business :). Whether the new regulation will stop SMS/Voice spam is yet to be seen. More information and discussion about this can be found at http://www.medianama.com/2011/09/223-the-impossibility-of-trais-sms-spam-regulations-anonymous/ and http://www.medianama.com/2011/09/223-what-mobile-marketing-sms-cos-think-of-trais-sms-spam-regulations/

From KooKoo's perspective it does not affect us too much as most of the KooKoo (http://www.kookoo.in) apps are inbound apps. But we do have certain apps which allow subscribers to register for alerts and sms/voice alerts have to be sent to them. For now, we are not allowing any outbound calls/sms to NCPR registered numbers until things clear up a bit and we are really sorry for the inconvenience.

For affected businesses we suggest the following work around. Move your data distribution channel from a push based solution to a pull based solution.

Lets say you currently have some code which loops through list of phone numbers and sends an SMS to them, we have to update our code to receive an incoming and play the text to the caller based on the callers phone  number.

For example:

Your current pseudo code could look like:

for(i=0;i<num_of_clients;i++)
{
sendsms(client[i],message[i])//send message[i] to client[i]
}

This should be changed to :

$r=new Response();
if($_REQUEST['event']=="NewCall")
{
$message=getMessage($_REQUEST['cid']);//get message for caller id
$r->playtext($message);
$r->send();
}

So in 5 lines of code you can enable an inbound channel for your data distribution. If you have queries and would like help in porting your solution do mail us at support@kookoo.in

Obviously, this will not work for spammers ;) and you still need to get your clients to call your number. Though this may not be the best solution for now at least you can enable your data flow in some channels.

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

Google business messages and chat agents-A match made in heaven

Google has launched Google business messages without much fanfare. It's just a small button that pops up when someone searches for your business on Google. But from the conversation industry perspective this is HUGE .   Do you know that the small call button drives millions of calls i n a year for pizza joints and other retailers in the US. Businesses spend more than a trillion dollars supporting billions of customer service calls each year. Now imagine how many chat conversations the "Message" button can drive.  Think of how customers interact with business. 1. Search on Google. 2. Click on web site link. 3. Web site shows chat pop up and tries to force the user to chat.(Annoying. I know :)) 4. User clicks on chat and starts conversing with a bot or an agent. This flow can now be completely changed. The new flow can be: 1. Search on Google. 2. User clicks on Message and starts conversing with a bot or an agent. What if you could design a customer experience that helps...