An important client email deserves more than one tone option

Start with the decision the email must unlock

Write a short brief before asking for polished English: who will read the message, what they already know, what you need them to decide, and which commitments you are authorized to make. A request for missing materials needs a different structure from a refusal to include additional work. Simply asking for a professional tone hides that distinction.

Keep a fact block separate from tone preferences. Include the approved price, deliverable, dates, dependencies and next action. Mark unknowns explicitly. Give the models only material you are permitted to share; replace client names and confidential project details when they are unnecessary. The useful comparison is how each draft expresses the same position.

A fictional scope-change email, expressed three ways

Suppose a fictional design client requests two additional screens after approving a four-screen scope. The extra work has not been priced. You can discuss it on Tuesday, but cannot promise the original delivery date if the scope changes. The email should invite a decision without silently accepting the work. These are example inputs, not a Colay customer result.

Ask for variants and their consequences

In Colay, select available agents and use Ask separately to compare their first drafts. Request clearly different styles rather than eight minor paraphrases. If eight lenses help, name them: warm, neutral, concise, consultative, executive, formal, boundary-setting and relationship-repair. The number describes requested writing approaches; it does not mean eight independent reviewers have endorsed the email.

Draft an English email for a new client using only this fact block: [approved scope, requested change, dates, dependencies, next action]. Audience and relationship: [context]. Create three versions: warm and collaborative, direct and neutral, and firm with a practical option. Keep all commitments identical. Do not invent a price, deadline, apology for an unconfirmed fault, or concession. For each version, give a subject line, the email, and one sentence explaining its communication tradeoff. List missing facts separately. Flag any wording the recipient might read as acceptance of extra work.

Review commitments before reviewing elegance

Google's developer writing guide recommends clear language for readers with different levels of English proficiency. Here that means avoiding idioms such as ballpark it or move the goalposts when a literal sentence is clearer. This is a writing principle, not evidence that a model can predict how your particular client will react.

1. Read only the dates, amounts, scope statements and promises in each draft. Reject a version that changes them, even if it sounds excellent.
2. Check the action requested from the client. They should know whether to approve an option, supply information or arrange a conversation.
3. Compare one sensitive sentence across drafts. Explain why the chosen wording fits this relationship instead of selecting the longest or most confident answer.
4. Read the complete email once in context, then paste the approved version into your mail client and send it yourself.

Keep the choice as a reusable editorial note

Save the final email with a short note: audience, communication goal, selected tone and phrases rejected for changing the terms. That note is more reusable than a folder of unexplained drafts. On the next important email, reuse the decision criteria while updating the facts. If the wording changes obligations or responds to a dispute, route it to the person responsible for those commitments.

Questions, answered