juno journey
Book a demo

One assistant to ask. Every agent behind it.

Juno, the Super Agent, is the assistant every user talks to. Ask in plain words: it works out which agent should act, hands the work over, follows it to the end and brings back what needs your OK.

Book a demo

4.7 / 5G2

1Trigger & Signal

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

2Juno, the Super Agent

Juno

  • JunoUnderstands the request
  • JunoRoutes it
  • JunoFollows it

3The agents

  • Jaden
  • Jasmine
  • Jemma
  • Jeremy
  • Jensen

4Loop

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 on Friday; you shouldn't have to find the right agent for each, brief it, and chase all three.

One request, routed to three agents

Example data

Ask one assistant, in plain words

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, employees

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

  • Suggestion chips to start

    Quick-start prompts are there when the chat opens, so nobody starts from a blank box.

  • Answers from your own content

    Courses, goals, your team's progress, your learning budget and your calendar, in plain words.

  • Answers from the docs

    How-do-I questions answered from the Juno docs, the page cited. Rolling out gradually.

  • A table when you need one

    Ask who is behind; get a short table to save, export or open in full.

  • Prefer Claude, ChatGPT or Copilot?

    The same actions work from there →

The right agent gets the work, and nothing falls through

Example data

  • 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 follows what's pending

    It follows each job to the end and brings back what is still waiting.

  • Started without anyone typing

    Not started, not completed, a due date coming, a failed quiz, a changed HRIS attribute.

  • Rules start paused

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

What needs you comes back on one card

Example data

  • The card before any write

    The audience with its count and a named sample, the message, 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

    Without the right permission, a blocked card names the one that is needed.

  • 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 lands where you already look.

  • Routes, sequences, proposes, prepares, reports

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

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

Six agents, each with a job

Questions people ask.

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 words: it works out which agent should act, hands the work over, follows it to the end and brings back, on one card, what needs your OK before anything is written.

How is it different from the agents?

Each agent has one job: Jaden builds and ships, Jasmine finds and funds, Jemma plans, Jeremy validates, 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 nobody has to brief five agents and chase each one.

Do I need Claude or ChatGPT?

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 Claude, ChatGPT or Copilot, the same actions work from there through the Juno MCP, with the same card to approve before anything is written.

What does it do without me?

It reads, finds, drafts and prepares. Nothing is written 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 starts paused until you enable it, and once it runs, a trigger inside Juno, like 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, 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 cancelled first. A rule it creates waits, paused, until you press Enable, and it then lives with your other automations in Juno, where an admin can switch 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 needs none: your LLM reads the change, orchestrating the Juno MCP with Jira's own MCP, and drives Juno. The same holds for GitHub, Confluence, Notion and Google Drive, and for hundreds of apps with an MCP server.

How much does it cost?

Pricing is published on the Pricing page.