Who Is the Agent Talking To? Participant-Aware Role Switching for Embodied Student-Support Dialogue

summary

The gist

RPO-PDT presents a retrieval-grounded, role-play-based dialogue system for adaptive student support in higher education.

In short

This work introduces a system that allows students and tutors to switch roles dynamically during embodied dialogue. It uses participant-aware role switching to adapt support strategies based on who is speaking, leading to more natural and contextually appropriate student support interactions.

Key concepts

Participant-Aware Role Switching
This mechanism explicitly tracks whether the current speaker is the tutor or the student. The system uses this information to adjust its conversational approach—for example, changing how it offers advice or questions based on whether it is guiding a tutor or responding to a student.
Embodied Interaction
This refers to dialogue that involves physical presence and non-verbal cues, specifically using robots like Furhat. It means the interaction goes beyond just text; the system can use speech, gaze, and facial expressions to make the support feel more human and natural.
Role Switching State Slot
The system maintains a specific memory slot that stores the current active role (tutor or student). This is a command-driven mechanism ensuring that the dialogue always knows who it is currently addressing, preventing accidental role confusion during complex conversations.
Adaptive Dialogue Strategy Generation
The system generates different support responses by retrieving and reusing previously successful strategies based on the current interaction context. This allows for online adaptation of communicative behavior without needing to fully retrain the underlying model.

Terminology used across episodes

This episode discusses

The paper

Who Is the Agent Talking To? Participant-Aware Role Switching for Embodied Student-Support Dialogue · Read on arXiv

Filip Janik, Ewa Olton, Robert Smales, Harris Spratt, Shea Tait, Md Zia Ullah, Yanchao Yu

Edinburgh Napier University

We present RPO-PDT, an embodied conversational agent that adapts its conversational role to the current participant. It acts as a Per- sonal Development Tutor (PDT) when supporting students and as a simulated student when faculty rehearse tutoring strategies. Voluntary closed-set participant verification informs a confidence- controlled role manager: stable enrolled-faculty matches activate the Student role, while enrolled students and unmatched partici- pants use the default PDT role and uncertain observations cause no transition. The system combines Furhat interaction, Rasa or- chestration, institutional retrieval, safeguarding, and LLM-based generation. User control is preserved through manual role override, consent-based facial enrolment, temporary interaction identifiers, and explicit retention or deletion of enrolled profiles. The demon- stration exposes both role-switching behaviour and these privacy controls in interaction.

DOI: 10.1145/3841580.3845752

Transcript

Introduction to the show: ident: Robotics Radio. Generated commentary on the latest robotics and control papers.

Rosa: I'm Rosa.

Dev: And I'm Dev, here with Taro.

Rosa: We're looking at the paper: "Who Is the Agent Talking To? Participant-Aware Role Switching for Embodied Student-Support Dialogue".

Dev: Here's the gist of the paper. RPO-PDT presents a retrieval-grounded, role-play-based dialogue system for adaptive student support in higher education.

Rosa: RPO-PDT is able to provide institution-specific Personal Development Tutor (PDT) guidance using structured knowledge sources and is designed around a reverse-roleplay loop where unresolved interactions are replayed from the student perspective, enabling alternative tutor strategies to be generated and stored as reusable strategy memory.

Dev: This system supports both textbased and Furhat-based embodied interaction for demonstrating grounded, safe, and adaptive student-support dialogue.

Rosa: System Architecture and Components RPO-PDT is implemented using a modular architecture that combines Rasa-based dialogue orchestration, structured institutional knowledge sources, policy-constrained LLM generation, deterministic safety escalation, and an optional Furhat robot interface.

Title and authors: Rosa: They start by introducing RPO-PDT and how it provides institution-specific Personal Development Tutor guidance using structured knowledge sources. This grounding is key for making sure the advice is locally accurate.

Dev: The paper mentions they use YAML files as lightweight stores for all that knowledge, including course lookups and university support service information.

Rosa: And they also stress that the system is constrained by explicit persona, boundary, confidentiality, and safety policies embedded right into it.

Taro: That constraint mechanism sounds important because it’s not just letting an LLM talk freely; there are hard rules governing what the agent can actually do or say.

Dev: And they detail a deterministic safety escalation layer that checks both the user input and the generated response for risk levels like low, high, or crisis.

Rosa: The paper shows this safety layer is always active, checking for things like crisis disclosures and signposting to resources instead of just relying on generative modeling.

Taro: I wonder how robust that deterministic check is when dealing with complex human language; does it catch everything or just the obvious crises?

Dev: They say the purpose of that guideline isn't to make clinical judgments but to promote conservative support behaviors, meaning it steers the agent away from things like making medical diagnoses.

Rosa: It’s about ensuring that even when the system is trying to be helpful, it stays within safe operational boundaries defined by those YAML stores.

Taro: So for someone who only listens to this show, what does that safety layer actually mean in practice for the student interaction?

The paper's summary: Dev: The core concept they summarize is RPO-PDT’s ability to provide grounded support while actively learning from past interactions.

Rosa: They focus on the reverse-roleplay mechanism again, explaining that if a case isn't resolved, it gets stored in a strategy memory.

Dev: When we replay that unresolved case from the student's perspective, the system generates alternative tutor responses and saves them as reusable strategies for future use.

Taro: So it’s not just about solving one problem; it’s about building a library of successful ways to handle difficult situations based on past failures or unknowns.

Rosa: That ability to adapt based on stored cases, rather than changing the underlying model weights, is a big piece of information here.

Dev: They also summarize the architectural setup: Rasa for dialogue orchestration combined with policy-constrained LLM generation and this strategy memory component.

Taro: And they show that this entire setup supports both text-based and embodied interaction via Furhat to demonstrate grounded support dialogue in a more natural way.

Rosa: Basically, they’re showing how retrieval, safety control, and embodiment can all work together to create a system that actually adapts its communication style over time.

Dev: It’s moving towards systems that are less about predicting the next single word and more about managing a sequence of interactions based on what has worked before.

The paper's improvements: Rosa: The authors suggest improving the system by focusing on making those stored strategies truly reusable and adaptable to new situations, not just directly mapping to the old case.

Dev: They highlight that they are moving beyond simple case retrieval toward a mechanism where alternative responses can be generated and compared against each other dynamically.

Taro: So they are suggesting a system where the agent tries several different approaches based on the stored memories and selects the best one for the current context, which is an improvement over just retrieving a single stored answer.

Rosa: They also emphasize that this entire adaptation happens through retrieval and reuse of these cases and strategies, rather than having to update any of the main model weights.

Dev: That shift from parameter-updating to strategy memory is what makes the online adaptation possible without needing a full retraining cycle for every new scenario.

Taro: If you can adapt behavior this way, it means the system can handle novel student queries in a way that feels more personalized and less like it's following a rigid script.

Rosa: And they also point out that they are exploring how to integrate human-in-the-loop validation for these reusable support strategies in the future work section.

Conclusion: Dev: To wrap up, RPO-PDT is a retrieval-grounded system that uses institution-specific knowledge and policy constraints to provide grounded student support.

Rosa: The key contribution is the reverse-roleplay loop which allows for generating and storing alternative tutor strategies as reusable memory for online adaptation.

Dev: It successfully combines text and embodied interaction with Furhat to demonstrate this adaptive dialogue in a setting that feels more real for the user experience.

Taro: For someone listening, it means we’re seeing how an AI can manage complex support interactions by learning from its mistakes in a safe, constrained environment.

Rosa: It shows how you can build systems that maintain clear role boundaries while still being flexible enough to offer different supportive approaches depending on the student's situation.

Dev: We’re looking at a system that uses stored past interactions to inform future actions, keeping things grounded by those institutional knowledge files and safety policies.

Taro: It’s about creating a support dialogue agent that doesn't just answer questions but learns how to handle the messy parts of student interaction over time.

More episodes

← Home