A guide for admins and faculty on the data behind Dialogue activities
Purpose
When you assign a Dialogue activity, a voice or text conversation with an AI character built around your course content, you're introducing a new kind of learning tool into your classroom. This page explains what data Dialogue collects, why it's collected, and how it can help you understand what's happening in your course.
During a Dialogue Session
A student has a conversation, spoken or written, with an AI character designed around your course or assignment. That conversation is the activity itself. Everything described below comes directly from that interaction, nothing is collected separately or without the student's participation.
Quick Reference: What We Capture
| Data Type | What It Tells You | Captured By Default? |
|---|---|---|
| Session record (who, when, duration) | Whether and how long students engaged | Yes |
| Full transcript | What the student actually said or wrote | Yes |
| Rubric scores | How the student performed against defined criteria | Only if a rubric is attached |
| Usage patterns (repeat attempts, text vs. voice) | Whether students are engaging as intended | Yes |
| Student feedback (post-session prompt) | How the experience felt to the student | Yes - Coming soon |
| Audio recording | — | No, conversations are transcribed, audio is not stored |
Why We Capture This
Data collection is built around three questions faculty consistently ask:
- Is it working? Transcripts and rubric scores show the actual quality of student reasoning, not just whether they completed the activity.
- Is it fair to my students? Session data helps confirm the activity isn't confusing, disruptive, or leading students astray.
- Can I trust the results? Because the conversation itself is the assessment, it's harder to fake or shortcut than a written assignment alone.
This data is meant to support your judgment, not replace it. A rubric score is a starting point for review, not a final verdict. Your read on a student's work, and your relationship with that student, stays central.
What We Don't Capture
- No audio storage. Voice conversations are transcribed to text; the recording itself isn't retained.
- No use outside the activity. Nothing about a student's engagement with Dialogue affects anything beyond that specific assignment.
Who Can See This Data
Access is scoped to your administrator, faculty, course and institution and connects to your existing LMS roster and course. Data isn't shared outside your institution's environment.
Common Questions
Will this replace my grading? No. Rubric scores and transcripts inform your evaluation; they don't substitute for it. You decide what weight this data carries, if any, in a grade.
Can students game this? Because the conversation is adaptive and happens in real time, it's harder to script or fake than a written assignment. Still, no tool is foolproof; treat unusual patterns as a starting point for a conversation with the student, not an automatic conclusion.
Can I see more detail than what's shown by default? Reach out to your program's Dialogue admin or Noodle point of contact. Additional views and reporting options may be available depending on your institution's setup.