# Requisites

Requisites are the main way to collect information from the user through Q&A.

They can be added to any Text or Event Trigger and your Virtual Assistant can ask for a single or multiple pieces of information from the user with a single Trigger!

You can be explicit when asking for information with Required Requisites, while Optional ones will possibly be filled from the user's initial message.

## Fields#

Requisites consist of the following fields:

Check for:

1. Checks if an Entity or Context Variable is present.
2. If the Check for is present, the user's answer must match the specific requested value. (Eg. requested values can be emails, payment methods, dates etc)
• Entity variables start with @ and Context Variables start with $. • You can check for nested context variables by doing things like $user.email
• Entity values are used for the specific Dialog.
• Context variables are saved for the whole session.

Save as:

• Used to save User's answer inside a context variable. If the save as field is not present, then the user's answer will not be saved in the Context.

## Medium Complexity Example#

In this example, the use of a mandatory requisite with a check for field is illustarted. More specifically, the Virtual Assistant is able to extract an answer from the user, which must be constrained with regards to a predefined Entity. As we can see from the example, when the Trigger for Booking a Flight is activated, the Virtual Assistant asks the user to fill an airline requisite. In this case the airline is an Entity and can only take two values: Delta and American Airlines. Thus, any answer from the user must belong in the airline entity. If not, then the requisite question (given by the if not present, ask field) will be asked again. This can also be seen from the Chat image below. It is worth noting that the type field is set to text in this case, as the expected answer is an airline.

Last updated on