Check the tone of everyday English client emails without starting over

Review the change that matters in this conversation

Start with your draft and the minimum relevant context from the thread. State whether you are following up, reporting a delay, asking for clarification or disagreeing with a request. Include the client's last question when you have permission to share it. Remove unrelated names, attachments and internal discussion.

Ask for a diagnosis before a rewrite. A model that explains which sentence may sound accusatory gives you something to evaluate. A complete polished replacement can bury the actual problem under new greetings and assurances. Google's tone guidance favors straightforward language across different levels of English proficiency; your routine should preserve that clarity without making every email sound identical.

A fictional follow-up: change the implication, not the facts

Suppose a client has not yet sent approved assets and your draft says: You still haven't sent the assets, so we can't do anything. Your true position is narrower: layout work is blocked, other preparation can continue, and you need the assets by Wednesday to keep the current plan. These are invented inputs for this exercise.

A useful revision is: We are waiting for the approved assets to continue the layout work. Could you send them by Wednesday so we can keep the current plan? It removes the accusation and the inaccurate claim that nothing can proceed. It does not promise that delivery is guaranteed merely because the assets arrive.

Use a prompt that prefers minimal edits

Run the same brief through selected available agents in Ask separately when a sentence is sensitive. Compare their reasons, not a generic politeness score. Eight requested editorial lenses are an option for an unusually difficult message, not eight human approvals. Ordinary updates usually need fewer variations.

Check this English client email: [draft]. Relevant thread context: [permitted excerpt]. Purpose: [one next action]. Fixed facts and commitments: [list]. First identify at most three issues affecting tone, clarity or unintended commitments. If the draft is suitable, say so. Then provide a minimally edited version and one warmer alternative. Explain each meaningful change using original wording → revised wording → reason. Do not add deadlines, certainty, concessions or repeated apologies. Keep the requested action clear. Put factual questions outside the email.

Build a lightweight habit around the final check

The overlay does not read the conversation automatically or send the email for you. Its value here is keeping a focused review close to the place you are already working. If a suggested sentence changes a commercial position, take it out of the language review and resolve the underlying decision first.

1. Draft the factual message yourself before generating alternatives. This keeps the review attached to a clear intention.
2. Open Colay, supply the draft and context, and request the minimal-edit review. On macOS, ⌘⇧K opens the overlay by default; the shortcut is configurable.
3. Select only changes you understand. Read dates, conditions and promises separately from tone, then read the final email aloud.
4. Paste the reviewed text into the conversation. Check the recipient and thread context in your mail app before sending.

Save recurring lessons instead of an ever-growing template folder

Keep a brief personal note with three columns: phrase you often write, possible unwanted implication, and a replacement that fits your voice. For example, separate a requested date from a promised date, or replace an unclear pronoun with the actual deliverable. Reuse the lesson, not private details from another client's thread.

After a few real exchanges, review which edits you accepted and which you reversed. The useful result is fewer recurring communication problems and less time spent choosing between nearly identical drafts. Measure your own review time if that matters; do not assume a particular speed improvement or contract outcome from the number of models used.

Questions, answered