La narration de la vidéo, en anglais.
Scenario 5: Score the learner’s answer
Hi and welcome back! From here on, the videos get a bit more advanced, but they show how far you can take personalized interactions for your learners. In this video, our Q&A learns to grade: it will give a score and a verdict, check each answer against the store's real returns policy, and when the learner misses the mark, Storyline will step in with a reminder. Here's our Q&A again. The learner answers… and the card flips with a score and a verdict. And when the answer breaks the store's policy, a reminder pops up in the course. Let's build it.
A score and a verdict
Let's start with our Q&A, "Customer apology". Until now, it ran on "Feedback only": the AI sends back a few sentences of feedback, and that's it. The learner reads them, but for Storyline it's just text. "Score and verdict" changes that. Instead of free text, the AI fills in a short form: the feedback, plus a score and whether the learner passed. Each line of that form is a return variable. The widget shows them on the card, and Storyline receives each one in its own variable, like the one ending in "score", ready to use in your triggers. Let's set it up. In "What comes back", switch from "Feedback only" to "Score and verdict". The feedback field is already there. Click "Add return variable": we name it score, pick "Number" in the type menu, and describe it as "Score from 0 to 10". One more: passed, we pick "Boolean" and describe it as "True if the score is 7 or more". In the instructions, we add one sentence: "Also give a score out of 10, and set passed to true when the score is 7 or more." Under "Look", "More styling", we leave "Score display" on "Fraction", pick score for "Score", type 10 in "Score out of", and pick passed for "Pass / fail". In "Try it"… the card flips: feedback, a verdict and a score. Let's save. We'll come back to that verdict in Storyline in a moment.
The store’s policy
Next, the store's returns policy. For this, we'll use a feature we haven't seen yet: reference documents. You give the AI a policy, a procedure or a slide deck, and it uses that text when it answers. On the course page, under "Reference documents", click "Add a document" and choose the file: here, our one-page PDF. It's read right in your browser: SlideMind keeps only the text, never the file. Under "What the AI will read", we check that the text came through, then click "Add document". Because we added it to the course, every slide of the course reads it, unless a slide turns it off. A short document like this one is read in full with each answer; with longer ones, the AI reads only the passages that match the question. One thing to keep in mind: learners can get anything in these documents by asking the AI, so leave out anything confidential. Back in "Customer apology", the "Course context" sheet now lists the policy under "From the course", and "Use in this slide" is on. We add one more sentence to the instructions: "Check the learner's promises against the store's returns policy, and fail any answer that breaks it." Then, back in "What comes back", one more return variable, so Storyline can tell the learner exactly what went wrong: we name it policy_check, pick "Text", and describe it as "If the answer breaks the returns policy: what the learner promised or asked, then the rule it breaks, quoted from the policy. Empty otherwise." In "Try it", let's answer the way a rushed agent might: "Sorry, Maya. Please send the broken lamp back with a photo, and we'll ship a new one." "Not quite", 3 out of 10. The policy check doesn't show on the card: it goes to Storyline, with what the learner asks for and the rule it breaks. We'll see it in the course in a moment. Let's save.
The verdict in Storyline
Now, let's use that verdict in Storyline. Back on the slide, in the "Installation" step, we open "Storyline variables". We need two of them: the one ending in "verdict", which holds pass or fail, and the one ending in "policy_check". Storyline only keeps a value in a variable that already exists, so we copy each name, and in Storyline, we open the "Variables" window, click "Create a new variable", paste it and choose "Text". Twice. Next, a layer: in the "Layers" panel, we click "New Layer" and name it Policy reminder. On it, instead of a fixed message, a text box that shows the policy check: we type the variable ending in "policy_check" between percent signs. That way, the reminder repeats what this learner said and quotes the exact rule it breaks. Last, the trigger. Back on the base layer, we click "Create a new trigger". Action: "Show layer", Policy reminder. When: "Variable changes", and we pick our verdict variable. Under "Conditions", we add one: that same variable, "Equal to", fail. Pass, and the learner moves on; fail, and the reminder explains what went wrong.
Test in SCORM preview
Let's test. We publish the course for "SCORM preview" again, and launch it as Sam. Sam gives the rushed answer. The card flips: "Not quite", 3 out of 10, with feedback on what to do instead… and since the verdict is fail, the policy reminder fades in beside the card, with what Sam asks for and the exact rule it breaks. Your Q&A now grades answers, reads your documents, and tells Storyline whether the learner passed. In the next video, it's the chat's turn: Maya's face, a coach and three endings will follow the conversation. See you there!