A support-adjacent agent drafted a reply promising a refund window we do not offer. It was caught in review, but it was confident and well written. What is the pattern for keeping promises out of drafts entirely rather than catching them?
Claim-check gate against a facts sheet. Every sentence with a number, a date or the word "guarantee" has to point at a line in the facts sheet or it gets flagged. We use it on lifecycle emails and it removed this class of error.
Also give the agent a list of things it is not allowed to promise, phrased positively: "refund questions are routed to a person". Negative rules get forgotten; routing rules get followed.