Skip to main contentQubit and AITicket Autopilot
- How Ticket Autopilot worksTicket Autopilot has a plan ready when you open a ticket; you review it, lock it, and QuantumOps runs it step by step, asking before it changes anything or writes to a customer.
- Approving Autopilot stepsWhen an Autopilot step needs an approver, the people your administrator chose get the request in the browser extension and in Teams or Slack; the first decision wins.
- Autopilot settingsAutopilot settings is where an Administrator turns Autopilot on, sets modes and limits, chooses approvers and tool rules, connects Autopilot to StackJack for unattended runs, chooses the Halo agent it acts as, sets how sure it must be to decide on its own and picks the tickets that are planned ahead of time.
- Autopilot playbooksAutopilot reads your closed tickets and writes down how your agents resolve each kind of ticket, as a playbook with the checks they make, the decision they take and what they do next; this page covers reading a playbook, the time it saves and turning it into a routine.
- Autopilot routinesAutopilot routines solve tickets that match a pattern on their own, under limits an Administrator sets; this page covers creating and editing a routine, ending it in a decision, the built-in escalate and priority steps, shadow mode and run history.
- Autopilot activityThe Autopilot activity page lists the plans QuantumOps built and ran, the plans waiting for a person, the approvals asked for and decided, and an audit of every plan.