Check for conditions to proceed

This trigger allows to have custom conditions to be checked before rest of the triggers can be processed.

One of the few possible scenarios can be

Collecting multiple fields before next trigger can be executed
Comparing user message with internal chat variable. E.g you set chat variable and later you want that visitor entered correct text.

Attribute supported placeholders

Attribute supports these placeholders

lhc.<main chat attribute> E.g lhc.email, lhc.nick, lhc.phone etc. See swagger for all attributes.
<identifier> - this can be either custom attribute Field identifier or just array key from chat_variables
<chat_variable> - identical to {args.chat.chat_variables_array.<variable_key>} It can be set using Update current chat response response type
So if you set variable bot_touched in attribute field you can use either bot_touched or {args.chat.chat_variables_array.bot_touched}
{args.chat.<main chat attr>} or {args.msg.msg} you can use text matching for visitor message.
online_department use as attribute to check is department online (respects department online hours). In value field 1 means online, 0 - means offline
online_op_department use as attribute to check is department online (ignores department online hours). In value field 1 means online, 0 - means offline

If you do not enter Value means it's empty.

E.g

so lhc.email != <empty> as in screenshot. Means I'm checking that e-mail would not be an empty string.
{args.msg.msg} I'm expecting message to contain one of the words dispute, chargeback, refund{2}, money back, contact bank. Refund word can have two typos.