## TL;DR
Close abandoned tickets after two bumps over seven days, with a closing message that summarizes where things stand and says exactly how to reopen. Never close silently, and never close with blame. The close message is a safety net, not a verdict: it should make reopening effortless, because a meaningful share of "abandoned" tickets are customers who got busy, not customers who gave up.

## The query

```text
how to close a ticket the customer abandoned
```

## Use this when

- Your queue is full of tickets with no customer reply
- You need a team rule for when to close
- Agents are afraid to close tickets
- Customers complain about tickets closed without warning

## Not for

- Resolving tickets with an actual answer
- Closing engineering escalations
- Churn-risk or high-value account handling
- Closing tickets the customer asked you to close

## Steps

### 1. Confirm it is actually abandoned

The customer has not replied to your last two messages, and the ball has been in their court for at least 5 business days. If you are waiting on engineering, the ticket is not abandoned, it is blocked.

Expected output: a clear abandoned state, not a blocked or waiting state.

### 2. Send the final bump with a close warning

Restate the one question you need, and say the ticket will close in 48 hours without a reply. Short, factual, no guilt.

Expected output: the customer has explicit notice and a deadline.

### 3. Close at the deadline with a summary

Write the closing message as if the customer will read it a month later: what the issue was, what you asked for, what happens next. Set the status to solved or closed with a "customer unresponsive" reason code.

Expected output: a closed ticket that explains itself to anyone who opens it.

### 4. Leave the door wide open

"Just reply to this thread and it will reopen" or a one-click reopen link. Abandoned does not mean resolved, make the return path zero friction.

Expected output: the closing message contains an explicit, working reopen path.

### 5. Tag it for the data

Use a consistent reason code (customer-unresponsive, abandoned). This is how you find out that 40% of your abandons are one ticket type that needs a better first reply.

Expected output: every closed-abandoned ticket carries the same tag for reporting.

## Ready-to-use closing message

```text
I havent heard back, so Im going to close this ticket for now to keep
your queue clean.

Quick recap: your exports were coming out blank, and I asked which
browser you exported from so I can reproduce it on my end.

Just reply to this thread anytime and it will reopen right where we
left off.
```

## Variant phrasings

### closing stale support tickets

Same five steps. The difference between stale and abandoned is only the reason code you file under.

### what to say when a customer stops responding to a ticket

The closing message above. Keep it warm and factual, never "since you have not responded" as the opening line.

### auto-close policy for unresponsive customers

Steps 2 through 4 are your policy. Automate the bump and the close in your ticketing tool, but keep the message human-written.

## Why it happens

Agents avoid closing because it feels like giving up, and customers hate silent closes because it feels like being dropped. The written rule with a deadline solves both: the agent follows the clock, the customer gets warning and a summary. Most abandoned tickets are timing, not dissatisfaction, so the graceful close protects the relationship for the eventual return.

## Edge cases

- Customer replies after close: reopen immediately, acknowledge the gap warmly, never make them re-explain. The summary you left in step 3 makes this easy.
- Repeat abandoners: if the same customer abandons three times, the problem is usually the questions you are asking, not the customer. Review the thread.
- High-value accounts: dont auto-close. Hand the ticket to the account owner with the full summary instead.
- Abandoned mid-escalation: if engineering is still working, the ticket is not abandoned. Close the customer thread with a status update and track the engineering work separately.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_Spf_dLP8iDWAZHR4ghq2lw