Zendesk Follow-Up Tickets
A customer replies to a ticket you closed last month. Zendesk follow up tickets are what you get: a new ticket linked to the old one, rather than a reopen. That's deliberate.
Why closed means closed
Solved and Closed are different states and the distinction is the whole article. Solved means you think it is done. Closed means the record is sealed: it cannot be edited, reopened, or merged.
Tickets move from Solved to Closed automatically, via an automation that ships with most accounts and typically fires a few days after the solve. You can adjust that window, and a lot of teams should, because the gap between Solved and Closed is your customer grace period.
Once closed, a reply from the requester can't land on the original. So Zendesk creates a follow-up: a new ticket that carries a reference back to the one that spawned it.
What Zendesk follow up tickets carry
It's a real, ordinary ticket with a couple of distinguishing features.
It records that it came from another ticket, so an agent opening it can jump straight to the closed original and read what happened last time. That context transfer is the entire point, and it's why follow-ups are better than a bare new ticket with no history.
It does not, however, inherit everything. Assignment, custom field values and tags don't all carry over automatically, so a follow-up can land in a general queue rather than back with the agent who handled the original. If that matters to you, a trigger can copy what you need.
You can also create a follow-up deliberately from a closed ticket, which is the correct move when a customer raises the same issue again and you want the thread of history preserved rather than starting cold.
Routing them properly
Left alone, follow-ups drop into the same intake path as everything else. That is a missed opportunity, because a follow-up is by definition a returning problem and returning problems deserve a faster look.
Zendesk exposes the follow-up nature of a ticket as a condition you can build on, though the exact condition naming has shifted over time, so check what your account offers rather than copying a snippet blindly.
The setup worth building:
Reporting on follow-ups
Follow-up rate is one of the most honest quality metrics available and almost nobody tracks it. It answers a question CSAT only gestures at: did the fix actually hold?
In Explore, count tickets carrying your follow-up tag against total solved for the same period. Slice by the group or the topic of the original. A category with a follow-up rate three times your average isn't a support problem, it is a product problem or a documentation problem, and now you have the evidence to say so.
Watch one confound. If your Solved to Closed window is very short, you manufacture follow-ups: a customer who replies on day two gets a follow-up ticket instead of a reopened one, and your rate climbs for reasons that have nothing to do with quality. Lengthen the window and the number gets more meaningful.
Follow-up or duplicate?
Worth separating, because they look similar in a queue and mean opposite things.
A follow-up is the same customer returning to a resolved conversation. The history is relevant and the link is valuable. A duplicate is the same issue arriving more than once in parallel, usually because the customer got impatient or wrote in through a second channel.
Follow-ups you keep. Duplicates you merge, and note that merging requires the target to be less than Solved, so a duplicate you catch late may have to be handled as a follow-up whether you like it or not.
A quick way to tell them apart in the queue: check the timestamps. If the original was solved and closed and days have passed, it is a follow-up and the history is genuinely useful. If both tickets are open and were created within the same afternoon, that is a duplicate and one of them should not exist.
Two settings worth reviewing
First, the automation that closes solved tickets. Look at how many days it waits and ask whether that matches how your customers behave. A B2B account where somebody checks their email on Friday afternoons needs a longer window than a consumer product where replies arrive within hours.
Second, whether your notification on solve tells the customer what happens next. A message saying "reply any time and we will pick this up" is accurate, sets the right expectation and costs you nothing. Silence invites the customer to open a fresh ticket instead, which loses the history entirely and is worse for both sides.
Frequently asked questions
What happens on a Zendesk closed ticket reply?
A Zendesk closed ticket reply creates a new follow-up ticket linked to the original, because closed is final. That's deliberate, and it's why your reopen rate looks lower than it feels.
Can you reopen a closed ticket in Zendesk?
No. Closed is final. A reply from the requester creates a follow-up ticket that links back to the closed original instead.
What is the difference between Solved and Closed?
Solved is your judgement that the work is done and the ticket can still be reopened. Closed is a sealed record, set automatically by an automation some days after the solve.
Does a follow-up ticket keep the original assignee and fields?
Not all of them. It carries a link back to the original, but assignment, tags and custom fields do not all copy across. Use a trigger if you need specific values preserved.
How do I report on Zendesk follow up tickets?
Tag them on creation with a trigger, then in Explore compare that tag count against solved volume for the period. Slicing by group or topic is where the useful findings are.
Should I shorten the time before tickets close?
Usually not. A short window pushes ordinary replies into follow-up tickets and inflates your follow-up rate for no good reason.
The ones that are not follow-ups
Some returning tickets are genuine follow-ups. Others are the same request arriving more than once. Ticket Merger tells them apart.
Start free trial14-day free trial. No credit card required.