Customer onboarding
Guide customers from day one
Self-paced onboarding flows, account-setup education, hybrid journeys with live sessions, progress tracking and reminders, so a new account is using the product before the first check-in.
An academy that updates from the release, in-app lessons where the question arises, and certifications that expire when the product moves.
CalendarNorthwind Academy
Get your team running Northwind
Search your Northwind AcademySearch
Channels
Getting started

What shipped in 4.2
Updated for 4.2
Admin certification

Solution design
The academy is current until the next release, and the accounts that matter most are the ones who never open it.
Customer onboarding
Self-paced onboarding flows, account-setup education, hybrid journeys with live sessions, progress tracking and reminders, so a new account is using the product before the first check-in.

Customer onboarding
Northstar · new account, started 3 March
33%complete
Steps: 1 of 3Due: Mar 10, 2026
Academy
Your domain, your brand, one academy per audience or per customer, with role-based training and demos behind it, and the content updating when the product does.
Start hereGet your team running NorthwindUpdated for 4.2Getting started
by Northwind

Set up SSO in four minutes
by Northwind
Updated for 4.2
What shipped in 4.2
by Northwind
Updated for 4.2
See the LMSSee the AI Authoring Tool
In-app
Your customers ask your product before they ask your academy, and a good number of them will never type its address. Juno puts a short piece of that academy inside your product, at the point where the question comes up, branded as yours and rendered without touching your interface.
The lesson appears where the question is asked, not on a second website.
It reads as part of your product because it is your academy's own material.
Nothing is drawn on top of your screens and nothing is injected into them.
The academy version and this one are the same material, kept in one place.
When a release rewrites the academy version, this one changes with it.
Partners do not get this surface. It is the one place the two audiences genuinely differ.
Certifications
You can issue a certificate today. The part that gets planned last is the release that makes it wrong. A credential is not a completion. It is a claim your customer makes to their own market, and it should stop being true on a date you can see.
The same material, rendered on the page where the question is being asked.
Published beside the thread, instead of behind a second login.
Built to the formats a customer's own system already accepts.
You maintain the material once and the surfaces read from it.
What leaves the academy is what you decided could leave it.
Monetization & events
Neither of these is the reason you would switch, and both of them come up in the first call.
Yes. Payment runs through Stripe, so it arrives in the account your finance team already reconciles and there is no second billing system beside the academy. What you can put behind a payment is the part worth a call, and we would rather answer it with your catalogue open than in a paragraph.
Yes. Customer webinars, office hours and onboarding cohorts run on the same engine as the rest of the academy: rooms, instructors, calendar invitations, and the session landing on the customer's record like everything else. Guests can join without an account, which is what makes a public launch webinar possible without provisioning every attendee.
Accounts & CRM
Customers sign in with a link, accounts and contacts come from your CRM, and every training activity lands on the account record your CS team already reads.
Did the accounts whose owners took the Workflow Builder training adopt it more?
learning_activities_queryTrained owners: 58 % of accounts using it; untrained: 31 %. Correlation, not proof of cause.
Draft ready · waiting for your OK
A branded public homepage with your real courses, previewed before it goes live.
Your AI asks you
Your website, who it's for, programs to feature first, what must stay private
I want to design the homepage of our customer academy in Juno Journey: the public page customers land on to learn our product. 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. Our website, so you can match our colors, fonts and logo 2. Who the academy is for (new customers, admins, end users) 3. Which programs or certifications to feature first 4. Anything that must stay private Ask these in one message, then wait for my answers. If you can’t open our site, I’ll paste colors and logo; don’t guess. Check our Juno first: today’s public academy pages, navigation, and which published courses are ready to feature. If you have no public academy tools here, say so; don’t edit our internal academy instead. Then draft the homepage: hero, a link into the course catalog, a “Start here” row, featured programs from our real courses, and navigation. A new public page goes live when saved, so preview it and save only when I say so. Don’t change the live site until I explicitly approve.
Your 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.
Claude groups the questions customers really ask and drafts a lesson that answers them.
Your AI asks you
Whether and where you record or note calls, which window and call types, who it's for
I want to turn what customers actually ask on calls into training, so our people can answer before it comes up again. 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. Whether and where we record or note calls (a call recorder, meeting notes, a CRM), or I’ll upload transcripts 2. Which time window and which kinds of calls 3. Who the training is for 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 transcripts. Only use questions you actually find, and count how many calls each came from. Group the questions into themes ranked by frequency, then search Juno for content that already answers each one. Propose which themes need an update to an existing course, a new short lesson or FAQ, or a quick drill. Show me that plan first and build only what I approve, as drafts, with customer names removed. Don’t publish or assign until I say so.
Usage side by side for accounts whose owners took the training and those who didn't, labeled as correlation.
Your AI asks you
The feature, whether and where you track usage and account owners, the "used it" event
I want to compare feature adoption for accounts whose owners took the training vs. those whose owners didn’t. 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, the training that covers it, the date range 2. Whether and where we track product usage, and which event means “used it” 3. Where account owners are recorded (if anywhere) and how they match Juno users 4. Accounts or segments to exclude Ask these in one message, then wait for my answers. Check each non-Juno source is connected in this chat; if not, I’ll connect it or upload a CSV. Never estimate missing numbers. Pull completions from Juno first and show how you matched people. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Then build an interactive artifact: adoption for trained vs. untrained owners, counts per group and the account list. State definitions, show sample sizes and gaps, and say plainly it’s correlation, not causation. Change nothing anywhere.
A cybersecurity company that runs its customer certification programme in Juno, and what it says that programme did.
“Influenced 85%+ of direct customer ARR with Hunters Academy (our customer & partner certification program in Juno). It is becoming a company differentiator used to help close new business, supporting fast time to value for our customers.”
Customer Onboarding: Saved $60,600 (105 live customer success training hours) in 1-year with a technical customer onboarding certification in Juno.
Meagan D.Director of Sales Enablement, HuntersFour places a customer has to be ready, each with its own trigger and its own way of proving it worked. How journeys work