Courses, interactive lessons and video from a prompt or a document, built with your team, in your brand, in ten languages, and updated when the thing they teach changes.
4.7 out of 5G2
Refunds after settlement
PDFRefund policy 2026 revision.pdf
PowerPoint
Google Slides
YouTubeRefunds raised after settlement are reversed against the next settlement cycle.
Exceptions above €2,000 require a team-lead approval recorded against the case.
JadenBuild a course from Refund policy 2026 revision.pdf
Nothing saves until you keep or discard here.
Proposed sections
Trusted by teams at
A release, a policy, a process changes, and the course you published last quarter is quietly wrong. Generating it was the easy part.
Drop in a document or a topic; the editor proposes the structure, the sections and the knowledge checks, in a drag-and-drop canvas you see as the learner will.
Build a course from Release notes 4.2.pdf
Channel · What's newRelease 4.2From Release notes 4.2.pdfRelease 4.2
by Northstar
Course
Refund policy 2026
by Northstar
Course
Notification settings
by Northstar
Lesson
The same document becomes a course in the editor, an interactive SCORM lesson written from a description (Vibe SCORMing), or a narrated explainer video, with your approval before anything renders.
Turn Release notes 4.2.pdf into a course, a lesson and a video
Release 4.2
Release notes 4.2.pdf, the same source
25%complete
Steps: 1 of 4Due: Oct 16, 2026
What's new · Beta
Notification settings
Choose Email, Slack or in-app for each notification type, and know where learners still see reminders.
3 min4 steps1 checkPass 80%
games, simulations, branching scenarios from a prompt
storyboard, approve, render
Questions generated from the content, difficulty you set, feedback per question, and video assignments where a quiz is not enough.
Check what you know
by Northstar
Quiz
Intermediate · 4 questions
Co-authors, comments on any block, versions with revert, read-only previews for stakeholders, locked sections, and a status everyone can see.
On this paragraph
A refund raised after the batch has settled is reversed against the next settlement.
Marco Bellini · Payments lead
The exception threshold moved to €2,000 in June. This still reads as the old number.
Hannah Weiss · Training manager
Fixed in this draft. Taking it to publish once you have read it back.
Two verified reviews, in the words they were written in.
“Juno Journey makes it so much easier to build and manage upskilling programs for our teams. I love how quickly I can develop learning paths, it saves a lot of time and effort. The Course Builder (Jaden) is intuitive and helps me create content that’s relevant and engaging”
“Our support agents need to be kept up to date on a daily basis on all product changes and updates, Juno makes it really easy to create the content, automate its assignment and track the completion.”
Salome M.Customer Experience Training & AI Enablement Manager, Moon ActiveG2Colours, logo and fonts applied across every course; AI that writes in your brand tone; translations with version management across ten interface languages.
Remboursements après règlement
A refund raised after the batch has settled is reversed against the next settlement, not against the original charge.
Un remboursement émis après le règlement du lot est imputé sur le règlement suivant, et non sur le débit d'origine.
JadenTranslate Refund policy 2026 into French
Nothing saves until you keep or discard here.
Sections changed
It leaves the editor as a course, not as a file, and still exports wherever you need it.
A release note, a policy or a process arrives, in Juno or in ChatGPT, Claude and Copilot; the editor updates the one section it touches, keeps the version, and everyone already assigned sees the current course.
The pricing changed. Update our Pricing course to match the new page.
Plans and prices
Prices as listed on the previous pricing page.
Prices as listed on the new pricing page, one line per plan.
Where does a customer see the current price?
Sections changed
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.
Everything you shipped this month in one short course, plus an explainer video on the biggest change.
Your AI asks you
The date range, where your updates live, who it's for, your brand colors
I want this month’s “What’s new” digest in Juno Journey: one short course on what we shipped, plus a 60-second explainer video for the biggest change. 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 date range 2. Where our updates live (release notes, a changelog, or I paste them) 3. Who it’s for (customers, sellers, support, everyone) 4. Our brand colors Ask these in one message, then wait for my answers. Check that source is connected in this chat; if not, I’ll connect it or paste the updates. Never include a change I can’t trace to the source. Look in Juno first for courses that already cover these features, and update them instead of repeating. Then list the changes by product area and propose which one gets the video. Build the digest as a draft course with a short quiz. For the video, show me the storyboard and render only after I approve it, then add it to the draft course. Don’t publish, assign or notify anyone until I say so.
Storyboard first: scenes, narration, on-screen text. It renders only after you approve it.
Your AI asks you
The topic and takeaway, the audience, source material, brand colors, any screenshots
I want a 60-second explainer video in Juno Journey that teaches one idea clearly, even with the sound off. 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 topic and the one thing viewers should remember 2. The audience 3. Source material (upload it, tell me where it lives, or use a Juno course) 4. Our brand colors, and any real screenshots I want in it Ask these in one message, then wait for my answers. If the source lives outside Juno, check it’s connected in this chat; if not, I’ll upload it. Stick to the source: no made-up claims or numbers. Check Juno first for the course this video belongs in, or an existing video on the same topic. Then write a storyboard: scenes, narration, on-screen text, visuals. Show it to me and render nothing until I approve. After that, render it, add it to the course as a draft, and don’t publish until I say so.
Claude checks your courses against your source of truth and lists what to fix first.
Your AI asks you
Where your source of truth lives, which topics matter most, what counts as a recent change
I want to find training in Juno Journey that no longer matches how things actually work today. 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 our source of truth lives (product docs, release notes, policies) 2. Which topics or courses matter most 3. How recent a change must be to count Ask these in one message, then wait for my answers. Check that source is connected in this chat; if not, I’ll connect it or upload the documents. Only flag drift you can show evidence for. Read the relevant Juno courses, quizzes and journeys, compare each claim to the source, and give me a table: course, what it says, what the source says now, severity, suggested fix. This is a review, not an edit: change nothing yet. Offer to draft updated versions of the top items; after I approve, save them as drafts and don’t publish until I say so.
The editor earns its place inside a job somebody has to finish by a date. Each of these is a journey with its own trigger and its own way of proving it worked.
