1. Description

The page for setting the display of messages from the system.

Consists of fields (Fig.1):

Fig. 1. Templates

Available in:

The ability to describe specific update templates for a particular message gateway has been provided:

Update	Usage	Field	Sender	Recipient
title	Header format of new, incoming chat	Workspace member's name	Member	User/Agent
close	The static chat end message	Chat complete message	–	Member
join	Participant connection message format	Agent joining message	User/Agent	Member
left	Participant disconnection message format	Agent disconnection message	User/Agent	Member

The template syntax for the text/template package can be found here.

Actions - evaluations of data or control structures - are separated by $( and ) .

For example, the corresponding templates might look like this:

Update	Message template
close	`🎈 Dialogue completed!`
join	`👤 __$(md2 .FirstName)$(if .LastName) $(md2 .LastName)$(end)__`
left	`👤 ~$(md2 .FirstName)$(if .LastName) $(md2 .LastName)$(end)~`

If in the Agent disconnection message field enter:

👤 ~*$(md2 .FirstName)$(if .LastName) $(md2 .LastName)$(end)*~

then when the Agent disconnects, the chat will display the name of the Agent who left the chat.

Specific to telegram-* providers only

1.1. Workspace member's name

Here you enter the text or template displayed for the agent's incoming chat. Anonymous name of the subscriber, for example.

Here you enter the text or template displayed to the subscriber when the Agent connects to the chat.

Here you enter the text or template displayed to the subscriber when the chat is closed.

Here you enter the text or template displayed to the caller when the Agent has left the chat.

To anonymize incoming chats, enter the text, for example:

Anonymous

In this case, templates, as such, are not used at all. The constant is described here.

All incoming chats from the gateway for which such a template is described will be displayed as Anonymous.