A fix, carried out for them.
Employee requests trigger your runbooks automatically. June takes action in your connected tools to resolve the issue.
- Check requester and runbook rules
- Reset MFA in Okta
- Confirm the employee is back in
June turns employee requests into completed actions. It runs your runbooks, follows access policies, and answers from company knowledge. All in Slack or Teams.
A familiar place to ask. A helpful way forward.
Reset an authenticator. Grant the right access. Find the answer. June follows the processes you’ve configured and sees the request through.
Employee requests trigger your runbooks automatically. June takes action in your connected tools to resolve the issue.
June checks eligibility, follows your approval policy, and grants access. Timed access ends automatically.
June draws on your company’s knowledge, respecting the employee’s permissions in each connected source.
Open the VPN app, sign in with your work account, and select Connect.
The conversation and attempted fixes come with the request. Your team can investigate with June, reply to the employee, and mark it done.
Calls freeze in Zoom. A restart and reconnecting the network haven’t helped. Jordan has a customer call this afternoon.
Keep the context with the request…
The conversation, the context, and the steps already tried. Ready when IT steps in.
IT replies from June. The employee gets the reply in the same conversation.
Internal notes and Ask June stay with IT, separate from employee replies.
June creates and syncs a linked ticket, keeping the request and its tracking together.
Employees message June in Slack or Microsoft Teams. June can answer questions, follow software access policies, and automatically run request-triggered runbooks from the conversation.
June can use your Knowledge Base to answer questions, follow configured access policies to request approvals and grant software access, and run the runbooks you’ve set up for employee requests. You define the policies and instructions.
The request can be escalated to your IT team with the conversation and troubleshooting context. IT can review what has already been tried, reply to the employee from June, and mark the request done when it’s resolved.
Yes. Use Ask June inside the request to investigate, bring together relevant context, and work through the next steps with the AI agent. Internal notes and the Ask June conversation stay private to IT, separate from replies sent to the employee.
When Jira is connected, June creates a linked ticket and keeps it in sync with the request. Your IT team can work in June while keeping the ticket connected to the conversation.
Yes. June inherits access permissions from the third-party source. Answers reference only knowledge the employee has access to in Confluence or Google Drive, including shared content.