Why FrontM.js?
  • Updated on 17 Aug 2019
  • 1 minute to read
  • Contributors
  • Print
  • Share
  • Dark
    Light

Why FrontM.js?

  • Print
  • Share
  • Dark
    Light

Conversational interactions

FrontM Apps are built from the ground up to enable complex conversational interactions - like a Chatbot, in other words. Standard chatbots normally interact with users via screens (i.e. mobile, desktop or web) and with systems using APIs. To interact in a conversational way, both scripts and NLP engines are used.

The partcular problem all chatbots face is that conversations are unstructured by nature while business transactions are structured by nature and that introduces a number of limitations to the conversations you can implement.

There are three main types of limitation we would like to overcome with our architecture:

  1. Access to backend APIs requires stable network connections;
  2. An chatbot created for one particular transaction on one particular system cannot be easily re-utilised for a different transaction and/or system;
  3. Chatbots can only manage the context of one conversation at a time.

Running on ANY network

FrontM Apps therefore keep running when they are offline and can also maintain data integrity when the connection is unstable or intermittent.

Generic transactional Apps

When a developer creates an App that is integrated to a ticketing system like, for example, salesforce.com, the very same App can also be re-utilised and integrated to Microsoft Dynamics or SAP CRM. Moreover, it can be integrated with all of them at the same time!

Multi-tasking Apps

As mentioned, human conversations can be chaotic. For example, a person can change the subject or context and come back without warning. If apps are to be truly conversational, they should be able to manage a conversation that can switch subject or context naturally. FrontM Apps can maintain multiple conversation subjects and contexts, keeping the transactions secure and unambiguous.

Was this article helpful?