Variables

In this section, you will find information about variables.

In the instructions for more complex tasks, it is possible to use variables. Below is a list of possible variables that allow Suvvy to understand the current parameters specific to a particular dialogue. All variables in the text are enclosed in curly braces { } and are divided into several types:

• Constants

• Variables related to channels (CRM, messengers, etc.)

Constants

Currently, one constant is used - the time constant. It allows the bot to understand the current time in the time zone specified in the additional settings.

{current_datetime}	Current date and time

Example of use in the instruction

#Current date and time
{current_datetime}

By default, the current date and time are embedded in the "service" instruction and are available to every new bot.

Variables related to channels

For some channels, it is possible to use the data coming from them to fill the instruction and expand the semantic context of Suvvy.

Such features are specifically available for channels like:

• amoCRM / Kommo

• Bitrix24

For amoCRM / Kommo, there are situations where we need to know from which channel (WhatsApp, Inst, Avito, etc.) the communication is taking place. Depending on the channel, we can provide the client with different information.

In this case, we can use the variable:

{origin}	Message source in the deal

By assigning this variable to another one, we can use it in the instruction for some special scenarios. Below is an example:

Using {origin}

Source_of_the_dialog = {origin}.
If the client wants to register:
- If Source_of_the_dialog = instagram_business, then the link: https://clck.ru/45D4LoB
- If Source_of_the_dialog = com.wazzup24-1, then the link: https://clck.ru/35D64LoX
- If Source_of_the_dialog = com.wazzup.whatsapp, then the link: https://clck.ru/74D4Lor

Here we assign the variable Source_of_the_dialog with the value of the source

Thus, the link that Suvvy will send to the client will depend on the source that came to us from amoCRM.