1. Script name

2. Creation of variables to be used as part of the script

The type of variables determines how they will be spoken by the system during the dialog. The system will be declining the date and amount in rubles depending on the number

1. Title of the block

2. Text of the question to be spoken by the system

3. List of phrases spoken bythe system in case of user’s no response*

4. Time duration the system awaits for the answer from user to finish the call**

• Short – 5 seconds
• Middle – 7 seconds
• Long – 10 seconds

• System 1 – Google recognition service
• System 2 – Yandex recognition service

6. If ticked, the system will recognize the user's emotional coloring and record it in the variable {detector.emotions}***

7. If ticked, the system will not be waiting for a response from the user, but will transfer it to the operator

8. If ticked, the system will not be trying to find response to the question through other blocks of the “Question” type, located on the same branch

* If there are more than one options, then phrases will be spoken in random order

** You can read more about recognition duration time here

*** You can read more about types of emotions here. (You can read more about types of emotion here

1. Title

2. Creation of a variable in which the system will record a response from the user

3. Data type that the system expects from the user to proceed to navigate through the branch

4. Name of the response button*

5. Determines display order of the button*

Thus, if we have a button with a serial number equal to 3 in one of the 4 development branches, then this button will be displayed penultimate in the list.

* Used for chats only

Navigation through the branch will be performed if the user's response matches the keyword.

1. Words or expressions that the system expects from the user to navigate through the branch

Enter keywords separated by spaces. Expressions shall be entered using quotation marks, i.e. “already on the spot”

It is also possible to use the abstract word NEAR in an expression that will mean any word, i.e.:“I am not going NEAR”, where NEAR can be any word: anywhere, ever, now, tomorrow, etc.

The system is provided with a balance system, when the explicit response “yes”from a person may not always denote recognition, i.e.: “Yes, I can clearly hear you, I am not going to lunch”.In this response, we can see the word “yes”and preposition “not”, which is of higher priority in the context, and is a negation in the general concept of the response: “I am not going to lunch”. Thus, when arranging keywords and expressions, it will be more explicit to add some “weight” to negative words: “+++no” and “+no”. Each plus sign has a unit of weight. Where the word or expression is one unit. Accordingly, in the example one word is added to the word “no”, and 3 words are added to the preposition “not”. In case of quantitative predominance, the decision making system will choose this route.

In the opposite situation, we alternatively can reduce the weight using the minus sign: “-yes”

2. Name of the response button (see description in the Arrow Properties)

3. Determines display order of the button (see description in the Arrow Properties)

For example, to match the delivery date of goods, it is possible to check that the date is greater than the current one in order to avoid the situation when the delivery will be arranged for the previous day.

If the year is not explicitly specified in the date, then the current one is applied

Also, this type is trying to determine the time. Possible variants:

• At 14:00
• In n minutes
• In n hours

If the user does not explicitly specify the time, then the current one is applied

3. Name of the response button (see description in the Arrow Properties)

4. Determines display order of the button (see description in the Arrow Properties)

Navigation through the branch will be performed if number announced by the user matches the number specified in the arrow properties.

1. Value Check Condition

For example, when conducting an opinion poll, the system may ask a question: “How old are you?”, and then ask different questions for various age groups according to specific conditions. 

The comparison follows the following rules:

{RECOGNIZED} {OPERATOR} {COMPARED}

Where 

• {RECOGNIZED} is the number that was recognized in the user's speech during the dialog
• {OPERATOR}is the comparison operator (less, more, equal, etc.)
• {COMPARED} is the value specified in the properties (see item No. 2)*

2. Response that the system expects from the user

3. Name of the response button (see description in the Arrow Properties)

4. Determines display order of the button (see description in the Arrow Properties)

* May contain variables enclosed in curly brackets, which can be transmitted when setting a task.

Navigation through the branch will be performed if the announced number of symbols in the number matches the number of symbols specified in the arrow properties.

1. Value check condition.

2. Expected input mask.

For example, for a passport we can set a mask of the form #### ######, where each symbol # denotes a digit.

3. If the system failed to recognize response or the user response does not match the specified one, then the system will not attempt to re-poll.

4. Value that the system expects from the user:

If a person during conversation denotes a number that will not fit the specified value, then the system will prompt the user to say the remaining digits until they exactly match the specified option in the script.

5. Name of the response button (see description in the Arrow Properties).

6. Determines display order of the button (see description in the Arrow Properties).

Navigation through the branch will be performed if the intention specified in the properties matches the already voiced intention of the user*:

1. System selection.

2. Agent selection.

3. Intentions that the system expects from the user.

4. Creation of variables in which data clarified by the system during the dialog can be recorded.

5. Name of the response button (see description in the Arrow Properties).

6. Determines display order of the button (see description in the Arrow Properties).

* To work with this type, established connection to Twin.ai and a trained agent are required. You can read more about it here.

Is used to receive data from the server.

It is possible to obtain data about the order, product, user, etc. using this type of request.

1. URL of the page we will be working with