Closing a ticket due to no response
The whole sequence, not just the last message.
A conversation that goes quiet is not resolved, it is abandoned, and closing it well takes more than one message. This set is the full three-touch sequence: a first check-in, a second nudge with a deadline, and a warm final close, plus variants for the cases where you were waiting on the customer for information, waiting on them to confirm a proposed fix, or dealing with a refund or billing question specifically.
Every blank is in [square brackets] (the order number, the deadline, the fix you proposed), because the right wording depends on what you already told this particular customer. There is also a category for closing with the answer anyway: for the cases where you figured out the fix without their reply and it is worth sending it before you close, rather than closing on silence alone.
The standard sequence
First nudge, day 2
Hi {customer.name}, Floating this back to the top of your inbox, no rush at all. The one thing I still need is [the question you asked]. Whenever you have a minute is fine. And if it sorted itself out, that is a perfectly good answer too. Say the word and I will close it off. {agent.name}
What to change: Replace [the question you asked] with your actual open question, restated in one line so they do not have to scroll up. Touch 1 of 3, sent about two days after your last message.
Second nudge, day 5
Hi {customer.name}, One more check on [the question you asked]. I will keep this thread open until [date], then close it so it stops sitting in your inbox. Reopening is one reply, any time. A single line is plenty. I can take it from there. {agent.name}
What to change: Set [date] two to five days out and make it real, because the next template has to honor it. Touch 2 of 3, around day 5, and deliberately shorter than touch 1.
The close, day 7 to 10
Hi {customer.name}, I am closing this one so it is off your plate. Nothing is lost on our end. If it comes up again, just reply right here and the whole thread comes back exactly where we left it. No form to fill in, no explaining it twice. Thanks for writing in. {agent.name}
What to change: Check that replying to a closed thread really does reopen it in your tool before you promise it. Touch 3 of 3, seven to ten days after your last message, and on the date you named in touch 2.
When you are waiting on information
Nudge when you need a screenshot, order number, or account email
Hi {customer.name}, Still happy to dig into this. I just need one thing first: [the screenshot, order number, or account email]. Quickest way to get it: [the literal steps, one line]. If that is a hassle, tell me and I will see how far I can get without it. {agent.name}
What to change: Include the literal steps, not just the ask. Plenty of these threads go quiet because the customer did not know how to take the screenshot. Touch 1 of the waiting-on-information sequence, about two days after you asked. Use the standard second nudge in between.
Close when the information never arrived
Hi {customer.name}, I am going to close this one for now so it is not sitting unanswered in your inbox. If you still want help with [the issue], reply here with [the screenshot, order number, or account email] and I will pick it straight back up. Everything we already covered is still in the thread, so you will not have to explain it again. {agent.name}
What to change: Name the missing item one more time so replying is a single action. Touch 3 of the waiting-on-information sequence, seven to ten days after the first ask.
When you proposed a fix
Check-in after you suggested a fix
Hi {customer.name}, Checking in on [the fix you suggested]. Did that do it? If it did, you do not need to reply. I will close this in a few days and take the quiet as good news. If it did not, tell me what you are seeing now and I will keep going. {agent.name}
What to change: Keep the "you do not need to reply" line. It is the whole point: it makes silence a valid answer instead of an outstanding obligation. Touch 1 of the after-a-fix sequence, two to three days after you proposed the fix.
Close assuming the fix worked
Hi {customer.name}, Closing this one on the assumption that [the fix] did the job. If I have that wrong, reply and it reopens. For next time, the short version was: [the fix in one or two lines]. {agent.name}
What to change: Restate the fix in one or two lines so the thread is still useful when they search their inbox for it in six months. Touch 3 of the after-a-fix sequence, seven to ten days after the check-in.
Refunds and billing
Close a refund or billing thread
Hi {customer.name}, Quick update on your [refund or billing question], then I will get out of your inbox. Where it stands: [exactly what has and has not happened to the money, with the amount and the date]. Nothing here is waiting on you. I am closing the thread so it stops pinging you, and that changes nothing about the [refund, credit, or charge]. If it has not landed by [date], reply here and I will chase it. {agent.name}
What to change: Never close a money thread without the amount, the date, and what happens next. Say plainly that closing the thread does not close the refund, because that is what the customer will assume. Send around day 7, and only once the money side is actually settled or scheduled. For the earlier touches, use the standard first and second nudge with the amount added.
Closing with the answer anyway
Close, but answer what you think they needed
Hi {customer.name}, Rather than close this with nothing useful in it, here is my best guess. If you were running into [your best guess at the problem], the answer is [the answer, two or three lines]. I will close the thread here so it stops sitting in your inbox. If I guessed wrong, reply and I will start over with you properly. {agent.name}
What to change: Only send this when the guess is genuinely likely. A wrong guess reads as not having read their message, which is worse than a plain close. Use it in place of touch 3 in any of the sequences above.
Frequently asked questions
How many follow-ups should I send before closing a silent ticket?
Two, generally: a first check-in a few days after your last message, and a second one a few days after that with a clear "closing this out if I don't hear back by [date]" line. Closing after a single unanswered message reads as impatient; chasing a customer past two nudges starts to feel like pressure rather than help.
Is it rude to close a ticket the customer never replied to?
No, as long as you said you would. The rudeness is in closing silently with no warning, not in closing at all. The second nudge in this sequence exists specifically to give a deadline, so the close that follows is the thing you already told them would happen, not a surprise.
Should I still send the answer if I close a ticket with no reply?
When you have one, yes. If you figured out the fix, the setting they needed to change, or the reason for the delay without their confirmation, send it and close, rather than closing on silence with nothing to show for it. The "Closing with the answer anyway" category in this set is for exactly that: a customer who searches their email later finds the answer waiting, even though they never replied.
Does closing a conversation mean the customer can never reply again?
No, not in AcornReply. A resolved conversation stays closed until a new reply arrives from the customer, at which point it reopens automatically. Closing a silent thread is a housekeeping decision about your queue, not a door you're locking on the customer.