> ## Documentation Index
> Fetch the complete documentation index at: https://helpdocs.getthread.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation Completion Auto-Close

> When note evidence shows an intent or external automation actually finished the work, verify it and close the ticket with an audit note — aborting the moment any human message arrives after completion. Answers the "auto-close tickets the automation already handled" workflow.

<Info>
  **Category:** Automation & Flows · [View source ↗](https://github.com/bryan-getthread/skills/blob/main/skills/automation-and-flows/automation-completion-auto-close/SKILL.md)
</Info>

**Connectors:** none — works with Thread out of the box

**Role:** [Service & Ops Manager](/start-here/roles/service-ops-manager)

**Outcome:** Time & Cost Savings (Capacity)

**When to use:** An intent or automation resolves a request end-to-end (password reset, provisioning step) and the ticket lingers open; "close the ones the automation already finished"; a flow should sweep automation-handled tickets closed once the completion note lands. Fires on the NOTE-ADDED event (the completion note landing) — not a timer or "N minutes after".

**Run it:** on one ticket · or as a Flow (triggered when a completion note is added).

## Prompt

```
Close tickets an automation genuinely finished — but only after confirming from note
evidence that it completed, and only if no human has said anything since. When in doubt,
leave the ticket open; a false close is worse than a lingering open ticket.

Your entire reply is the audit note, verbatim: either `AUTO-CLOSED. Automation: <name>.
Evidence: <note ref>. No human message after completion.` or `NO ACTION. Reason: <no
completion note | human message after completion | status missing>.`

1. Re-read the ticket and its full thread, newest-first.

2. Find explicit completion evidence: a success message from the intent/automation, a
   "completed / done / provisioned" system note tied to THIS ticket's request — not a
   "started" or "queued" note, and not a client asking for the thing. No unambiguous
   completion note -> stop. Never fabricate completion or infer "it probably worked" from
   silence.

3. Abort on any human message after completion. If a technician or client posted anything
   (question, correction, new request) after the completion note, the ticket is live again
   -> do nothing. This abort is absolute.

4. Confirm the target closed/resolved status exists (respect the desk's closed-status
   taxonomy). Status missing on tenant -> no action.

5. Close the ticket by moving it to the resolved/closed status and leave a plain-text audit
   note: which automation completed, the note it was evidenced by, and that no human message
   followed.

Status change and the audit note are the only writes — no reply to the client, no re-
categorization. At most one close per ticket. Notes are plain text (PSA compatibility).
```


## Related topics

- [Status Automations: Auto-Update Thread Statuses](/inbox/status-automations.md)
- [Automation & Flows](/skill-library/automation-and-flows/overview.md)
- [Flow Builder](/skill-library/automation-and-flows/flow-builder.md)