Generator
Refusal Policy Generator
Most assistants are told to be helpful and honest, which does not stop one inventing a refund policy. A refusal policy names the categories it must decline and the exact words it uses instead. This writes that document.
- Names the categoriesNot just “be careful”
- Gives the wordingWhat it says instead
- Sector awareMedical, legal, financial
Work it out
Your numbers
Your system prompt
This is an operating policy, not legal advice. If you are in a regulated sector, have your compliance owner read it before it goes live.
What the numbers mean
A refusal policy is not a safety disclaimer
Disclaimers protect you after something goes wrong. A refusal policy stops the thing going wrong, by naming in advance what the assistant is not permitted to answer.
The wording matters as much as the rule
“I do not have that” followed by a real next step keeps trust. An apology followed by a guess destroys it. Specify the sentence, not just the intent.
A wrong refusal is also a defect
If the assistant declines something your documentation clearly answers, the source is unclear. Log both directions or you will only ever fix half the problem.
Regulated sectors need this before launch, not after
The medical, legal and financial clauses are not decoration. In those sectors an invented answer is a regulatory event, not a support ticket.
Questions
It makes it less talkative and more trusted. Visitors who get “I do not know, here is who does” come back. Visitors given a confident wrong answer do not.
Into the system prompt, and into whatever review process you use for answers. It is a document for the people configuring the assistant as much as for the model.
No. It is an operating policy. If you work in a regulated sector, your compliance owner should read it before it goes live.
Want this run against your actual site?
Tell us the page your assistant lives on and the questions you care about. A person runs them and sends back the raw answers.