How do we make sure customers actually know about a new feature, not just that we published a release note?

Start from the change, not the account list. The accounts that use the feature are found in your CRM, and the change reaches them where they already are: the lesson rewritten in the academy, a message to their admins, and the lesson inside your product. You approve before anything goes out, then see who learned it, account by account.

How do you know which customers a change affects?

The release says what moved, so the audience is derived from the change. Your LLM reads the release and, through your CRM, finds the accounts that use that part of the product. In Salesforce, Contacts become Juno learners through a rule on fields already on the account, and a dry run shows who would be created first.

How do you update a customer course when the product changes, without re-uploading it?

Juno rewrites the part of the lesson that moved and keeps the rest, in place. The course keeps its address, so every link to it, from your help centre or from your product, still opens it. Nothing is deleted and uploaded again, and the rewrite waits for your approval before it publishes.

How do you measure whether a release landed with customers?

Per account, per release. Of the accounts a change affects, you see which learned it, with the activity written to the Contact and its Account in Salesforce, where the Most Trained Accounts report ranks them. Adoption of the feature, support tickets and renewal are then read against the accounts that learned it, as direction, never as a promise.

Can the training appear inside our product when a feature changes?

Yes. The lesson can sit inside your product, at the screen that changed, alongside whatever you already run there. It is the same lesson the academy holds, so the change is written once and reads the same in both places, and a customer who never opens the academy still meets it where the work happens.

How do you avoid spamming customers with every small change?

Not every change earns a message. Your LLM reads the release and proposes which changes matter to whom, and the small ones stay in the academy. Only the accounts that use the part that changed are told, and nothing reaches them until you approve the audience and the words. You see the list before anyone else does.

How do we train customers and our own team on the same release?

The same release runs for all three audiences, and only the last mile changes. Customers get the lesson in the academy, in the product and in a message, measured on the accounts that learned it. Your teams get a brief per team before launch, partners a certification refresh. See Release & Product Update and Certify Your Partners.

Your customers learn what you shipped, the week you ship it.

The lesson is rewritten in place, so every help-centre link still works. The accounts that use the feature are found in your CRM and told where they already are: the academy, their inbox, the product. You see, account by account, who learned it.

Book a demo

4.7 / 5G2

Customer & Partner Training

Northwind· Help · Reports

Northwind Academy

Release 4.2Exporting reportsExporting reports3 min · Same linkOpen the lessonPick a report1 minThe new export screenRewritten · 1 minSchedule an export1 minQuick checkQuiz

The feature shipped a quarter ago. The tickets started last week.

The release note went to everyone, the academy still teaches the old screen, and the accounts that use the feature never heard about it.

How it works

1Trigger & Signal

JiraThe release
ConfluenceThe spec
SalesforceWho uses what

2Knowledge Design

Your LLM + Juno MCP

Rewrites the lesson in place
Finds the accounts that use the feature
Drafts the message

Human approval

3Delivery & Adoption

Customer admins
End users
Your CSMs

4Measure

Accounts that learned it, per release

One release, to the accounts it changes something for

Release 4.2 changes the export screen. Update the customer course and tell the accounts that use exports.

Three support colleagues at their laptops, one on a call

A laptop and a notebook on a wooden desk

See how a release becomes the lesson

The weeks after the release

Reach the accounts that use the thing that changed

IntegrationsConnect Juno to your company's tools

Customer provisioningEnabled

SourceSalesforce ContactsFeature in useExportsDry run38 accountsSign-inMagic link

Edit

SalesforceEnabled

Connected asNorthwindSyncsLearning activityReportMost Trained Accounts

Disconnect

Derived from the change
The release says what moved. The audience is the accounts that use it.
Resolved in your CRM
Salesforce Contacts become learners through a rule on fields already on the account.
A dry run first
You see who would be created before anyone is.
Sign-in by magic link
Customers open the academy from a link, with no password to set.

Three places they already are, and one promise we don't make

We do not claim to make a customer read anything. We claim to stop spending your reach on the accounts a change does not affect, and to show you, account by account, whether it landed.

Four colleagues learning together around a laptop

The academy
The lesson is rewritten in place. Every link to it still opens it.
Their inbox
A message to the admins of the accounts that use the feature.
The product
The lesson sits inside your product, at the screen that changed.

Count the accounts, one release at a time

Release 4.2 · Exports

Accounts that learned it

24 of 38

AccountToldLearnedStatus

Northstar · USDoneTold 3 adminsLearned 3 of 3

Northstar · EMEAIn progressTold 2 adminsLearned 1 of 2

Northstar · APACNot startedTold 4 adminsLearned 0 of 4

On each Account recordMost Trained Accounts

Try it

Build a Product Hub channel from our release notes
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
Claude, opens in a new tab ChatGPT, opens in a new tab
New to Juno? See it in a demo
The prompt
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.
Turn a release into a click-through lesson
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
Claude, opens in a new tab ChatGPT, opens in a new tab
New to Juno? See it in a demo
The prompt
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.
Compare adoption: trained vs. untrained account owners
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
Claude, opens in a new tab ChatGPT, opens in a new tab
New to Juno? See it in a demo
The prompt
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.

Every prompt

MeasureAccounts that learned it, per release

AudienceWhat they receiveMeasured on

CustomersThis pageWhat they receive The lesson in the academy, in the product, and a message to the accounts it affectsMeasured on Adoption of the shipped feature · ticket deflection · renewal

EmployeesWhat they receive A release brief per teamMeasured on Teams certified before release day

PartnersWhat they receive Partner academy and certification refresh, no lesson in the productMeasured on Certified partner capacity · partner-sourced pipeline

Questions people ask.

How do we make sure customers actually know about a new feature, not just that we published a release note?: Start from the change, not the account list. The accounts that use the feature are found in your CRM, and the change reaches them where they already are: the lesson rewritten in the academy, a message to their admins, and the lesson inside your product. You approve before anything goes out, then see who learned it, account by account.
How do you know which customers a change affects?: The release says what moved, so the audience is derived from the change. Your LLM reads the release and, through your CRM, finds the accounts that use that part of the product. In Salesforce, Contacts become Juno learners through a rule on fields already on the account, and a dry run shows who would be created first.
How do you update a customer course when the product changes, without re-uploading it?: Juno rewrites the part of the lesson that moved and keeps the rest, in place. The course keeps its address, so every link to it, from your help centre or from your product, still opens it. Nothing is deleted and uploaded again, and the rewrite waits for your approval before it publishes.
How do you measure whether a release landed with customers?: Per account, per release. Of the accounts a change affects, you see which learned it, with the activity written to the Contact and its Account in Salesforce, where the Most Trained Accounts report ranks them. Adoption of the feature, support tickets and renewal are then read against the accounts that learned it, as direction, never as a promise.
Can the training appear inside our product when a feature changes?: Yes. The lesson can sit inside your product, at the screen that changed, alongside whatever you already run there. It is the same lesson the academy holds, so the change is written once and reads the same in both places, and a customer who never opens the academy still meets it where the work happens.
How do you avoid spamming customers with every small change?: Not every change earns a message. Your LLM reads the release and proposes which changes matter to whom, and the small ones stay in the academy. Only the accounts that use the part that changed are told, and nothing reaches them until you approve the audience and the words. You see the list before anyone else does.
How do we train customers and our own team on the same release?: The same release runs for all three audiences, and only the last mile changes. Customers get the lesson in the academy, in the product and in a message, measured on the accounts that learned it. Your teams get a brief per team before launch, partners a certification refresh. See Release & Product Update and Certify Your Partners.
How is customer training priced?: Pricing is published on the Pricing page.

Your customers learn what you shipped, the week you ship it.

The feature shipped a quarter ago. The tickets started last week.

One release, to the accounts it changes something for

The weeks after the release

Reach the accounts that use the thing that changed

Derived from the change

Resolved in your CRM

A dry run first

Sign-in by magic link

Three places they already are, and one promise we don't make

The academy

Their inbox

The product

Count the accounts, one release at a time

Per account, per release

On the CRM record

Checked, not assumed

Then the revenue line

Try it

Build a Product Hub channel from our release notes

Turn a release into a click-through lesson

Compare adoption: trained vs. untrained account owners