Confirm whether it is the same issue
A customer can return with the original unresolved problem or a new request in the same thread. Review the earlier closure reason and ask a narrow clarification if necessary. Do not automatically classify all follow-up messages as failed resolutions. Keep the distinction visible so operational reporting and the customer's experience both reflect what happened.
Carry forward the unsuccessful attempt
Summarize the previous action, what the customer observed afterward and what evidence now differs. A new teammate should not ask the customer to repeat a step that clearly failed unless there is a reason to retry. If the case needs a different authority, name that decision and retain the previous owner in the context.
Fictional worked example
In a fictional case, support closed a delivery question after sending a tracking page. The customer returns because the page shows no new scan. The next note should say that the link was received but did not answer the status question. Repeating the same link is not a new resolution; the next step is a verified status check by the responsible team.
Action checklist
- Separate the same unresolved issue from a genuinely new request.
- Record the prior closure reason and the result reported by the customer.
- Avoid repeating a failed step without a stated reason.
- Assign the next decision and tell the customer what will happen next.