nmodes Introduces Arabic language support for Advanced AI Solutions

Most of the online search is keywords-based. Same in social domain, a vast number of analytical tools, networking platforms and mobile apps use keyword-based technologies as well.

There is a difference, of course, between traditional internet search and social search. The former finds websites. The latter finds conversations, messages, posts. Keyword-based internet search is doing a decent job for us for over 20 years. Keyword-based social search is not doing a decent job at all.

Consider a basic example: finding on Twitter who is interested in buying jeans. We can start by typing ‘jeans’ but that brings up too much noise. Maybe ‘need jeans’? Less noise but then we  people who use expressions like ‘looking for jeans’ or ‘want jeans’ or shopping for jeans’. Not to mention those who use ‘denim’, or brand names. So we have to run multiple searches or create a complex search string using logical AND and OR and hope it works. Neither option is simple, or convenient, and certainly not efficient.

The above example highlights the major flaw with keyword search - it does not capture the meaning of social conversations, and therefore cannot be a reliable source of information about conversations.

It does not provide too much of correct information. And it does provide lots of incorrect information. But the biggest problem is that it has extremely limited potential for improvement.  

So as long as we stick with keyword-based social search the results are destined to be limited.

Why, then, we stick with keyword-based search in social search? Simply because there is no good alternative. Until recently, that is.  

The advanced semantic technologies capable of capturing the meaning, or intent, of conversations are now offering an exciting alternative.

I will discuss these technologies on my next blog.

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.