Premature Closure Detector identifies tickets closed without customer confirmation. It adds a configured tag and a private note so teams can review tickets that may have been closed too early.
Before you start
Make sure your Help Desk account has:
- Access to Autopilot.
- Ticket categories where this AI Agent should check closed tickets.
- A tag that clearly identifies possible premature closures.
- A clear rollout plan for whether your team should review the AI Agent's work first.
Hire the AI Agent
- Open Autopilot > Home.
- Search for Premature Closure Detector.
- Select Hire Agent.
The setup flow opens on the Onboard step.
Configure the AI Agent
- Give your AI Agent a name.
- Enter a description that explains what the AI Agent should do.
- Choose Supervised Mode or Autopilot Mode.
- Select the ticket categories where the AI Agent should run.
- Under Agent Actions, enter the tag to add when a ticket appears to have been closed prematurely.
- Select Continue.
Use a dedicated tag so reports and ticket searches can distinguish these results from other closure-related reviews.
Review before deployment
- Confirm the selected categories and operating mode.
- Verify the tag that will be added to flagged tickets.
- Select Deploy Agent only after the configuration is correct.
What happens after deployment
The AI Agent runs when a ticket is closed in a selected category. When it determines that the customer did not confirm resolution, it adds the configured tag and a private note for review.
Review early results in Agent Activity Log before using the tag in reports or follow-up automation.
Troubleshooting
- A closed ticket is not checked: Confirm that the ticket belongs to a selected category.
- The expected tag is missing: Review the configured premature-closure tag and the activity result.
- Tickets are flagged incorrectly: Review whether customer confirmation is explicit in the conversation and use Supervised Mode while tuning the rollout.