Let a tool draft, then make the decision yourself
A practical way to use automation: give the tool a narrow job, and keep a person responsible for what goes out.
Give the tool a narrow job
Automation helps when the job is specific: a first draft, a list of options, or a sort of notes you already wrote. A vague request produces a vague result, and then someone has to untangle it.
Decide the standard before the tool starts. If you do not know what a good version looks like, the draft has nothing to be checked against.
Put a person at the end
A draft is not a decision. Someone who understands the message should read it before it is sent, posted, or handed to a team.
The review can be short. Check the facts you can verify, the names, and whether the draft still says the sentence you chose. If it does not, edit it or do not use it.
Do not automate the promise
A tool can speed up the writing. It cannot be responsible for what the words claim. Leave out any result, number, or offer you would not say yourself.
When the stakes are a relationship or a public name, slower and reviewed is the better system. Speed is useful only after the decision is yours.