1 Introduction

Users in the platform terminology would mean the end users of the chatbot who would interact with the bot over the various supported messaging channels the bot is set up for. These users are not to be confused with the users who would log into the MyBOT platform to build, deploy, manage, train or analyse the bot. Those groups of users are referred to as Portal Users.

2 Behaviour and fields

A user record is automatically created by the platform when a bot user interacts with the bot for the first time. There are some core attributes or fields which are associated with a user like – their associated channel, date/time which they started using the bot, date/time of their last interaction. 

Additionally, based on the channel of communication of the user, more fields can be populated for a user based on availability and access of data. Some examples of this are – For Facebook Messenger, the profile picture and name of the user are retrieved for every user record. Similarly, for Telegram users, the username or handle of the user is obtained and displayed.

For every user, based on their interaction, various state elements are maintained to manage their conversations with the bot. This could be a particular step in the path or context terms stored in the bot’s memory.

There might be multiple records for a single end user if they use the bot via multiple channels. User records are not automatically merged and synced due to lack of a primary field for association. For web bot users, a user would mean a unique combination of a device and browser. 

Was this article helpful?

Related Articles

Leave A Comment?