A hold is about the box, not the person
Most incomplete returns have ordinary explanations: a part left in a drawer, packed in another box, or never noticed. The hold should say what wasn't observed, not what the customer did.
Say "the lens wasn't observed in the box we received", not "you didn't return the lens".
Held, not denied
Tell the customer the refund is waiting, what is missing, and what happens next. Give them a simple way to answer: the part is coming in another box, they found it, or they believe it was in the box.
- What was received, and what wasn't observed
- That the refund is waiting, not refused
- The policy clause that applies, quoted
- How to reply, and that a person will read it
A person makes the call
The evidence should be in front of the person who decides: what the bench counted, the clip if there is one, and the clause. They can release the full refund, a partial one under the policy, or keep holding.
If the customer says the part was in the box, the person checks the evidence again before anything else happens.
Watch your own wording
When a person overrides a hold, ask for the reason in their own words. If the reasons start to read like boilerplate, the hold rule is catching the wrong boxes, and it's the rule that should change.
The same routine, with a camera and a person
In ReturnWitness, a hold names the line that wasn't observed and the policy clause, the decision agent can only move a case toward HELD, and the refund runs only after a person approves with their typed name. Customer messages drafted by a model in the recorded run are withheld from every replay because they repeated a reader's misread.