Customers learn the week you ship.

The lesson updates in place, and the accounts using it hear about it.

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.

Send each release to the accounts it affects

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

Claude

See how a release becomes the lesson

The weeks after the release

  1. ThuOct 1

    4.2 shipsReleased
  2. ThuOct 1

    Lesson rewritten in place

    Same link
  3. FriOct 2

    38 accounts notified

    • In the academy
    • By email
  4. Week 2Oct 8

    Lesson shown inside the product

    At the export screen
  5. Week 4Oct 22

    Who learned the change, by account

    • Drumlin · US
    • Drumlin · EMEA
  6. Week 6Nov 5

    On the CRM record

    Accounts that learned the change

Reach the accounts that use what changed

  • Audience based on the change

    The release shows what changed, and 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

    See who would be added as a learner before anyone is created.

  • Sign-in by magic link

    Customers open the academy from a link, with no password to set.

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

We don't claim to make customers read anything. We do claim to stop spending your outreach on accounts a change doesn't affect, and to show you, account by account, whether they learned it.

  • The academy

    The lesson is rewritten in place, so every existing link to it still works.

  • Their inbox

    A message to the admins of the accounts that use the feature.

  • The product

    The lesson appears inside your product, on the screen that changed.

Count the accounts, one release at a time

Release 4.2 · Exports

Accounts that learned the change

24 of 38
Drumlin · USDoneNotified 3 adminsLearned 3 of 3
Drumlin · EMEAIn progressNotified 2 adminsLearned 1 of 2
Drumlin · APACNot startedNotified 4 adminsLearned 0 of 4
On each Account recordMost Trained Accounts

Read next, as direction

Feature adoptionSupport ticketsRenewal
  • Per account, per release

    See how many of the accounts a change affects have learned it.

  • On the CRM record

    Learning activity is written to the Contact and its Account in Salesforce.

  • Checked, not assumed

    A short quiz after the lesson shows which accounts understood the change.

  • Then the business results

    Adoption, tickets, and renewal, compared against the accounts that learned it.

Try it

  • Build a Product Hub channel from our release notes

    Your releases become short lessons and videos, filed by product area.

    The prompt

    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.

  • Turn a release into a click-through lesson

    Your new screens, rebuilt from screenshots and tracked as SCORM.

    The prompt

    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.

  • Compare adoption: trained vs. untrained account owners

    Usage for trained and untrained account owners, side by side, as correlation.

    The prompt

    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.

All promptsNew to Juno? See it in a demo

MeasureAccounts that learned each release

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 for each teamMeasured on Teams certified before release day
PartnersWhat they receive Partner academy and certification refresh, with no lesson in the productMeasured on Certified partner capacity · partner-sourced pipeline

Frequently asked questions

How do we make sure customers know about a new feature?

Start from the change, not the account list. The accounts that use the feature are found in your CRM, and once you approve, they get the rewritten lesson where they already are.

How do you know which customers a change affects?

Your LLM reads the release and uses your CRM to find the accounts that use that part of the product. In Salesforce, a dry run first shows who would be added.

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

Juno rewrites only the part of the lesson that changed. The course keeps its URL, so every link to it still works, and the rewrite waits for your approval.

How do you measure whether a release landed with customers?

By account and by release: learning activity is written to each Contact and Account in Salesforce. Adoption, tickets, and renewal can then be compared against it, as an indicator, never a promise.

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

Yes. The lesson appears inside your product, on the screen that changed. It is the same lesson as in the academy, so customers who never open the academy still see it.

How do you avoid spamming customers with every small change?

Small changes stay in the academy, and only the accounts that use the part that changed are notified. Nothing reaches them until you approve the audience and the message.

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

One release reaches all three audiences. Customers get the lesson and a message, your teams a brief before launch, and partners a certification refresh. See Release & Product Update and Certify Your Partners.

How is customer training priced?

What each plan includes is on the pricing page. For a quote, talk to sales.