Separate follow-ups from new questions
Not every reply to a closed ticket is a failure. A customer who says thanks, or asks about something unrelated, is not telling you the fix did not work. Look at a sample and sort reopens into: the answer did not work, the answer was incomplete, the customer had a new question, and a thank you. Only the first two are problems with your replies.
Close when the customer has confirmed, not when you have replied
Set tickets to pending after your answer, and let them close automatically after a few days of silence. A ticket that waited for the customer to confirm is far less likely to bounce back than one closed the moment you hit send.
Check the fix before you say it is fixed
When a reply says an issue is resolved, confirm it on your side first: reproduce it, check the account, or look at the logs. Saying fixed and being wrong is the most expensive way to reopen a ticket, because the customer now trusts you less.
Say what happens next
Many reopens are a customer asking what is going on. End each reply with the next step and when they will hear from you. If you are waiting on someone else, say so.
- Name the exact change you made, so the customer can check it.
- Say what to do if it still does not work, and where to reply.
- Do not close a ticket that is waiting on your own team.
Look for patterns by topic
Tag reopened tickets and look at which topics come back most. If one product area accounts for most reopens, the fix may be a better help article or a product change, not better replies.