What is Bot platform

Multi platform robot is a pack of Corezoid processes which are released 4 main principles:
1. Receiving messages from users from different messengers
2. Reduction of received data to common format
3. Data processing according to main logic of Bot
4. Sending messages based on that channel (messenger) from which it came

What Sender company is and why choose it?

For implementing functional of connecting operators to chat with users of your Bots.
Because Sender is messenger which is a workplace for operators of your company. Messages from users of different messengers are processed in a single interface.

2) specify only text_id when you create task to send a message to the Send message process.
Instead of "loading" processes with nodes to send multiple message texts for multiple messengers in different languages.

For example, in order to send message about choosing language you need only 1 node and it looks like this:

Data transfer to the process Operators calling, when chat_state = active and when user_text or button_id contains one of the signs that user wants to connect to operator

Set variable copy_proc_id - ID of the process, which process the command /lang

Creating the task in multi-step process, which ID is defined by variable copy_proc_id. The reference {{channel}}_{{chat_id}} of this task is unique and used to modify it on the steps of the process.

Modifying the task in multi-step process with attribute action = cancel to lead out it from node with callback to final node. This used in case of error not_unical_ref in the previous step. This error means that Bot’s user has not completed multi-step process and started from the beginning.

30 seconds delay before retrying to create task in multi-step process which ID is defined by variable copy_proc_id.

Retrying to create task in multi-step process which ID is defined by variable copy_proc_id (repeat 7). There can be many multi-step processes (copy_proc_id), but nodes for creating, modifying and retrying to create task (7, 8, 9, 10) - only in one copy.

If none of the given in node 2 conditions worked, then get proc_id of multi-step process from State diagram using unique ref = {{channel}}_{{chat_id}}.

Users

State diagram used to collect data about users of different messengers. This data is used to build dashboard to show statistic of different channels.

It is also used to store the attribute of language of the user's communication with a Bot (lang). Process Сommand Lang adds it when user makes a choice.
This parameter is used to choose object with text and buttons in process Send message.

Texts

State diagram for storage and control of text messages and buttons.
More details in section Manage message texts.

Operators calling

Modifying the task in State diagram by ref = {{channel}}_{{chat_id}} and transmitting the attribute chat = active.

Creating the task in State diagram with ref = {{channel}}_{{chat_id}} and transmitting the attribute chat = active in the case of error not_found_task of logic 1.

Command Lang

Modifying task in State diagram by ref = {{channel}}_{{chat_id}} with transmission of attribute of the current process (proc_id), command (command = lang) and messenger’s token (token)

Creating task in State diagram with ref = {{channel}}_{{chat_id}} with transmission of attribute of the current process (proc_id), command (command = lang) and messenger’s token (token), in the case of error not_found_task of logic 1.