This release is in GitHub. Brief CS, our customers, and our partners by Friday.
Journey created

Billing release · CS readiness
journey
Steps in order, a certificate on completion
A journey also runs the process around the learning path.
Not sure where to start? See your readiness gap in 5 minutes.
A release, a policy, a new hire, or a renewal: the journey is what Juno runs each time, from the change to the proof that people are ready.
The journey starts automatically, manually, or from your own tools.
If a person matches all the criteria: Department Customer Success, then auto-assign this training.
If a person matches all the criteria: Partner tier Gold, then auto-assign this training.
Who, what, format, and language, decided from the context Juno keeps up to date.
Human approval
Enrollment, reminders, escalations, and reassignment run without anyone chasing them.
Learning that fits them, delivered
Measure the impact, and the next change starts the journey again
This release is in GitHub. Brief CS, our customers, and our partners by Friday.
Journey created

Billing release · CS readiness
journey
Steps in order, a certificate on completion
A journey holds courses, quizzes, videos, articles, and SCORM.

Billing release · CS readiness
What changes on the invoice, and how to explain it
Completing this journey earns Billing release certified
60%complete
Lock the sequence where it matters, or leave it open.
Workshops are part of the journey itself, not on a separate calendar.
Open answers, uploads, and recordings are reviewed before the learner moves on.
Issued when someone finishes, with its expiration date.
What a person is given, and the day it is due.
Where content is organized for the people it serves.
Approve a build, sign off before anything is sent, or rule on an exception. The approver changes with the journey: a manager, a CSM, or a compliance officer. You set the level of autonomy.
JunoAssign the Billing release journey to Customer Success, due Oct 9.
I'll assign “Billing release · CS readiness” to 20 people.
These 20 people will be enrolled and see it in their feed.
CancelAssign to 20 peopleYour releases become short lessons and videos, filed by product area.
Your AI asks you
Where your release notes live, who it's for, your product areas, how far back
I want a Product Hub channel in Juno Journey: one place where people learn what we ship, easy to refresh from our release notes whenever I ask. 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 release notes live (a tool, a docs site, or I paste them) 2. Who the channel is for (customers, our own staff, both) 3. Our product areas, to use as topics 4. How far back to go 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/upload the notes. Never invent a release. Search Juno first for lessons on these features and any existing product channel, and reuse what fits. Then propose the channel: a topic per product area, existing content filed in, and a draft lesson for each gap. Build it as a new private channel and preview it. Adding content to a channel with members notifies them, so ask before touching an existing one. Don’t publish or notify anyone until I approve.
Your new screens, rebuilt from screenshots and tracked as SCORM.
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.
Three phases for one role, a checkpoint quiz per phase, your courses reused.
Your AI asks you
The role, what "ramped" looks like at 30/60/90, any existing material, who signs off
I want a 30-60-90 day onboarding journey in Juno Journey for one role, so new hires ramp on a clear path instead of a pile of links. 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 role and the team 2. What “ramped” looks like at day 30, 60 and 90 3. What material we have outside Juno, if any, and where 4. Who signs off at each milestone Ask these in one message, then wait for my answers. For material outside Juno, check that source is connected in this chat; if not, I’ll connect it or upload files. Don’t invent our processes. Search Juno first and reuse existing courses and quizzes wherever they fit. Then propose the journey: three phases, the courses in each, a checkpoint quiz per phase, and the gaps you’d fill with short new courses. After I approve the outline, build the new pieces and the journey as drafts. Don’t publish, assign or notify anyone until I say so.
A short course, a 5-question check, and an acknowledgment, with who's done.
Your AI asks you
The policy document, who must complete it, the deadline, acknowledgment or quiz
I want to roll out a new policy in Juno Journey with proof that everyone who needs to has read and understood it. 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 policy document (upload it, or tell me where it lives) 2. Who must complete it (departments, locations, roles) 3. The deadline 4. Acknowledgment, a quiz, or both Ask these in one message, then wait for my answers. If the document lives in a tool outside Juno, check it’s connected in this chat; if not, I’ll upload it. Stick to what the policy says; don’t add rules. Search Juno for older versions of this policy training and update rather than duplicate. Then plan a short course (what changed, what it means for you, examples), a 5-question check with a pass mark, and an acknowledgment step. Show me that outline, the audience and the due date first, then build as drafts. Don’t publish, assign or notify anyone until I explicitly approve.
“Speaking from my experience, Juno is the perfect combination of functionality and flexibility. Juno is really intuitive to use, and allows me to quickly build courses, create high-quality journeys, and maintain them all easily in one place.”
Meagan D.Director of Sales Enablement, Hunters“We had to onboard 100 new hires remotely and connect them directly with their teams' objectives and workflows. Using Juno's onboarding path, we decreased the time and manpower involved by 20% and were able to finalize the process within a month.”
Hili B.HR & OD Expert, KalturaA course is content someone completes. A journey is the whole run: the content in order, the live sessions, the checkpoints, the people it applies to, and what changed by the end. A course ends at completion. A journey ends by producing the trigger for its next run.
A learning path, as your LMS probably calls it, is the sequencing part of that. It orders content and tracks progress. Nothing comes before it and nothing after it: no trigger, no audience rule, no automated delivery, and no measure of what changed.
Three related concepts, kept separate on purpose. A group is a segment of people. A channel is a space that holds content. A journey is an ordered run of learning that tracks completion. One scheduled run of a journey, for one set of people, is a cohort.
A journey does not end at completion. Its last phase measures what changed in the work: a step where someone does the thing, a manager's confirmation, or the same question asked before and after.
That measurement is the Behavioral Change Signal. It is composed, not fixed: you choose which signals count for this journey and at what level (per release, team, population, or account), and the view is built from them. It is not a single number, and nothing is graded.
In-platform and human-in-the-loop signals are available today. Business signals, such as what your CRM, product analytics, or support queue show, are where the same measurement is heading next.
learnedtalked about itused itthe outcome you pickcorrelation, never causation
Measurement plan · draft

Billing release · CS readiness
Journey
Customer Success explains the new invoice without escalating it
What we'll measure
confirmed by the manager at each checkpoint
by role, geography, and risk profile
flagged per person before they lapse
who did what and when, exportable per policy
scenarios and pitches, checked, not just clicked
the same question, asked twice
Every journey names the audience it was built for and also runs for the other two: the same phases, a different last mile, and its own signals for each audience.