Integrated Real-Time Data Boosts Content Delivery

sasha uritsky

Feb 12, 2016

How to make content more relevant and appealing to the content consumer?

This is a problem that has been on the mind of content creators for some time now. In our age of information abundance it is not easy to stand out and make your voice heard. The competition for the consumer’s attention is escalating, and with the number of information sources ever increasing, it will only get tougher.

Traditionally, a content delivery does not change across the target audience. A commercial, or a blog, looks and is experienced in the same way by all viewers and readers. We are entrenched in this paradigm, and can hardly imagine it being otherwise.

It turns out, the advancement of new technologies capable of capturing individual intents in real time brings up new opportunities in creating personalized experiences within the framework of content delivery.

This is how content can become more relevant - by becoming more personalized.

In a rudimentary form, we are already familiar with this approach as seen in online advertising. Some web and social resources aim at personalizing their promotional campaigns based on whatever drops of behavioural patterns and interests they can squeeze out of our web searches. The problem, of course, is that the technologies used to power these campaigns understand human behaviour poorly and results, therefore, more often than not leave a great deal to be desired. To put it mildly.

nmodes has been working on semantic processing of intent for several years. We now can capture intent from unstructured data (human conversations) with accuracy of 99%. (Interestingly, many businesses do not require this level of accuracy, being satisfied with 90%-92%, but we know how to deliver it anyway).

We recently started to experiment with personalizing content by using available consumer intent.

We used Twitter because of its real-time appeal.

We started by publishing a story, dividing it into several episodes:

And we kept the constant stream of data flowing, concentrating on intent to dine in Paris:

We then merged the content of the story with consumer intent to dine in Paris as captured by our semantic software. Like this:

This merging approach shows promising results - the engagement rate jumped above 90%.

Overall we are only at the beginning of a tremendous journey. We know that other companies are beginning to experiment, and the opportunities from introducing artificial intelligence related technologies into content delivery are plentiful.

There is a long road ahead, and we've made a one small step. But it is a step in a very exciting direction.

Interested in reading more? Check out our other blogs:

Building Facebook Messenger chatbot: what they forgot to tell you.

There are lots of written tutorials and online videos on this subject.

Yet many of them omit important details of the bot building process. These details may vary from one user to another and are difficult to describe in a unilateral fashion. Consequently it is easier for tutorial writers not to mention them at all. We try here to fill the gap and provide some additional clarity.

1. Creating Facebook app.

One of the first steps in building a Facebook Messenger bot is creating a Facebook App. It requires a business Facebook page. This might seem obvious to avid social users yet worth mentioning: a business Facebook page can only be created from a personal Facebook page. If you already have a business Facebook page move on to the next step. If you have a personal Facebook page go on and create a business page. If you are among the lucky ones that live without Facebook presence now is your chance to become like everybody else.

2. Getting SSL certificate.

Next you need to setup a webhook. Your web application is hosted on a web server and the webhook’s role is to establish connection between Facebook and your web application via your web server. In order for the webhook to work you need SSL certificate because Facebook supports only secure connections (HTTPS) to external web servers. So first, you need to purchase it. The costs change from one company to another but it is important to buy a reliable certificate otherwise Facebook might reject it. All major ISP companies offer SSL products. Second, you need to install it on your web server. The installation process can be tricky. Sometimes you can get technical help from the ISP company that sold you the certificate (as a rule of thumb, the bigger the brand the better their technical support is supposed to be. But the cost may be higher too). You can also rely on popular tools, such as keytool command utility, assuming you know how to use them. In any case, it might be a good idea to allocate several days, up to a week, for this step when planning your project.

3. Choosing the server environment.

Your options are (almost) unlimited. Many online tutorials use Heroku which is a cloud-based web application platform, but a simple Tomcat web server would suffice too. Your decisions should be based on your business requirements. A lightweight server such as Tomcat is a good fit when it comes to web centric, user facing applications. If backend integration comes into play, a web application server should be considered.

Your choice of programming languages is also broad. PHP is one popular option, Java is another but the list by no means ends here. Your chatbot app communicates with Facebook using POST requests, so any language that supports web protocols will work. Again, make decisions having your business goals in mind.

Artificial Intelligence Chat Is Evolving Faster Than IVR

Although it doesn’t feel like all that long ago, way back in the 90s one of the most important factors to a call center’s success was the ability to route a customer to the right support agent with the IVR (Interactive Voice Response). Countless hours were spent identifying the most efficient call routing patterns and expert agent capabilities to ensure that your request reached the right person quickly. This technology is still widely used today and there are still teams in the largest companies programming IVR systems to accomplish pretty much the same goal.

As the standard for customer support evolved there have been many attempts to improve the function and the customer experience associated with IVRs to reduce hold times and provide more relevant support faster. Even today some companies will use their IVR system as a way to keep a customer on hold, rather than provide a solution, when agents are inundated with calls.

For those of us who’ve worked in the voice industry for some time, we’ve seen first-hand the attempts to accomplish a customer’s need before reaching an agent. First there was expert agent routing that delivered your call to the agent most qualified to help you. Then came advances in voice recognition, which today has evolved to be a very effective tool to increase containment rates and deflect calls from reaching a live agent. My two favorite examples of the power of voice recognition are Cox Communications and Capital One, two examples of great voice recognition and routing.

Our memory, however, is short. It wasn’t so long ago that we were all pulling our hair out punching digits into the phone or constantly repeating “agent”, “Agent”, “AGENT”, AGENT!!!!!”.

Whether it was a limit of computational power or the sheer cost of developing and implementing advanced call center technology, it took decades for phone systems to be able to front end the customer support process as efficiently as they do today. Thankfully we all survived to see it without boiling over from the hypertension usually associated with calling with a customer service department.

Bad customer experience is definitely not the case with Chat Artificial Intelligence (Chat AI). While we seem to hear about the shortcomings of Chat AI like the disconnected conversations and the robotic like responses, these experiences are usually the product of Chatbots with limited AI functionality or early stage deployments. The increases in both computational power and the massive advancements in machine learning are driving excellent customer experiences that improve over time.

When was the last time you heard of technology actually performing better, on its own, without a ton of additional development work or continuous updates? Well, that’s the case with Artificial Intelligence. Like a person, the more experience it has interacting with customers and information, the better it performs with little need to be manually improved or fine-tuned.

Today, AI Chat can be used to answer a large majority of customer requests and because Artificial Intelligence learns as it is used, customers prefer to interact through AI chat to avoid all of the frustrations commonly associated with calling a contact center agent.