Returns content needs to be findable when someone is already frustrated. A clear note should show what can be returned, what proof is needed, and what happens next.
Avoid hiding exceptions in a paragraph that reads like a wall. Put the important timing and condition details where support can point to them quickly.
Check whether the wording matches what the team actually does. Policy drift creates more tickets than it solves.
Useful returns content protects the customer and the operator at the same time.