Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Test Greeting Patterns

    • Test the basic greeting pattern by running the agent and initiating interaction from the Start page.

    • Set the agent’s name in dialog_init.mod2g and verify self-identification functionality.

  2. Test User Response Variations

    • Provide non-greeting inputs to test the agent’s response and inspect session updates in Debug mode.

Instructions

[TBU]Greet, and Self-Identify

3. Request a Random Recipe Recommendation

...

  1. Test Recipe Recommendation

    • Add a50recipeSelect to the agenda in dialog_init.mod2g and verify the agent's ability to:

      • Ask for recipe preferences.

      • Respond with a random recipe recommendation.

  2. Test Recipe Confirmation

    • Ensure the agent correctly displays the recommended recipe and allows user confirmation.

Instructions

[TBU]Request a Recommendation

4. Select Recipes by Name

...

  1. Test Recipe Request Handling

    • Add the new pattern to the agent’s agenda in dialog_init.mod2g after the c10 pattern.

    • Test the interaction flow:

      • Agent asks for a recipe.

      • User requests a specific recipe.

      • Agent acknowledges the recipe choice and moves to the confirmation phase.

  2. Verify Intent Recognition

    • Check the Dialogflow Training Tool to confirm the recipeRequest intent is recognized.

    • Verify the SIC server logs show the correct intent and transcript.

  3. Handle ASR Failures

    • Use the chatbox feature to avoid ASR failures and ensure the agent can handle specific recipe requests reliably.

Instructions

[TBU]Select Recipes by Name

5. Filter Recipes by

...

Implementing this capability will involve implementing some of the conversational and reasoning competences that a conversational recipe recommendation agent should have. It will enable users to request recipes which use specific ingredient (types) or ask for recipes from a specific cuisine. This one of the capabilities that requires quite a big amount of work. Some of the bigger challenges will be to make Dialogflow understand ingredients (at least those that are in our database; and cuisines, for that matter, but those are fewer), to implement the logic to filter the recipe database with the feature requests of a user, and to present those in a nice way to the user on a webpage.

Summary Description

...

bgColor#DEEBFF

A: What recipe would you like to cook?

Inclusion

Summary Description

Panel
bgColor#DEEBFF

A: What recipe would you like to cook?

U: I'd like to make a recipe with ____ *.

A: All the recipes left include ____ *. Do you want to add another preference?

  • insert name of an ingredient (type) or cuisine here

Implementation Tasks Overview

Instructions

[TBU]Filtering by Inclusion

Unexpected Intents

Summary Description

...