Skip to main content

Text message


This article explains text element. Text element looks like for visitor

In back office it looks like this


Text message

Text message can have few sending options

  • {default messaget[show from hour, show till hour]} inclusive is first hour. Few examples
    • Default message
    • {welcome_message__Welcome to our website}
    • {good_evening__Good evening__t[17:24]} - Show this message from 17 until midnight
    • {good_morning__Good morning__t[0:17]} - Show this message from midnight until evening
  • You can give random answer by separating messages by ||| or just clicking

First message part before text message is text identifier and can be used to translating messages to multiple languages.

Replaceable variables

Text area supports these replaceable variables

  • {lhc.nick}
  • {}
  • {lhc.department}
  • {lhc.add.<field identifier>} - supports only first level attributes
  • {lhc.var.<variable key>} - supports only first level attributes
  • {<any chat attribute>} You can see all available variables using this modal window
  • {} - incoming chat id
  • {*} - first payload attributes in array format
  • {args.msg.msg} - visitor message.
  • {} - you can go as deep as you want to show chat variable
  • {} - access order_id from additionally defined chat variable which is stored as This variable is invisible for operator and will be stored in chat_variables attribute
  • {args.msg_text} - payload value if button/dropdown value click is unknown.
  • {<previous chat attribute>} This is usefull if on chat start you want to update present chat attributes based on previous one. This action should be executed on chat start trigger. Few examples
    • {} - access previous chat nick
    • {} - access previous chat chat variables
  • {msg_id} - present message id.
  • {args.current_trigger.<id|name>} - current trigger id. Stores current trigger
  • {args.first_trigger.<id|name>} - first trigger id. As during bot trigger execution multiple triggers can be involved this variables stores very first one.
  • {random_20} - generate random string length of 20
  • {*} - variables which were defined by extensions. Lear how to define your own custom variables.
  • {} Chat object also see __get method for magic attributes like
    • department or user
      • {} name visible in the widget or
      • {} name visible in the back office
  • {current_time_ts} current time in unix timestamp. E.g [dateformat=Y/m/d, H:i:s]{current_time_ts}[/dateformat]

These are the main classes

All classes can be found here

You can also set value from Rest API E.g

  • {content_1} up to {content_6} (these will be string values)
  • {content_1_json} up to {content_6_json} (will be already json encoded string). This is usefull in case you set chat variable

Escaping variables for url and [html] blocks

Escape arguments are supported only for {args.* syntax.

  • {} - escape argument in the url
  • {} - escape argument in the url
  • {} - escape argument in the [html]{}[/html] block.

This feature is used in Jitsi integration

Foreach cycle

You can foreach any chat variable. In this scenario we foreach chat variable

{foreach=args[chat.chat_variables_array.debts]} - {args.item.debt_organisation} for the value of {args.item.debt_value}

HTML message

Content of this textarea will be rendered as HTML directly. It also supports translations.

Example how to generate trigger button. Trigger in this case is 1355. Trigger ID you can see always in trigger menu.

To return to main menu click <a onclick='lhinst.updateTriggerClicked()' data-id="{msg_id}" data-payload="1355" class="action-image link-trigger-button">here</a>

Save as system message.

Message will be saved a system message and won't be visible by visitor. Might be usefull during Rest API calls integration if you want to store some information just for operators.

Save as a visitor message.

Sometimes you want to save a message as it was a visitor message.

Hide on next message.

This message will be auto hidden as soon there is at-least one other message after present one.

Render buttons as dropdown.

If you have many buttons. E.g countries you provide services. You can check this option and buttons will be rendered as dropdown options.

Render buttons even if it's not the last message.

This will render buttons even if buttons is not the last message in bot response.

Hide text area on response.

When this message is send area for a visitor to enter a message will be hidden. Make sure you include buttons in your response.

Send a message only at chat start

This message will be send only once and only on start chat event. If you have multiple triggers which is calling same text message. Sometimes it's usefull to have this.

Save as a log message.

Message will be saved as a log message.

Reaction options

Reaction allows to have reaction to bot message. They are visible for the operator in the back office.

  • Reactions are available only for bot text messages.
  • Operator can see reactions in the back office.
  • Future releases might add support for admin reactions to visitor messages.

Few samples how thumb reaction can be setup.

Row structure

<Material Icon>|<internal value>|<identifier>|<Title,<optional>>
  • Material icon - at the moment only thumb_up and thumb_down is supported.
  • Internal value - You can put number or string. It's value is stored as selected value for identifier.
  • Identifier - if multiple icons have same identifier other icon is unselected by value and new is selected.
  • Title - you can put title for the icon.

Message body sample using Material Icons.

thumb_up|1|thumb|Thumbs up
thumb_down|0|thumb|Thumbs down

Message body sample using native UTF reaction icons.

&#128077;|1|thumb|Thumbs up
&#128078;|0|thumb|Thumbs down

You can listen to reaction also using. Sample values are based on above samples

erLhcoreClassChatEventDispatcher::getInstance()->dispatch('chat.reaction_visitor', array(
'reaction_identifier' => $identifier, // `thumb`
'reaction_value' => $valueAction, // `0` OR `1`
'action' => $action, // `add` OR `remove`
'msg' => & $message, // Message object
'chat' => & $chat // Chat object
Styling reactions

For styling, you should use Widget themes -> Custom CSS -> Widget body additional CSS, takes effect after save section

Few samples

/* Have a different color for material icons thumb icons */
#messagesBlock .reaction-item,
#messagesBlock .reaction-item:hover {

/* Thumb down icons should be red reaction-id-thumb-0 => reaction-id-<identifier>-<internal value> */
#messagesBlock .reaction-item.reaction-id-thumb-0 {

#messagesBlock .reaction-item.reaction-selected {
/* Selected reaction item style */

/* Set various reaction bubble color options */
#messagesBlock div.reactions-holder {
background-color:blue!important; /* Set custom background color*/
border:1px solid red!important; /* Set custom border */
border-radius: 5px!important; /* Set custom border radius */

Reactions always visible.

Reaction icons will be always visible.

Webhook execution delay

In case you are running php-resque worker and your messages are not delivered in the order you write in the bot you can add delay to any next message.

Quick reply options

These options defines visible buttons under a message.


Just button name visible in frontend. Button names support translations by department

How to render button by department without cloning a bot?

Buttons are not rendered if their name is empty. In combination with bot translations you can have buttons to render for one department and empty for another.

Example of workflow if button should be rendered only for specific department.

  • If you want to render button for specific department put it's name like {<some_identifier>__} E.g {visible_for_a_department__}. Default value will be empty so button won't be rendered.
  • Create a translation with visible_for_a_department as identifier in translation group
  • Modify department and assign translations group.
  • Now bot will find button name in translation group and will render a button, but button won't be rendered for any other department.

Example of workflow if button should be rendered only for specific department.

  • If you want to render button for all departments put it's name like {<some_identifier>__Default name} E.g {visible_for_a_department__Default name} Default value will be Default name so button will be rendered.
  • Create a translation with visible_for_a_department as identifier in translation group. Do not enter any value in Default tab Translation field
  • Modify department and assign translations group.
  • Now bot will find button name in translation group and will not render a button, but button will be rendered for any other department.

'Precheck event' and 'Arguments`

Sometimes you want to show the button depending on some validation. E.g user is logged/is some third party service available etc. If you set precheck event like valid_username Live Helper Chat will dispatch event like

$validationResult = erLhcoreClassChatEventDispatcher::getInstance()->dispatch('chat.genericbot_handler', array(
'render' => $quickReply['content']['render_precheck_function'], // `valid_username`
'render_args' => $quickReply['content']['render_args'], // `Arguments`
'chat' => & $chat,

When in your extension you can listen for this and validate it like this.

In bootstrap.php file listen for an event

$dispatcher = erLhcoreClassChatEventDispatcher::getInstance();
$dispatcher->listen('chat.genericbot_handler', array($this,'genericBotHandler'));

Function could look like

function genericBotHandler($params) {
if ($params['render'] == 'valid_username') {
return array(
'status' => erLhcoreClassChatEventDispatcher::STOP_WORKFLOW,
'content' => array(
'valid' => false,
'hide_button' => true // You can just disable it by replace this line with `'disable_button' => true`


Type describes what type of action will be executed/rendered. There is four types of actions in total.


When visitor clicks a button we will open defined URL just as a link.


This will issue defined payload. It's usefull if you are integrating third party AI bots. As this event can be passed to them.

Update Chat

These are quick updates you can do on button click. There are three types of events you can do from quick replies.

  • Transfer to operator [Depreciated] - I would personally just use Execute trigger and define a trigger where response type is Update current chat as then I can define more flexible transferring workflow.
  • Transfer to bot [Depreciated] - Like an above written I prefer that workflow instead.
  • Subscribe to notifications - this is usefull to define in default auto responder trigger and suggest visitor subscribe while they are waiting for an operator to accept a chat.
  • Execute trigger - it's my preferred way to set actions as you can choose defined triggers from the list.
  • Minimize widget - usefull in case you are showing intro button and want that one of them would minimize a widget. It can be used in proactive invitations also.

Store name

If you enter Store name button click will be recorded within chat in additional_data als you will recorded button click within chat itself.

Store value

If you enter Store value it will be used as value instead of button name.

Button ID

We will set this DOM element ID as defined in this field.

Bot conditions to satisfy

You can enter condition Identifier read more about conditions

Idea is that this button will be shown only if condition is satisfied, otherwise button will be hidden.

You can enter multiple conditions and all of them has to be satisfied.

and condition itself can look like this

Add action on message

These are quick updates what happens on a message. I would suggest just use Collect custom attribute response type. See example how to use it.


Syntax for simple buttons looks like. This can be send directly as a meta_msg body to 

"_id": "Hkhov7S77",
"type": "text",
"content": {
"text": "Here is sample element",
"quick_replies": [
"_id": "HJRmO7HQ7",
"type": "button",
"content": {
"name": "Button",
"payload": "about_us"
"_id": "S1TVdXSQm",
"type": "url",
"content": {
"name": "",
"payload": "https:\/\/"