Phy-gital Roundtable: Breakfast Roundup from Germany and Netherlands

02 May '15 | Debjyoti Paul

German Shoppers: Meet Them in the Fast Lane to Phy-gital

15 January '15 | Ralf Reich

Shoppers Will Share Personal Information (But They Don’t Want to be “Friends”)

15 January '15 | Anil Venkat

Modernize or Perish: Property and Casualty Insurers and IT Solutions

14 January '15 | Manesh Rajendran

Benelux Reaches the Phy-gital Tipping Point: Omnichannel Readiness is Crucial

13 January '15 | Anil Gandharve

The New Omnichannel Dynamic: Finding Core Principles Across Industries

13 January '15 | Debjyoti Paul

Technology does not disrupt business – CIO day 2014 Roundup

02 December '14 | Anshuman Singh

Apple Pay – The Best Is Yet To Come

02 December '14 | Indy Sawhney

Digital transformation is a business transformation enabled by technology

01 December '14 | Amit Varma

3 Stages of FATCA Testing and Quality Assurance

06 October '14 | Raman Suprajarama

3 Reasons why Apple Pay could dominate the payments space

18 September '14 | Gaurav Johri

Beacon of Hope: Serving Growth and Customer Satisfaction

05 August '14 | Debjyoti Paul

The Dos and Don’ts of Emerging Technologies Like iBeacon

30 July '14 | Debjyoti Paul

What You Sold Us On – eCommerce Award Finalist Selections

17 July '14 | Anshuman Singh

3 Steps to Getting Started with Microsoft Azure Cloud Services

04 June '14 | Koushik Ramani

8 Steps to Building a Successful Self Service Portal

03 June '14 | Giridhar LV

Innovation outsourced – a myth or a mirage or a truth staring at us?

13 January '14 | Ramesh Hosahalli

What does a mobile user want?

03 January '14 | Gopikrishna Aravindan

Bot Platform – “You must choose. But choose wisely.”

Posted on: 19 September '16
Girish Managoli
Girish Managoli
Chief Architect, Social Inclusion, Central Architecture Group

In the closing scene of “Indiana Jones and the Last Crusade”, the protagonist is forced to choose. The guarding knight of the grail says, “You must choose. But choose wisely, for as the true Grail will bring you life, a false one will take it from you!”

As CUI (Conversational User Interface) gains credence, clients are wondering, “How do I build an effective bot?” Several platforms are available today. This post is an attempt to help you choose the right platform for your next successful bot.

NLP (Natural Language Processing)

The crux of a bot is the ability to convert human input into machine comprehensible tokens. Human language varies widely based on literacy, demographics and conversational abilities. To handle these variations, the bot platform needs to include:

  1. A powerful language processing engine that can break down the input correctly (Whether the user politely says “Will you please book my flight to Boston from New York?” or quips “NYC to BOS” in short, the NLP engine should be able to tokenize them equivalently)
  2. Rich ontology database to recognize context and ambiguous meanings (When the user says ‘interest’, do they mean the monetary rate or a favorable concern? It depends on the context and part of speech)
  3. Pragmatic canonical dictionary to identify common equivalences (user may say “dint” or the grammatically correct “didn’t” – the bot should be equipped to treat them just the same).

AI (Artificial Intelligence)

While NLP adds language comprehension skill, a bot needs more cognitive capabilities to serve customers smartly – capabilities include reasoning, pattern matching, learnability, perception. The bot platform can include these capabilities natively or through pluggable components allowing the developer to pick and choose. For instance, a bot can become adept at reading facial expression by using Face API.

Memory

Memory is yet another quality that a bot should possess. Akin to the human brain, memory can be:

  • Short-term: When the user says “I like the second one”, she is clearly referring to the choices provided shortly earlier, which the bot should remember.
  • Long-term: If the bot remembers the last chat with the customer and the problem they are having, it prevents the frustration of repeating.

The platform may allow usage of a cache grid or connecting to databases for persistent retention.

Channels

The platform should allow access to the bot through multiple channels – web, mobile, REST API or via popular IM front-ends such as Skype, WhatsApp or Facebook Messenger. A contemporary bot platform also supports use of unconventional interfaces innovatively. For example:

  • Rich-media integration (bot displays a map showing directions)
  • Voice and video (Speech recognition and gesture input)
  • Selectable options (user selects available appointment slot rather than typing a time)

Deep-linking

In a connected world, bots cannot work in a silo and need to talk to existing systems, services and apps. The day is not far when bots will talk to each other. How easily does the platform support such scenarios? How well can the platform scale to support emerging use cases? Answering these questions reveals the strength of the platform.

Ancillary factors

In addition to the above key factors, a few other influencing aspects are:

  • Security and privacy
  • TCO
  • Licensing
  • Vendor lock-in
  • Ease of development

There may not be a bot “holy grail”, but paying attention to these factors ensures you do not “choose poorly”. What have you chosen? We would like to know.

Girish has about two decades of experience spanning wireless protocols to cloud platforms. Having served several customers, in his present role, Girish is the architect of 'I Got' PaaS & SaaS solution to uplift the bottom of the pyramid, addressing social issues in waste management, education and agriculture. As part of the role, he continues to explore new ways to leverage on technology for social equity.

  • Dharmendra gangwar

    well covered ! very informative