Description of the fields in the Editor
Detailed description of the assignment of each editor field
Last updated
Detailed description of the assignment of each editor field
Last updated
Consider more about the shape of blocks and the shape of connections, how to use them and what they are needed for.
The picture below presents the "Text Message" form. By default, it is a reduced form.
To expand the full view of the form, press "Advanced Settings", "Button Settings" and "Attachment Settings". Then the form will take this form. In fact, after filling in this form, a block with some data/settings will appear on the field.
Let’s start with the main fields, it's very IMPORTANT to understand how to use them in the editor.
Answer: in this field you specify the text that will come to the user in personal messages. You can leave the field blank - for example, you just need to send a picture without accompanying text.
In addition to the text you can specify variables as #{variable} so their value will be displayed. You can write mathematical actions instead of a variable, for example#{2 + 2} will output 4
Dialogue State: The field that determines the block type. For more information about block types, read article
Description: In this field you can specify a brief description of the purpose of the block. Useful for structuring the logic of the bot helps not to get confused if you are working on a complex project with a large number of blocks. By default, the text is taken from the "Answer" field. The bot is not affected by this field.
Request Type: This field is a drop-down list for working with third-party APIs. The bot’s interaction with third-party APIs is described in detail in this article
​
You can perform logical or arithmetic actions in this field. You can assign a variable to a person who has entered this block or assigned existing variables. For example, it will be useful when creating a funnel or tracking the source of traffic. Working with variables requires separate detailed consideration. You can read about using variables here
​
Pipeline State: Here you can choose what condition the Salebot CRM sales funnel will place the customer when you switch to this unit. It is convenient not only for promotion of the client through the stages of the funnel, but also for visual segmentation of clients by categories. For example, applications from knitters in one column and sewing - in another column Salebot CRM.
Show buttons: By default, this slider is enabled and buttons are displayed to the client.
Show arrow keys as buttons: by default, this slider is enabled and the arrow(s) conditions from this block are displayed as buttons
The "Hint in Keyless Messengers" field is required when your bot should be running in Whatsapp and another messenger at the same time. Since Watsap does not support buttons, in this box you can offer users text with a digital menu. It will only be displayed in Watsap. It is used to navigate inside the bot (Figure 4).
The "Advanced Button Settings" field (Figure 5) is used to create the on-line buttons in the text). Read more about them here The following three fields are designed to work with attachments
URL attachment: here you can enter a link to a file or picture on the Internet.
Browse...: download the file/picture directly from the computer for further sending to the client.
Attachment type: a field designed to select the attachment type. There are 6 types. Their difference and how to use them correctly read here
If an attachment is added to the block, the "Delete attached file" option appears among the available block actions, as in Figure 7:
Now let’s look at the fields of the join form (Figure 8)
Delay before reply: This field specifies the time after which the bot will reply to the person. Time can be measured in seconds, minutes, hours and days. If such a connection is made from the block, the transition will be made automatically. This function is used to send automatic messages that do not require a user response.
Cancel when you switch to another block: Enable this slider if you want to abort the automatic message chain if the user has done something and has moved to another block.
If the slider is enabled, all scheduled timers will be canceled during the arrow jump, except where "Do not cancel" is enabled
This setting will prevent the timer from being reset even if the other arrows are enabled to "cancel messages with timer"
Sending time with delay: the bot will send a message at the specified time and add a delay from the "Delay before response" field. If the time has passed on the day of the message and you have set the slider "Send if the date has passed", it will be scheduled for tomorrow. You can use the variable in Figure 9 to specify the time. To do this, click the white arrow to the right of the field and enter the name of the variable.
Date of dispatch with delay: the bot will send a message on the specified day (at 00:00 hours) and add a delay from the field "Delay before response". It is best to specify the time when the message was sent in the field above at the same time. You can use the variable in Figure 9 to specify the date. To do this, click the white arrow to the right of the field and enter the name of the variable.
Condition: Condition of transition to another block. Described in detail in this article
Condition Type: The default setting is "Ignoring errors and inaccuracies". There are 4 types of condition checking:
Ignoring errors and inaccuracies: this means that the condition will be checked for a partial match with the text entered by the user. That is, if the user has entered a word or phrase with errors or another ending, the condition will work.
By keyword availability: If you select this condition, if you have at least one keyword from the field "Condition", the transition will work.
Perfect match: This condition checks a word or phrase for a perfect match, without errors or alterations.
Regular expression: The condition checks the user’s response in the regular expression you specify. For example, the correct input of the phone format, email, enter only numbers, etc. You can learn more about regular expressions read here
Strings to which you do not need to answer: here you enter "minus-words", words to which the bot should not respond when checking the condition.
Comparison variable: the connection condition will be compared to this variable. It is necessary to specify without #{}, only the name of the variable. Convenient to use when filling in the form and comparing with the entered condition. In the example in Figure 10, the transition will be made if the value of the RETURN_TO_MENU variable is True. Don’t forget to disable the "Display as button" slider to prevent the user from being shown the True button.
For additional features of the field, see the link
​
Priority field: The default setting is 10. The higher the priority of the condition, the earlier it will be checked.
Skip once per dialogue: if this slider is enabled, the user will be able to get into this block only once while communicating with the bot. It is convenient to use if there are blocks of "Start dialog" with popular keywords, for example, the word "Hello". If a user writes this word while logging in to a bot and the "Answer once for a dialog" slider is enabled, the bot will ignore this word from the user in the next dialog. In quick answers we also recommend using this functionality to avoid errors in communication with the bot. Read more about quick answers in this article
Description: A field similar to the field "Description" in the form of creating blocks.
User enters data: When this switch is enabled, an additional field "Input data" appears. You need to enter the name of the variable into which the user’s response will be recorded. The variable name is entered with one word. The variable is case sensitive. In the example in Figure 11, the user’s response will be written into the variable "User’s response":
Button Settings: By default, the "Display as Button" switch is enabled. If this is not necessary, just turn it off. Also in this subsection, you can align and arrange buttons and change their color. Works only in messengers where buttons are supported.
​
​
