Enrollment, reminders, and recertification run on rules you set once.
CalendarAI Academy
Learn it, try it, get certified.
Search the AI AcademySearch
Channels
Prompting that works
Build your first agent
AI Practitioner
Agents in your workflow
What shipped in October
Due in 2 days
Pricing by usageDue tomorrowSSO on every planDue in 3 days
New admin rolesDue in 6 daysTrusted by teams at
Chasing completions, re-running refreshers, rebuilding a report, fixing a course that quietly went stale: none of it is what you were hired for.
A course, a live session, and a survey a month later usually sit in three tools, with nothing connecting them. In Juno, they are one program.
Payments compliance 2026
Support
25%complete
Order the steps once, and every learner follows the same path.
Start from one template, then schedule a run with real learners in it.
Add a workshop or classroom day as a step in the path, with attendance included.
Ask what changed six weeks later, inside the same program.
See what each person did across every step, on a single row.
Slides, documents, and recordings live with the step they belong to.
New hires, role changes, the refresher that comes back every April: the right training keeps reaching the right people after you close the tab.
If a person's department is Support or Ops, auto assign them to Security refresher.
Role, position, department, location, group, or employee type.
Assign this training, assign the next one, assign a survey, send a nudge, notify, or reassign.
Trigger actions three days before a deadline, or a week after someone starts.
The refresher reassigns itself on schedule, with no calendar reminder needed.
Rules-based audiences that other features can use.
In the app, in email, in Slack, or as a text message.
A policy changes on a Tuesday, and the course teaching the old rule stays live for weeks. Your assistant reads what changed, rewrites the course, and reassigns it to the people it applies to, keeping the previous version. Nothing reaches anyone until you approve it.
1A change arrives
2Updates the course
Your LLM + Juno MCP
3Reassigned
4Measure
Then back to step 1Four changes affect your training. Here is what each one updates. Nothing goes out until you confirm.
GitHubA product shippedProduct training is updated
JiraA process changedThe relevant course is updatedGongSellers struggle with an objectionPractice createdEarlier versions kept
ChatGPT, Claude, GitHub Copilot, and Cursor, connected through the Juno MCP.
Jira, GitHub, Confluence, Notion, Google Drive, your own wiki, and any other tool with an MCP.
The assistant can read, write, and see only what your Juno role allows.
“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.”
“Setting up integrations like HRIS and SSO is straightforward, which saves a lot of manual work.”
300+ learning programs, reaching up to 5,500 employees per course
Raiffeisen Bank, running enterprise learning on Juno's LMS.
“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.”
In Juno, you build the course where people take it, so the two never drift apart, and a version history lets you roll back. The AI Authoring Tool writes the first draft, so you are already editing by the time you sit down.
Partial refunds
After settlement, open an adjustment. Never refund twice.
1:52A merchant asks for a partial refund after settlement. What do you do first?
JadenTurn the new refund policy into a short course, an interactive lesson for the support floor, and a two-minute explainer.
PDFRefund policy 2026Proposed sections
Turn a document into a course.
Describe a lesson and get an interactive, versioned SCORM lesson.
Storyboard, approve, render.
Much of your training still happens in a room, and it usually ends with a paper sign-in sheet that someone photographs and someone else types up. In Juno, the attendance list, the signatures, and the certificate all come from one record.
Refunds after settlement, BerlinDate & TimeThu, Sep 24 · 10:00LocationBerlin · Room 2.4Webinars, workshops, classroom sessions, recurring dates, and room availability.
The attendance list fills in automatically as people arrive and scan.
Each person signs next to their own name on the attendance sheet.
Self-registration with admin approval, and a waitlist once seats fill up.
Earned by attending, by passing, or added manually.
See who attended and who didn't, session by session.
See results by team and manager, before and after training.
Learning dashboard
Last 8 weeksExportA quick check on a launch's key facts, with a due date and a drafted nudge.
Your AI asks you
The topic or course, who takes it, the deadline, the pass mark and attempts
I want a quick 5-question drill in Juno Journey that locks in the key facts after a launch, with a due date so it actually gets done. 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 topic, or the course it should reinforce 2. Who should take it 3. The deadline 4. The pass mark and how many attempts Ask these in one message, then wait for my answers. Find that course or lesson in Juno first and base every question on it. If the material lives outside Juno, check it’s connected here; if not, I’ll paste it. No questions you can’t trace to the source. Show me the 5 questions with answers and one-line explanations. After I approve, build the quiz as a draft and prepare the assignment with the deadline as its due date. Tell me plainly what Juno reminds people about on its own; you can’t schedule repeats or reminders from this chat. Draft a nudge I can send later. Show me who would get the assignment and the nudge, but don’t assign or send anything until I explicitly say go.
One view per manager: who finished, who's overdue, and one suggested nudge.
Your AI asks you
Which managers or teams, which numbers matter, the period, anything from outside Juno
I want a learning digest for every manager: who on their team finished what, who’s overdue, and one thing to follow up on. 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. Which managers or departments to include 2. Which numbers matter (completions, overdue, scores, time spent) 3. The period it covers (e.g. the last 7 days) 4. Whether to add anything from outside Juno, and from where Ask these in one message, then wait for my answers. Check anything outside Juno is connected in this chat; if not, I’ll upload an export. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Never fill in numbers you can’t read. Build an interactive artifact: one view per manager with their team’s progress, overdue items and a suggested nudge. State definitions, data gaps and counts. Show me a sample for one manager first. Nothing runs on a schedule; tell me how to refresh it. Don’t send it to anyone or notify learners.
Teams down the side, topics across the top, gaps visible before the deadline.
Your AI asks you
Which groups and topics, which courses count, what "done" means, the date range
I want a completion heatmap: groups down the side, topics across the top, and each cell showing how far along that group is. 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. Which groups (departments, roles, locations) 2. Which topics, and which courses count for each 3. What “done” means (completed, passed, above a score) 4. The date range Ask these in one message, then wait for my answers. Pull everything you can from Juno; if you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. If a grouping lives outside Juno (e.g. an HR system, if we use one), check it’s connected in this chat; if not, I’ll upload a CSV. Never guess anyone’s group. Confirm definitions with me, then build an interactive artifact: the heatmap with counts per cell, a click-through to the people in each cell, and the three weakest spots with suggested next steps. State definitions, show sample sizes, and grey out cells too small to judge. Don’t assign or notify anyone.
A short list of what to update, merge or retire. Nothing changes until you say so.
Your AI asks you
Which audience matters most, what "stale" means for you, any source of truth to check
I want an honest audit of our academy in Juno Journey: what’s stale, what’s missing and what’s duplicated. 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. Which audience matters most (customers, partners, employees) 2. What “stale” means for us (age, product version, low completion) 3. Whether we have a source of truth to compare against, and where Ask these in one message, then wait for my answers. If we do, check it’s connected in this chat; if not, I’ll connect it or upload an export. Don’t guess what’s current. If you can’t read completions here (analytics may be off for our account), I’ll upload an export from Juno. Read our academy pages and channels and the courses they point to. Give me a table: item, issue (stale, missing, duplicate, broken link), evidence, suggested fix, effort. This is read-only: don’t edit, archive or unpublish anything. Offer to draft fixes for the top 3; after I approve, save them as drafts and don’t publish until I say so.
The LMS is where these get delivered. Each one is a journey with its own trigger, its own steps, and its own way of proving it worked.
