One assistant for all of Juno's agents.

Ask Juno. It hands the work to the right agent and reports back.

1Trigger & Signal

  • You ask in Juno
  • A manager asks
  • Something changes in Juno or your HRIS a new hire, a due date, a failed quiz

2Juno, the Super Agent

Juno

  • JunoUnderstands the request
  • JunoRoutes it to the right agent
  • JunoFollows it through

3The agents

  • Jaden
  • Jasmine
  • Jemma
  • Jeremy
  • Jensen

4Back to you

What needs a decision comes back to you, on one card

Five agents. You shouldn't have to know which one to ask.

You want a course updated, a budget checked, and a status update on Friday. You shouldn't have to find the right agent for each task, brief it, and follow up on all three.

One request, routed to three agents

Ask one assistant, in plain language

JunoWhat can I help with?

  • Find a course on project management
  • What goals do I have this quarter?
  • Show me my team's learning progress
  • What's my remaining learning budget?
Ask Juno
  • Admins, managers, and employees

    Every user asks the same assistant, from the Juno home page or the sidebar.

  • Suggested prompts to get started

    Quick-start prompts appear when the chat opens, so no one has to start from a blank box.

  • Answers from your own content

    Ask about courses, goals, your team's progress, your learning budget, and your calendar, in plain language.

  • Answers from the docs

    How-to questions answered from the Juno docs, with the source page cited. Rolling out gradually.

  • A table when you need one

    Ask who is falling behind and get a short table you can save, export, or open in full.

  • Prefer ChatGPT, Claude, or GitHub Copilot?

    The same actions work from there →

The right agent gets the work, and nothing falls through

  • It reads the request

    It works out what you are asking for, even when one request holds three jobs.

  • It picks the agent

    Each job goes to the agent built for it: Jaden, Jasmine, Jemma, Jeremy, or Jensen.

  • It sequences the hand-offs

    Jaden builds, then Jeremy validates. Jasmine finds, then the manager approves.

  • It tracks what's pending

    It follows each job through to the end and reports back on anything still waiting.

  • Started without anyone typing

    Training not started or not completed, an upcoming due date, a failed quiz, or a changed HRIS attribute.

  • Rules start paused

    Its rules are checked for duplicates, then stay paused until you enable them.

Anything that needs your input comes back on one card

  • A review card before any change

    It shows the audience with its count and a named sample, the message, and the scope, all editable.

  • The receipt, in the same thread

    Once you confirm, a receipt with its counts stays in the conversation.

  • The blocked card

    If you lack the right permission, a blocked card names the permission you need.

  • Your role, and no more

    Access is granted only to the data and actions your Juno role already permits.

  • Everything waiting for you, on your Juno homepage and in your notifications

    What the agents bring back appears where you already look.

  • Routes, sequences, proposes, prepares, and reports

    It never decides and never approves. That stays with a person.

How your data is kept: Security and the Trust Center.

Frequently asked questions

What is Juno, the Super Agent?

Juno, the Super Agent, is the AI assistant every Juno user talks to, from the home page or the sidebar. Ask in plain language, and it works out which agent should act, hands off the work, follows it through to the end, and brings back, on one card, anything that needs your approval before any change is made.

How is it different from the agents?

Each agent has one job: Jaden builds and ships, Jasmine finds and funds, Jemma plans, Jeremy validates, and Jensen measures. Juno, the Super Agent, is the one you ask. It sends each request to the right agent, sequences the hand-offs, and reports back, so no one has to brief five agents and follow up with each one.

Do I need ChatGPT or Claude?

No. The assistant is built into Juno: it sits on your home page and in the sidebar once your administrator enables it. If your team prefers ChatGPT, Claude, or GitHub Copilot, the same actions work from there through the Juno MCP, with the same card to approve before any change is made.

What does it do without me?

It reads, finds, drafts, and prepares. It makes no changes on its own: every assignment, notification, or rule comes to you first as a card, with an audience you can edit. A rule it sets up stays paused until you enable it. Once the rule is active, a trigger inside Juno, such as a failed quiz, starts the work.

Can I see everything it did?

Yes, in the conversation where you asked. After you confirm, a receipt appears in the same thread with its counts: how many people were newly enrolled, how many were already assigned, and how many invitations were queued. The receipt stays in the chat transcript, so you can come back to it later.

Can I stop what it started?

Nothing starts before you confirm it, and every card can be edited or canceled first. A rule it creates stays paused until you click Enable, and it then sits with your other automations in Juno, where an admin can turn it off at any time. Assignments and messages go only where the card said.

Does it read our Jira?

Juno has no native Jira connector and doesn't need one: your LLM reads the change by combining the Juno MCP with Jira's own MCP, then runs Juno. The same applies to GitHub, Confluence, Notion, and Google Drive, and to hundreds of other apps with an MCP server.

How much does it cost?

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