Simulations, branching scenarios, click-throughs and games, coded by your AI assistant from what you describe. Play it with tracking live, point at what to change, and save it to Juno as a lesson that reports score and completion.
Pricing objections: practice round
SCORM 1.2 · connected · 9 values tracked
Dana · Head of Operations
How do I know it will work for us?
Good. A shared measure turns the pilot into her decision.
Round complete. You scored 100. Passing is 70.
Example data
Trusted by teams at
A simulation or a branching scenario means a seat in an authoring tool, a day of building, and a package to rebuild every time a screen changes.
Describe
Tell Claude or ChatGPT what it's about, who it's for and what people should be able to do afterwards. It asks what it needs, then codes the lesson from scratch: a conversation with a customer that branches on every answer, a practice run of your new screens, a game that drills the rules.
claude.ai/newJuno connectedWhat should we build today?
Build a branching practice round for our sales team: a customer pushes back on price, the rep picks a reply, and the talk branches from there.
Build a branching practice round for our sales team: a customer pushes back on price, the rep picks a reply, and the talk branches from there.
I'll draft it and open a preview. Nothing is saved to Juno until you say so.
What should passing look like?
JunoRead the training on this featureJunoDrafted the scenario, 3 decision pointsJunoOpened the preview, tracking onDraft ready, nothing saved
JunoReply to Claude…Play it
The lesson opens in a full preview with Juno's SCORM player behind it. As you click through, a side panel shows every value the lesson reports: each answer, the score, and pass or fail against your passing score. One click shows it on a phone.
Pricing objections: practice round
SCORM 1.2 · connected · 2 values tracked
Dana · Head of Operations
You cost more than the tool we use today.
Example data
Review
Click any element in the preview and leave a comment right where it sits. Send your comments to the AI in one go: it changes only the lines that need it, not the whole lesson, and shows you the new preview.
Pricing objections: practice round
SCORM 1.2 · connected · 9 values tracked
Click an element to comment · Esc to exit
Dana · Head of Operations
My team won't switch tools in the middle of the quarter.
Example data
Save it
One click saves it to Juno as a SCORM lesson: no zip, no upload, no authoring tool. Saving puts it live in your catalog, so it saves only when you say so. It reports completion, pass or fail, the score and every answer, question by question, and you assign it, add it to a journey or pin it to a channel like anything else in Juno.
Pricing objections: practice round
SCORM 1.2 · connected · 9 values tracked
Pricing objections: practice round
SCORM 1.2 · Live in the catalog
Omar Haddad · interactions
Example data
Versions
Edit a saved lesson and Juno adds a new version. People halfway through keep the one they started, and any earlier version comes back in one click. Lessons you imported from Rise or Storyline can be edited the same way.
Example data
Each prompt opens your AI with the ask written for you. Nothing goes live in Juno until you approve.
A customer asks a question, your rep picks a reply, and the conversation branches from there.
Your AI asks you
The feature, who talks about it, real customer questions, any call notes you have
I want a branching practice scenario in Juno Journey where people rehearse talking about a new feature with a customer and see where each answer leads. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. The feature and the problem it solves 2. Who talks about it (sales, CS, support) 3. The questions and objections customers really raise 4. Call notes or transcripts we can use as examples, if any Ask these in one message, then wait for my answers. For sources outside Juno, check they’re connected in this chat; if not, I’ll paste excerpts. Never present invented quotes as real. Search Juno first for training on this feature so the scenario matches it. Then outline a customer persona, 3-4 decision points, strong and weak answers with feedback, and a score. After I approve, build it as an interactive HTML lesson with SCORM tracking and preview it. Saving it to Juno puts it live in our catalog, so save only when I say so; don’t assign it.
Your new screens rebuilt from your screenshots, with hotspots, a quick check and SCORM tracking.
Your AI asks you
Where the release note lives, screenshots of the new screens, who it's for, the pass mark
I want to turn a product release into a click-through lesson in Juno Journey: people practice the new flow, answer a quick check, and the score reports back to Juno. Use the Juno Journey connector for anything in Juno. If it isn’t connected, stop and tell me how to add it (https://docs.junojourney.com/mcp/overview). Before you build anything, ask me: 1. Where the release note lives (or I’ll paste it) 2. Screenshots of the new screens (I’ll attach them) 3. Who the lesson is for 4. The pass mark Ask these in one message, then wait for my answers. If the release note lives in another tool, check it’s connected in this chat; if not, I’ll paste it. Rebuild each screen in HTML to match my screenshots; never invent UI. Search Juno first for training on this feature, and update it if it exists. Then outline 4-6 steps that mirror the real clicks, with hotspots and short coaching, plus a knowledge check. After I approve, build it as an interactive HTML lesson with SCORM tracking and preview it. Saving it to Juno puts it live in our catalog, so save only when I say so; don’t assign it.
