Dialogic

Designing Effective Scenarios in Dialogic

Scenarios are the foundation of engaging, impactful learning experiences in Dialogic. Each scenario is built around a set of parameters that shape the interaction between the student and the AI interlocutor. Understanding these parameters and how to use them effectively will help you create meaningful and dynamic learning environments.

Below is a breakdown of the key scenario parameters and considerations for creating effective scenarios:

Scenario ID

    • What it is: A unique identifier for each scenario.
    • Purpose: Makes it easy to reference and organize scenarios within the Dialogic library.
    • Best Practices:
      •  
        • Use short, memorable codes (e.g., HIST1 for a history scenario or PHYS2 for physics).
        • Avoid duplicate IDs, as they will be flagged automatically.
        • Keep a consistent naming convention for easier tracking.

Scenario Name

    • What it is: A descriptive name visible to the student.
    • Purpose: Gives the student a clear idea of what the scenario is about.
    • Best Practices:
      •  
        • Be clear and engaging (e.g., “Rescuing an Astronaut” is better than “Physics Lesson 1”).
        • Match the tone to the subject—exciting for adventurous topics, professional for business skills.

Hint Link

    • What it is: A URL to supplementary resources that the student can use for guidance during the conversation.
    • Purpose: Provides additional context, hints, or background information to support the student’s interaction with the interlocutor.
    • Best Practices:
      •  
        • Use clear, reliable, and relevant resources (e.g., articles, videos, or slides).
        • Ensure the link is accessible and appropriate for the student’s level.
        • If no hint is necessary, leave the field blank to keep the activity focused.

Category

    • What it is: The subject or topic area of the scenario.
    • Purpose: Provides broad context for both the teacher and the student.
    • Best Practices:
      •  
        • Keep it concise yet specific (e.g., Biology, American Revolution).
        • Use familiar categories students can relate to, such as school subjects or skills.

Interlocutor Avatar

    • What it is: A visual representation of the AI interlocutor.
    • Purpose: Makes the interaction more relatable and engaging.
    • Best Practices:
      •  
        • Choose avatars that fit the tone and role of the interlocutor.
        • Use high-quality, appropriate images—store them on Google Drive for easy access.
        • Avoid generic or overly abstract visuals.

Language

    • What it is: The language in which the scenario is written and will take place.
    • Purpose: Ensures the AI communicates in the desired language.
    • Best Practices:
      •  
        • Specify the language clearly (e.g., English, Spanish).
        • Use this field to adapt the scenario for multilingual classrooms.

Age / Level 

    • What it is: The target age or level of the students
    • Purpose: Helps the large language model modulate its language and the concepts deployed during the scenario
    • Best Practices:
      •  
        • Be explicit (e.g., high school freshmen, B1-level ESL students).

Skills

    • What it is: The specific skills being targeted in the scenario.
    • Purpose: Provides clarity to students about the focus of the activity.
    • Best Practices:
      •  
        • Be explicit (e.g., critical thinking, debate skills, vocabulary practice).
        • Use this parameter to reinforce the learning objectives.

Scenario Description

    • What it is: A brief explanation of the scenario visible to the student.
    • Purpose: Sets the context and expectations for the interaction.
    • Best Practices:
      •  
        • Be concise but informative. Avoid overwhelming the student with too much detail.
        • Use the [student] shortcode to have the student’s name inserted automatically. 
        • Use language that is accessible to your audience’s skill level.

Interlocutor Name

    • What it is: The name of the AI character in the scenario.
    • Purpose: Personalizes the interaction and enhances engagement.
    • Best Practices:

        • Choose memorable, fitting names (e.g., Professor Abbot, Ziegfried the Engineer)
        • For fictional or historical figures, use the correct name and include relevant context in the role.

Interlocutor Role 

    • What it is: The role the AI interlocutor will play in the scenario.
    • Purpose: Provides the AI with instructions about its identity and behavior.
    • Best Practices:
      •  
        • Be detailed and specific (e.g., “A 19th-century art dealer skeptical of Van Gogh’s work”).
        • Use the [student] shortcode to have the student’s name inserted automatically. 
        • Use adjectives to give the AI personality (e.g., eccentric, knowledgeable, curious).

Opening Message

    • What it is: The first message from the interlocutor to the student.
    • Purpose: Captures the student’s interest and sets the tone for the conversation.
    • Best Practices:
      •  
        • Start with an intriguing statement or question.
        • Match the message to the role and context (e.g., “Quick! I need your help decoding this map before the enemy finds us!”).
        • Always end with a question or prompt to encourage a response.
        • Use the [student] shortcode to have the student’s name inserted automatically. 

Special Instructions

    • What it is: Instructions for the AI that shape its behavior and responses during the interaction.
    • Purpose: Ensures the AI adheres to the scenario’s educational goals.
    • Best Practices:
      •  
        • Provide clear, concise instructions.
        • Use the interlocutor’s name frequently to reinforce its identity and role.
        • Avoid overly complicated instructions; simplicity ensures better AI performance.
        • Use the [student] shortcode to have the student’s name inserted automatically. 

End Type

    • What it is: The condition that determines how the conversation ends (e.g., time-based or exchange-based).
    • Purpose: Controls the duration and pacing of the scenario.
    • Best Practices:
      •  
        • Use time-based for open-ended discussions or writing practice.
        • Use exchange-based for structured, predictable interactions.

End Value

    • What it is: The specific time or number of exchanges at which the scenario ends.
    • Purpose: Provides a clear endpoint for the interaction.
    • Best Practices:
      •  
        • For most scenarios, aim for 10-20 minutes or 10-15 exchanges.
        • Adjust based on the complexity of the topic and student engagement.

Wrap-up Value

    • What it is: The point at which the AI begins concluding the conversation.
    • Purpose: Ensures a smooth transition to the closing message.
    • Best Practices:
      •  
        • Set this parameter slightly before the end value (e.g., 8 minutes for a 10-minute conversation).
        • Use wrap-up instructions to reinforce key points or encourage reflection.

Wrap-up Instructions

    • What it is: Special instructions for the AI during the wrap-up phase.
    • Purpose: Guides the AI in summarizing or closing the conversation effectively.
    • Best Practices:
      •  
        • Prompt the AI to summarize key points or provide constructive feedback.
        • Encourage reflective questions (e.g., “What do you think was the most important idea we discussed?”).
        • Use the [student] shortcode to have the student’s name inserted automatically. 

Closing Message

    • What it is: The final message from the interlocutor to the student.
    • Purpose: Provides closure and leaves a lasting impression.
    • Best Practices:
      •  
        • Make it friendly and encouraging (e.g., “Great job today! I hope you’ll help me again soon.”).
        • You can opt for an automatic closing message, generated by the LLM. Provide instructions (for example, to provide feedback to the student on their conversation) or leave it blank for a generic, automatically generated closing message.  
        • Optionally include a call to action, like a follow-up scenario or reflection exercise.
        • Use the [student] shortcode to have the student’s name inserted automatically. 

Autoplay

    • What it is: A feature that enables the interlocutor to initiate the conversation without waiting for the student’s input.
    • Purpose: Sets the tone, provides immediate context, and jumpstarts the conversation to create a dynamic learning experience.
    • Best Practices:
      •  
        • Use for scenarios that benefit from a clear, engaging opening.
        • Craft a strong first message that hooks the student’s interest.
        • Avoid using Autoplay if the student needs time to review the scenario first.

Gender 

    • What it is: A setting for selecting the gender of the interlocutor’s voice when Google Text-to-Speech (TTS) is enabled. Options include “Male” and “Female.”
    • Purpose: Aligns the audio presentation of the interlocutor with the character’s persona to enhance immersion.
    • Best Practices:
      •  
        • Choose a gender that aligns with the scenario’s context and character.
        • For non-binary or gender-neutral characters, leave the field blank or select a voice that fits the tone of the scenario.
        • Test the voice to ensure clarity and appropriateness for your students.

Dialect 

    • What it is: A setting that specifies the regional accent or dialect for the interlocutor’s voice when Google TTS is enabled.
    • Purpose: Adds cultural and linguistic authenticity to scenarios, enhancing student engagement.
    • Best Practices:
      •  
        • Use dialects that fit the scenario’s setting (e.g., British English for a London-based scenario, American English for a U.S.-based one).
        • Refer to the TTS Language-Dialect Codes for supported options.
        • Ensure students are familiar with the chosen dialect to avoid unnecessary confusion.

State

    • What it is: A setting that determines whether a scenario is “Active” or “Inactive.”
    • Purpose: Controls the availability of scenarios in the Dialogic library. Active scenarios are accessible to students, while inactive ones are hidden.
    • Best Practices:
      •  
        • Set the state to “Inactive” for scenarios still in development or not ready for use.
        • Regularly review and update the status of scenarios to keep your library organized.
        • Use “Inactive” for scenarios that are seasonal or tied to specific lessons, and reactivate them as needed.
        • Check the state of scenarios before sharing your app link with students to ensure only appropriate ones are visible.
      •  
Youtube Linkedin X-twitter Envelope

© 2025-2026 LQD Research. All rights reserved.