Releases, pricing, positioning, policies: caught where they are born, delivered to the people they affect, proven on the number your CEO asks about.
4.7 / 5on G2
Attendance and completion are what most systems can measure, so they are what gets reported. The question underneath is a different one: is the customer-facing population current on the changes of this quarter, and where is it drifting? Juno is built to answer the second one.
“Don't tell me who completed training. Tell me what changed.”
Changes in this quarter
This quarterExample data
The share of your customer-facing people current on the changes of the last period, by team and role.
Median time from a change being caught to the affected teams confirming they are ready.
The share of changes closed with a knowledge check or an agent validation.
The share of teams whose lead signed off readiness on the changes that needed it.
Tickets, quotes and calls move alongside this. We show the direction and never claim the cause.
The view is built from the changes, teams and roles you choose.
Teams running Juno today
Keep sales, CS and support current on what changed: releases, prices, pitches, processes and the tools they work in.
1Trigger & Signal
2Knowledge Design
Your LLM + Juno MCP
3Delivery & Adoption
4Measure
Learned it · talked about it · used itThe conversation
Release 4.2 is in Jira. Get Sales and CS current on it by Friday, and give reps a way to practise the pitch.
Example data
Training deliverables
12:34CoursePositioning for the New ReleaseReal customer calls
This week2:14Uses new positioningDiscovery1:46Handles objectionObjection handling3:21Mentions new use caseUse cases2:08Missed pricing messagePricingBehavioral impact
Last 30 daysExample data
Change detection
The announcement is the moment everyone plans for, and it is already late. By the time it is written, the change has been live in a ticket, a pull request or a wiki page for a week. The loop starts in those systems instead, on the day the change lands.
JunoBILL-2841 closed: usage-based pricing goes live. Draft the heads-up and assign it to the affected teams.
Drafted the heads-up, a 3 min read. Here's the assignment, ready when you are.
I'll assign "Usage-based pricing goes live" to 412 people.
These 412 people will be enrolled and see it in their feed.
Example data
A release lands in your tracker, and the work to make people ready starts from that ticket.
A price change, a new pitch, a process edit in the wiki. No ship date, same consequence.
Salesforce, Datadog, NVIDIA and Claude ship on their own schedule, into your teams' week.
Your LLM reads the change and drives Juno, from the assistant your teams already use.
Jira, GitHub, Confluence, Notion and Google Drive are reachable over MCP, scoped to your permissions.
Anything that runs an MCP server is reachable the same way.
Every write action shows an approval card, and drafts stay invisible until you publish.
Targeted reach
Search assumes the person knows there is something to look for. Most do not: they were not in the room when it changed, and they carry on executing the version they learned. The change has to arrive at the people it affects, with their name on it.
If a person in Account Executive,Customer Successor Supportin EMEA, assign this training.
Heads-up · 3 minIf a person completesthe heads-up, auto assign them to Knowledge check, 3 questions.
Example data
Target by role, position, department, location, employee type or group, written once as a rule.
A heads-up, a short piece, a full module or a live session, depending on how big it is.
Channels post into Slack and Teams, one way, and the record stays in Juno.
A knowledge check or an agent validation closes the change.
Knowledge Hub search covers published content by topic, keyword or skill, for whoever does come looking.
The rule fires on the next change, and the one after that, without being rebuilt.
Update once
The library ages faster than anybody can maintain it, and the field works that out before you do. Once a rep opens two things that contradict each other, they stop opening either. Content in Juno is edited in place, so the version everyone has is the one you just changed.
Section 2 · Usage-based tiers
Usage-based pricing goes live Thursday.
JadenUpdate Section 2 for usage-based tiers
One section changed. The 412 people already assigned get this version when you publish.
Sections changed
Example data
Change the content itself. No delete, no re-upload, no second version to reconcile.
Everybody who has it gets the corrected version without being assigned it again.
Translation at scale, so the correction lands the same way in each one.
Authoring sits in the same place as delivery, so a fix does not need a second tool.
Three moments, each judged on its own number, each with its own page.
Each card opens Claude with the prompt ready. It asks before it builds, and nothing goes live without your OK.
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.
Pitch, product and competitive material in one place reps actually open.
Your AI asks you
Whether you have playbooks or recorded calls, which roles, the skills and deals to win
I want a sales enablement channel in Juno Journey where reps find pitch, product and competitive material in one place. 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 we have playbooks or recorded calls, and which tools hold them 2. Which sales roles and segments this is for 3. The skills or deal types we most need to win Ask these in one message, then wait for my answers. Check each tool I name is connected in this chat; if not, I’ll connect it or upload exports. Never guess what’s in a playbook or a call. Look in Juno first for existing sales courses, quizzes and channels, and reuse them. Then propose topics (e.g. by deal stage), file existing content in, and suggest 3 new pieces for the biggest gaps (one from a strong call, if we record calls). Build it as a new private channel with drafts and preview it. Adding content to a channel with members notifies them, so ask before touching an existing one. Don’t publish, assign or notify reps until I approve.
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.
Learned, talked about it, used it, impact: one dashboard from your Juno data and the tools you connect.
Your AI asks you
The launch and team, whether and where you record calls and track usage, the outcome
I want a learning → impact funnel for one of our launches. 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 launch, its date range and the team that learned it 2. Whether and where we record or take notes on customer calls 3. Whether and where we track product usage, and which event means “used it” 4. The outcome to end on, where it lives, and how accounts map to people 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 an export. Never invent data. Start in Juno: this launch’s training and who completed it. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Confirm definitions with me, then build an interactive artifact: the funnel (learned → talked about it → used it → outcome) in total and per person, the biggest drop-off, and suggested next steps. Show sample sizes and gaps. Don’t claim causation; don’t assign or message anyone.
Two customers, in their own words.
“The journeys with automations really helped me make sure my support agents were being kept up to date on our product on a daily basis.”
“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.”
“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.”
From the Hunters case study
“Designed role-based, highly scalable, and ROI-positive onboarding certification programs in Juno for sales, partners and customers.”
The same reach, for the people who don't work for you.
