own-to-closure

---
name: "own-to-closure"
description: "Use for every open case that must not drift: end-to-end ownership from ack to confirmed fix, follow-up drafts, and resolution tracking."
triggers: ["follow up on an open ticket", "closure board", "overdue ticket", "waiting on customer confirmation", "stale support case", "draft a nudge to the customer", "own this case to closure"]
version: "1"
---

# Own to closure

Use this for every open case that must not drift. Own it end to end, from
ack to confirmed fix, with follow-up drafts and resolution tracking.

## What you need

The open tickets with ages and owners, the last customer touch per ticket,
and the CRM or ticket records behind them.

## Own the queue

1. Walk every open case in age order: what was promised, what moved with
   evidence, what is overdue, and the one next action with its owner and
   date. Stale cases without movement get a nudge draft; overdue ones get an
   urgency flag and an escalation note.
2. Ack first and fast: every case gets an instant acknowledgement draft with
   the expected reply time even when the answer is not ready yet. Draft each
   follow-up in company voice with the receipt: what was done, the date, and
   the check-back question. Follow up 24-72h after each fix; ack within
   hours, resolve within one business day. Resolved cases close only on
   customer confirmation or clear evidence, with the fix, receipt, and lesson
   logged exactly as the records wrote them.
3. Read sentiment per thread — relieved, neutral, still hot — and roll repeat
   themes into voice-of-customer notes with counts, never invented scores.
   Retention risks and upsell signals go to the owner as drafts, never as
   customer promises.
4. Show the closure board in chat, most overdue first, take one round of
   edits, then save it as the day's owned list with dates.

## Output

The closure board plus staged follow-up drafts. Offer to log touches to your
ticket store or CRM when connected, as drafts they approve first.

## Fallbacks

A thread with no reply gets one more nudge with a plain deadline, then an
escalation note — never silent closure.