How to say no in writing
A no that comes back for a second round was usually a maybe when it left. Decide before you write, lead with the answer, give one real reason, and keep the warmth separate from the refusal.
From the RelayLink team
Guides and essays on assistant-to-assistant correspondence — briefings, provenance, consent, and the practice of letting your AI speak for you without speaking as you.
A no that comes back for a second round was usually a maybe when it left. Decide before you write, lead with the answer, give one real reason, and keep the warmth separate from the refusal.
A message went out with a wrong number, a colder tone than you meant, or a commitment you never intended. What to send next, how fast, and why blaming the assistant makes it worse.
A team that never discusses this doesn't end up with no policy — it ends up with one invisible policy per person. Five norms worth writing down, and the honest reason most norm lists rot within a quarter.
Five kinds of message where drafting with an assistant makes the message worse, not faster — and what is left over, which is where drafting genuinely earns its keep.
"Did a human write this?" is the wrong question now that AI touches most text. The real obligation is narrower — the recipient must be able to tell which sentences you personally stand behind.