## TL;DR
Close the ticket on the workaround, but dont close the problem. Summarize what works for now, name what is still broken, and tell the customer exactly what happens next: who owns the real fix and when they will hear about it. A close that hides the workaround's limits gets reopened.

## The query

```text
how to close a ticket with a workaround in place
```

## Use this when

- The real fix needs engineering time you dont have yet
- The customer can work normally with the workaround
- You are cleaning up a queue of known-issue tickets
- The workaround is stable and documented

## Not for

- Closing tickets as "working as intended"
- Workarounds for security or data-loss issues (those stay open)
- Auto-closing stale tickets with no resolution
- Situations where the customer rejected the workaround

## Steps

### 1. Confirm the workaround actually works for them

Dont assume. Ask: "Can you confirm this gets you unblocked?" A close on an unconfirmed workaround is a reopen waiting to happen.

Expected output: explicit customer confirmation recorded in the ticket.

### 2. Write down the workaround in the ticket

The exact steps, not "the workaround we discussed." Future agents and the customer both need the recipe in writing.

Expected output: numbered workaround steps saved on the ticket.

### 3. Name what is still broken, honestly

One sentence: "The underlying issue, [description], is still open on our side." Hiding this is what makes customers feel tricked when they hit the bug again.

Expected output: the known limitation stated in the closing message.

### 4. Give the real fix a home and a date

Link the internal issue, name the owner, and give the next checkpoint: "Our team is tracking this as [issue ref], I will update you by [date]." The ticket closes; the problem stays tracked.

Expected output: an internal issue link and a follow-up date on the ticket.

### 5. Close with an explicit reopen invitation

"Reply here if the workaround stops working and this reopens automatically." Customers accept workaround closes when reopening is one reply away.

Expected output: the closing message contains the reopen line.

## Ready-to-use template

```text
Good news: we have a way to keep you moving.

WORKAROUND (confirmed working):
1. [step one]
2. [step two]
3. [step three]

What is still broken: [one-line description of the underlying issue].
This is tracked as [issue ref] with our [team], and I will update you
by [date] on the real fix.

I am closing this ticket for now since you are unblocked. If the
workaround stops working, just reply here and it reopens right away.
```

## Variant phrasings

### closing a support ticket with a temporary fix

Steps 2 and 3. The written recipe plus the honest limitation is the whole close.

### how to resolve a ticket when the bug is not fixed

Step 4. The ticket can close when the problem has a tracked home and a date.

### workaround close message template

The template as-is. Swap the bracket parts and send.

## Why it happens

Workaround closes go bad because agents treat "closed" as "done" and customers treat "closed" as "forgotten." The fix is to separate the two in writing: the ticket is closed because the customer can work, and the issue stays open because the bug still exists. When both truths are on the page, nobody feels tricked.

## Edge cases

- The customer rejects the workaround: dont close. Keep it open and escalate the real fix. A forced close is a guaranteed reopen plus a CSAT hit.
- The workaround is clunky: say so. "This is not great, I know" costs nothing and buys patience while the fix is built.
- The real fix has no date: be honest about that too. "I dont have a timeline yet, I will update you when it is scheduled" beats a fake date.
- Workaround stops working later: honor the reopen promise instantly. Nothing kills trust faster than a broken reopen invitation.
- Bulk-closing known-issue tickets: personalize the first line per ticket, then reuse the rest. Bulk closes that read as bulk get bulk reopened.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cUkSUSoxp41NRqEu-B0Bqg