Meet Juno.
The teammate who closes tickets.
Juno reads the request, checks the policy, and does the work in your systems. Access, resets, onboarding. Closed, not triaged.
Figma editor seat request
Tomas Reyland · @it-support
Check Software access policy for the requester’s team, then assign the Figma editor license through Okta and confirm in the ticket.
Executing tasks
Checked Software access policy
Assigning Figma license in Okta
ROI
The numbers behind a quieter desk
OUTCOME-DRIVEN
Measured by tickets closed, not hours logged
Juno takes the repetitive half of the queue and runs it around the clock. Your engineers keep the work that needs judgment.
JUNO
EMPLOYEE A
EMPLOYEE B
EMPLOYEE C
WHAT OUR CLIENTS SAY
Our queue went quiet and nobody noticed. That was the point.
Ines Okonkwo
CIO
HOW IT WORKS
Learns the job.
Then does the job.
CO-PILOT
Works alongside your team
Juno sits in the queue with your team, reading tickets and proposing the next step for each one.
An engineer approves, edits, or declines. Every decision becomes an example Juno keeps.
Nothing runs unattended until you say so.
LEARNING
Builds skills from your tickets
Resolve a ticket once with Juno watching and it turns the steps into a reusable skill.
Skills carry your policies, your naming conventions, and your approval chain.
Skills are versioned, so changes are visible.
AGENTIC AUTOMATION
Runs the work on its own
Once a skill has earned trust, Juno executes it end to end without waiting on a queue.
Anything outside the policy, or above a risk threshold you set, still pauses for approval.
You see every action and can pull it back at any time.
HELPDESK
Employees ask in Slack. Juno does the rest.
An employee asks in Slack, the way they would ask a colleague.
Juno checks the relevant policy and answers in the thread.
If it needs tracking or approval, Juno opens the Jira ticket itself.
#it-juno-helpdesk
Dev Chaudhuri
Hi, I start managing the data team on Monday. Can I get admin on their Jira project?
Juno
Project admin on Jira needs sign-off from the current owner. I’ve sent the request to Priya and will confirm here once it’s approved.
Dev Chaudhuri
Great. Can you also add me to the #data-oncall channel?
Juno
Done. You’re in #data-oncall, and I’ve opened a ticket so the Jira change is tracked.
View in Jira
INTEGRATION HUB
Connected to the tools your team already runs
Native connections to identity, ticketing, HR, and collaboration systems. No middleware.
FEATURES
What’s underneath Juno
Juno runs on a platform built for enterprise IT: governed actions, durable memory, and a record of everything it does.
Multi-step orchestration
Juno breaks a request into steps, sequences them across systems, and retries or escalates when something fails.
SUPERVISOR
AGENT 01
AGENT 02
AGENT 03
Native actions
Hundreds of pre-built actions, each with scoped permissions, so Juno does the work rather than describing it.
Reset password
Assign license
Add to group
Durable memory
Juno remembers prior tickets, people, and exceptions, so the second request from the same team is faster than the first.
Updating memory…
Skill studio
Build or edit a skill in plain language, test it against a real ticket, and publish it to the team.
Read Software access policy to determine which apps the requester is entitled to, grant them with Grant app access, then notify the user in Slack.
Answers from your own documents
Searching for answer…
VPN setup guide
Confluence · Larkspur
Remote work policy
Notion · Larkspur
Equipment allowance
HiBob · Larkspur
Human-in-the-loop
Set which actions need a person. Juno prepares the change, shows the diff, and waits for the click.
Add user to group
User
dev.chaudhuri@larkspur.com
Group
data-admins
Discard
Approve
Governance and audit trail
Every action is logged with who asked, which policy applied, and who approved. Role-based controls decide what Juno can touch.
Elias Marchetti
Head of IT security
Put Juno on the roster.
See a week of tickets, resolved.
A 30-minute walkthrough with your stack.