A monthly update that leads with the numbers, names the problems, and makes a specific ask.
Compare shortlisted vendors against criteria you weighted before you saw any of the answers.
Explain an inherited formula in plain language, then say what breaks it and how to simplify it.
Turn a resolved ticket thread into a structured help article other customers can find.
A reply that lowers the temperature, owns what is ours, and offers a concrete next step.
Describe the question in words, get a query back with its assumptions and performance notes stated.
Turn a vague bug report into a reproducible ticket with severity, likely cause and next step.
Rejections that are kind, specific enough to be useful, and safe to send at volume.
A four-touch follow-up sequence where each message adds something new rather than nudging again.
Short connection notes that earn an accept, inside the character limit, without pitching.