Most support policies were written for people who already know the business. "Use discretion on late returns" makes sense to someone with two years on the team. To an agent, it is an invitation to guess.
The fix is not a longer policy. It is a policy where every decision has a rule, every rule has an owner, and every exception says what to do instead.
One decision per paragraph
Split long policies into short sections that each answer one question: can this item be returned, how is the refund paid, what happens if the item is damaged. Agents retrieve paragraphs, not documents, so a paragraph that answers two questions will be cited for both and fully right for neither.
Replace judgement words with numbers
- "Recently" becomes "within 30 days of delivery"
- "A small amount" becomes "under £40"
- "Use discretion" becomes "offer store credit; hand over if the customer declines"
If the team genuinely needs judgement in a case, say so and make it a handoff rule. That is a decision too.
Write the exceptions as instructions
"Final sale items cannot be returned" tells the agent what not to do. "Final sale items cannot be returned; offer to check the warranty instead" tells it what to do next. Every no should come with a next step.
Every no should come with a next step.
Give every policy an owner and a version
When a customer is told something wrong, you need to know which version of which policy said it and who can fix it. In Parley each knowledge source shows its owner, its last sync and the conversations that cited it, so a fix is one edit away.
Test with real questions
Take fifty real customer questions about the policy and run them as simulations before you publish. The failures will tell you which paragraphs are still leaning on judgement.



