Closing a ticket only after the customer confirms: a "pending confirmation" step with auto-close?

In some service companies I worked for, an incident ticket was never closed by us alone. When we thought it was fixed, the process sent the customer a message (sometimes through a different channel than the original one) with a link to reply and confirm that everything worked. Only that confirmation closed the ticket.

The typical case: a user cannot log in, the admin restarts the server, the login works on their side, the ticket gets closed. But on the customer's side it still fails, for a different reason, and the investigation has to go further. With customer confirmation, those tickets stayed open instead of coming back later as repeat issues.

In Front, as far as I can tell, the team decides when a conversation is Resolved. I found the Open, Waiting and Resolved statuses, custom ticket statuses, delayed rules, and the trigger "Incoming message is received". So I imagine something like this:

1. The agent sets a custom status such as "Pending customer confirmation" and a rule sends the "is it really fixed?" message.
2. If the customer replies "yes", a rule moves the ticket to Resolved. If they say no, it goes back to Open.
3. If nobody answers after a few days, a delayed rule resolves it anyway.

Has anyone built something like this, or is there a better pattern? Two things I could not tell from the docs: whether a reply can be read automatically as a yes or a no (or whether an agent has to look at it), and whether a one-click confirmation link is possible.

Thanks for any ideas.