The purpose of the bot provided by LiveTiles is to deliver on the vision of the next generation digital workforce. A key part of this vision is the use of conversational UIs to provide easy to use, familiar digital versions of core organizational processes that are currently manual or based on legacy user interfaces.
The goal is not to replace all functionality provided by the systems being integrated with, but merely act as a shortcut to quickly achieve a generic or mundane task. The aim is to assist users in completing the mundane and generic tasks they encounter on a daily basis as quick as possible, thus providing them with more time to focus on what is really important.

UX Elements

The bot uses various UI components to display information to the user. These are outlined below.

Messages

Messages are the responses provided by the bot back to the user that make up the dialog or conversation. By default, these are text, but below are a few more advanced UX elements that can also be used.

Buttons

Buttons are used to give users specific options of next steps or responses that they can use to continue the conversation.
Buttons can be clicked, or the text on a button can be typed as a command in the chat box.

Images

Small images can be displayed.

Cards

Cards are combinations of all the above. One response from the bot can also contain multiple cards in the form of a carousel.

Commands

At any stage during a dialog (the snippet of conversation that achieves one task for the user) the user can type 'Cancel' to stop the current action (for example booking a meeting). The bot will then ask the user to confirm that they want to cancel.

Mandatory variables

Some actions that the user will attempt through the bot are dependent on mandatory pieces of information. For example, when booking a meeting, as a bare minimum the bot needs to have a date and time. When these variables are not provided by the user initially, the bot will ask follow-up questions to gather all the necessary information. 

Compare the flow where everything is provided in the initial command...

... versus the flow where the bot needs to prompt for all required information...

Did this answer your question?