Describe a soft-skill situation and get back a realistic roleplay script, complete with characters, a turn-by-turn exchange, a branch point, and coaching notes, ready to paste into your authoring tool.
Write a [difficult customer] roleplay script for [de-escalation] training with a branch point and coaching notes.
An illustrative example. Your output will reflect your own sources, data, and prompts.
I wrote this from the escalation steps in your Service Standards, Section 3, and the tone in your brand voice guide. It runs one setup, a short escalating exchange, one decision point with three options, and coaching notes at the end.
Setup. Priya ordered a replacement part after her first one arrived cracked. The replacement has now arrived damaged too, the second time this month. She calls support already frustrated, and the learner, playing the rep, picks up the call.
Characters. Priya, a customer of two years who has taken time off work to be home for both deliveries; the rep, who can authorize a replacement or a goodwill credit but needs a supervisor to approve both at once.
The exchange escalates over a few turns before the rep has to decide how to respond.
Priya: This is the second broken one this month. I took the afternoon off to be here for it, again, and it's cracked right down the side.
Rep: Thanks for calling in about it. Can I get the order number so I can pull it up?
Priya: I gave it to the last person. Why do I have to keep repeating myself? Nobody there talks to each other.
Rep: I do have the previous case here, I can see the first replacement went out on the fourth.
Priya: So you can see it's happened twice and I still have nothing that works. I'm done being patient about this.
Decision point — how does the rep respond?
Coaching notes. The turn that decides this call is acknowledgement before solution. Name the problem and own it out loud ("Twice in a month is not okay, and I'm sorry you took the time off for this") before moving to the fix. Watch tone: warm, unhurried, and specific beats fast and scripted. Good looks like option A, a genuine acknowledgement, one concrete next step inside the rep's authority, and an honest expectation for anything that needs approval. If the learner picks B or C, replay this decision point and let them try the acknowledgement first.
Want me to add a second branch point after the resolution, or write an easy and a hard variant of the same scenario?
Scenario Scripting turns a situation you describe into a complete roleplay script: the setup, the characters, a turn-by-turn exchange that escalates, one decision point where the learner chooses how to respond, the likely consequence of each choice, and coaching notes on what good looks like. You review and refine it in chat, then paste it into whatever tool you build in.
Upload your service standards, tone guide, and a few real ticket examples to the Knowledge Center so the dialogue and coaching sound like your team.
Tell Joy the soft skill, the setup, and the kind of person on the other side. Joy drafts the characters, the escalating exchange, and a decision point.
Read it in chat. Ask Joy to sharpen a line, add a branch, soften the customer, or expand the coaching notes until the script does the teaching job you need.
Copy the finished script into Storyline, Rise, or your LMS and wire up the interaction. The writing is done; you're placing it.
Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.
A turn-by-turn exchange that builds tension the way a real call does, not stiff scripted lines learners see through.
One clear decision where the learner chooses how to respond, with the likely consequence of each option spelled out.
Joy drafts notes on tone, acknowledgement, and what good looks like, so learners understand why a reply works.
The dialogue and coaching reflect your service standards and real tickets, in your organization's voice.
Write the angry-caller or repeat-complaint scripts where tone and acknowledgement decide how the call ends.
Draft a discovery call or objection moment where the rep can choose to push or to listen.
Script a performance or conduct conversation with a branch for how the manager opens it.
Write a sensitive intake or bad-news moment where empathy and pacing change the outcome.
Joy drafts the roleplay script as text in chat: the setup, the characters, a turn-by-turn exchange, a decision point with the likely consequence of each option, and coaching notes. You review and refine it in the conversation, then copy it into your authoring tool. Joy writes the script; it does not build the interactive module or record any voices.
Yes, when you connect the material. Joy works from the service standards, tone guide, and real ticket examples in your Knowledge Center, so the customer's language and the coaching reflect how your team actually handles the situation rather than a generic template.
Yes. The default script has one decision point, but you can ask Joy to add a second branch after the resolution, deepen an existing branch, or map several choices. It rewrites the script so every option still leads somewhere and the coaching stays consistent.
Yes. Ask for an easy and a hard variant of the same scenario and Joy adjusts how quickly the customer escalates, how forgiving the branches are, and how much the coaching spells out, so you can stage practice from first attempt to confident.
No. Joy drafts the script as text you can review and refine in chat. You copy it into Storyline, Rise, your LMS, or whatever tool you build in, then wire up the interaction and any audio. Joy handles the writing; you handle the build.
Join the waitlist and be first to try this workflow when JoySuite launches.