Autopilot Overview

Autopilot lets you process Data Subject Requests (DSRs) automatically from start to finish, without clicking through each step of the workflow yourself. Assign a ticket to Autopilot once, and MineOS takes it the rest of the way — reviewing it, running its integrations, replying to the requester, and closing it out.

How Autopilot works

When a ticket is assigned to Autopilot, MineOS moves it through the same stages every DSR goes through, without waiting for you to trigger each one:

• Review – the ticket is verified and confirmed eligible to run on Autopilot.
• Process – every automated integration in the ticket's workflow runs.
• Reply – the requester receives a completion email based on the workflow's reply template.
• Close – the ticket closes once all integrations finish and the reply has gone out.
• Redact – the ticket is scheduled for automatic redaction, removing the requester's personal data from your systems.

Eligibility requirements

Not every ticket can run on Autopilot. A ticket is eligible only when:

• It's in an open state — Autopilot can't run on closed, unverified, redacting, or redacted tickets.
• Its workflow contains no manual tasks — every step must be handled by an automated integration.

If a ticket doesn't meet these conditions, the Put on Autopilot button appears disabled, with a tooltip explaining why.

Retries and failure handling

If an integration fails while Autopilot is processing a ticket, MineOS automatically retries the ticket as a whole. This happens up to three times. If all three attempts fail, the ticket is handed back to your queue for manual review. To be notified when this happens, set up the Slack error-notifications integration — see Slack Notifications for DSR. This alert is delivered only through that Slack integration; there is no webhook event to subscribe to for an Autopilot failure.

Autopilot and Required Attention

The Required Attention flag signals that a ticket needs a person to look at it before processing continues:

• If you assign Autopilot to a ticket that's already flagged as Required Attention, the assignment succeeds, but Autopilot won't start processing until the flag is cleared.
• If a ticket already running on Autopilot gets flagged as Required Attention, Autopilot pauses before moving to its next step. Any integration already in progress at that moment finishes normally, but nothing new starts. Once the flag is cleared, Autopilot resumes automatically from where it paused.

Is Autopilot right for your workflow?

Autopilot works best for standardized, fully automated workflows. It's a better fit to keep handling requests manually — for at least some rights or brands — if you:

• Regularly communicate directly with requesters or rely on internal notes as part of processing.
• Want to choose which sources get processed on a request-by-request basis, rather than applying the same flow every time.
• Have workflows that include manual tasks, since those tickets won't qualify for Autopilot.

You can assign Autopilot to individual tickets or in bulk from the Requests table, or set up an automation that assigns it to every new eligible request automatically.