Help Center/ Cognitive Engagement Center/ User Guide/ Tenant Administrator Guide/ Robot Management and Configuration Guide/ Operator: Configuring an Intelligent Robot/ FAQs/ How Do I Configure the Scenario Where Multiple Slots Are Filled Repeatedly?

How Do I Configure the Scenario Where Multiple Slots Are Filled Repeatedly?

Description

To enable a customer to interact with the chatbot to order a meal, the system needs to obtain the slot information such as the order date, time, and number of diners. The slot information that has been filled in needs to be updated at any time during the interaction with the robot.

For example, when a customer says "6:00 p.m. tomorrow, three persons", the system needs to record the information in the slots. When the customer changes his or her mind and says "7:00 p.m." during confirmation, the system needs to fill the new time in the slot.

The existing processing mode of the ODFS has the following problem: If the system uses mandatory slot information verification of the intention template, the slot information that needs to be updated cannot be updated immediately. If the system clears the context to fill in the slots again, the slots that do not need to be updated are also cleared.

Solution

Use the following method to support the scenario where a customer changes information repeatedly in multiple rounds of dialogs:

  1. During intention template configuration, all slots are made optional slots. In this way, the TUC does not cache the filled slots in an intention. Wait for the next interaction to obtain the information about the next slot. In this way, the problem of failing to update filled slots is avoided.
  2. Add the judgment logic for returning different command words based on slot information on the Response tab page.

  3. On the flow orchestration page, the system determines the branch of the command word returned by the intention based on the flow and plays different voices accordingly.

    For each identification interaction, slots are filled. Different intention codes are returned to the dialog flow for one or more slots filled. The dialog flow caches the slot information obtained in each interaction to the flow variables. In this way, the content filled in the slots can be updated according to the information cached by the ODFS each time the identification is performed.

Parent topic: FAQs