Post by account_disabled on Feb 28, 2024 6:31:59 GMT
The Dialog Flow platform is able to predict based on subsequent experiences where the most significant expressions will appear while ignoring distractors expressions irrelevant to the problem discussed in the conversation . Types of units Dialog Flow has three types of units. I will try to explain their main uses, as well as outline the most important differences between them. System entity These are the default units for Dialog Flow. These include the most common elements you may encounter in conversations with people. These include date and time, numbers, values expressed in various units weight , contact and geographic details, as well as names and surnames.
We recognize this type of units by the name sys. Unit_name . The database is very extensive, and the full list can be found in the documentation of the platform itself. Developer entity These are units that you can create yourself and according to your needs. They are based Chinese Europe Phone Number List on a list of keywords or phrases that match the set of a given concept. The more extensive the list, the greater the agent's ability to recognize the needs of our interlocutors. Moreover, we can supplement such a collection with synonyms of individual expressions to further enrich the ability to understand our application.
The bicycle service discussed as an example could create the bike-type unit and place in it all expressions defining the type of bicycle bicycle, two-wheeler, bicycle, lady, BMX . An interesting feature is "automated expansion". It allows Dialog Flow to identify words or phrases not highlighted on the list that match our entity. User entity These are specific units created for specific conversations with users. They allow the use of data that already exists or is available for a short period of time. This may be, for example, a list of recent orders or current promotions. Dialog Flow allows you to set a list of required data necessary to execute the intention.
We recognize this type of units by the name sys. Unit_name . The database is very extensive, and the full list can be found in the documentation of the platform itself. Developer entity These are units that you can create yourself and according to your needs. They are based Chinese Europe Phone Number List on a list of keywords or phrases that match the set of a given concept. The more extensive the list, the greater the agent's ability to recognize the needs of our interlocutors. Moreover, we can supplement such a collection with synonyms of individual expressions to further enrich the ability to understand our application.
The bicycle service discussed as an example could create the bike-type unit and place in it all expressions defining the type of bicycle bicycle, two-wheeler, bicycle, lady, BMX . An interesting feature is "automated expansion". It allows Dialog Flow to identify words or phrases not highlighted on the list that match our entity. User entity These are specific units created for specific conversations with users. They allow the use of data that already exists or is available for a short period of time. This may be, for example, a list of recent orders or current promotions. Dialog Flow allows you to set a list of required data necessary to execute the intention.