Tags
To make items in the Content section conditional to a specific state we use conditions. Conditions can be based on the existence or non-existence of tags.
Any flow node can be configured to set a tag when executed.
Tags can also be set automatically by the system based on a context or system event.
System tags
This paragraph gives an overview of all the tags that are set by the system.
online
The conversation happens within office hours
offline
The conversation happens outside office hours
web_capable
The conversation happens on a weblike channel (PWA, widget or studio)
User tags
The following tags are automatically set based on the basic user fields for Name, Email, Phone and Language.
The Remember option in Ask Choice, Ask Open, etc will store the value in the user object as well as set a user tag using the Assign to property.
user:phone
The phone number of the contact is known.
user:name
The name of the contact is known
user:email
The email of the contact is known
user:mobile
The phone number of the user is a mobile number
Call status tags
For bots used on a phone channel the latest call status of the conversation will be annotated in the conversation using the following tags to be able to identify what happened to phone calls in the underlying phone system (pbx):
Language tags
The following tags will be set to annotate the language the conversation is in at any given time. It will be set at conversation start, but also when using the flow nodes ask: language and switch language.
For every supported language there is a tag available on your bot:
Custom tags
To use tags in Flows or other parts of the system it is recommended to explicitly configure them under Setting > Tags. This way both the system as well as you and your colleagues can understand what tags are set. The system tags are also listed here.
Last updated
Was this helpful?