The quality of your business English emails isn't determined by the richness of your vocabulary or the number of templates you have. It's about your ability to design the email based on 'who, why, and in what tone.' A request for approval to a CxO should state the conclusion in three lines. A problem report to a client should be structured as facts → countermeasures → prevention of recurrence. A request to an internal team should be friendly yet clear about the deadline. Even though they are all 'business emails,' the approach changes fundamentally depending on the recipient.
Furthermore, as AI tools like Copilot and ChatGPT become integrated into the workplace, the very nature of writing business emails is changing. The era of copying and pasting from templates is over. The new skill required for business professionals is the ability to give appropriate instructions (prompts) to AI and then 'inspect' the quality of the output.
In this article, based on ELT's experience coaching over 10,000 individuals, we will explain a framework for designing emails for different audiences and provide ready-to-use AI prompt samples.
The Era of 'English Email Templates' Is Over
A search for business English email articles will yield a massive number of template collections, such as 'how to write subject lines,' '10 opening phrases,' and 'standard closing expressions.' While these are useful as a foundation, they are insufficient for writing emails that are truly valued in a professional setting.
We repeatedly hear the following from ELT students:
- "I wrote it exactly like the template, but the VP replied, "Can you get to the point?""
- "I thought I was being polite, but the client told me it was "Too much formality.""
- "My emails to the internal team were full of "Could you please kindly..." which actually created a sense of distance."
The problem isn't the correctness of the phrases, but the failure to design the tone and structure to match the recipient.
At the same time, as Copilot and ChatGPT become standard business tools, the way we write English emails is changing significantly. Anyone can have an AI write an email. However, the key differentiator is whether you can judge how the AI's output will be perceived by the recipient.
The Principles of Email Design: Adapting to Recipient and Situation
When designing a business English email, the first things to decide are not the 'correct phrases,' but these three points: 'To whom, for what purpose, and in what tone.'
Recipient | Tone Characteristics | Structural Principles |
|---|---|---|
CxO / Leadership | Extremely concise. 3-5 sentences max. | Conclusion/request in the first sentence → Rationale in bullet points → Clarify next steps. |
Client | Polite + Logical. Put the client's benefit first. | Understanding of the client's situation → Proposal/report → Specific next action. |
Internal Global Team | Friendly + Clear | State the purpose in one sentence → Details → Specify deadline and expected action. |
Business Partner / Supplier | Polite but with zero ambiguity | State facts first → Clearly present conditions/proposal → Set a response deadline. |
From here, we will explain both 'tips for writing manually' and 'prompts for using AI' for each recipient and situation.
Emails to CxOs & Leadership—Get to the Point in Three Lines
Design Principles
A CxO's inbox receives hundreds of emails a day. Whether your email gets read is determined by the subject line and the first sentence.
- Subject: Put what you need them to do in the subject. Not "Update on Japan Market," but "Approval Needed: ¥50M Japan Marketing Budget."
- Body: The conclusion of your request/report in the first sentence. Rationale in the next 2-3 sentences. The final sentence outlines the next step.
- Length: 3-5 sentences for the body is ideal. It should be readable without scrolling.
Tips for Writing Manually
The most common mistake in emails to CxOs is being 'too polite.' Openings like "I hope this email finds you well. I am writing to you today to..." are just obstacles preventing the CxO from getting to the point.
Bad Example:
Subject: Japan Market Update
Dear Mr. Smith,
I hope this email finds you well. I wanted to take a moment to update you on the progress of our Japan marketing initiative. As you may recall, we discussed this briefly during last quarter's review...
Good Example:
Subject: Approval Needed: ¥50M Japan Marketing Budget for H2
Hi John,
I'm requesting your approval for a ¥50M marketing investment in Japan for H2. The Japan market grew 15% YoY, and Competitor A has already committed a similar budget. Projected ROI is 3.2x over 18 months.
Happy to walk you through the details in our Thursday 1:1. Could you confirm if this is on your radar for approval this week?
Sample AI Prompt
When using an internal tool like Copilot or ChatGPT, you can generate an appropriate email with a prompt like this:
Please draft a business English email based on the following conditions.
[Recipient] VP at global headquarters. The relationship is formal, but we speak directly in monthly 1:1 meetings.
[Objective] Request approval for a ¥50 million marketing budget for the Japan market.
[Tone] Extremely concise and professional. The body should be 3-5 sentences long.
[Structure] Include 'Approval Needed' in the subject line → State the request clearly in the first sentence → Provide rationale in 2-3 sentences (ROI, market data) → Propose the next step in the final sentence.
[Background Information] The Japan market has grown 15% year-over-year. Competitor A has already made a similar investment. The projected ROI is 3.2x over 18 months.
[Instructions] Do not use standard greetings like "I hope this email finds you well." Get straight to the point. Avoid overly formal language.Prompt Tip: For CxO-level emails, if you don't explicitly instruct the AI to be 'concise,' 'get to the point,' and 'omit standard greetings,' it will default to generating an overly polite email.
Emails to Clients—Balancing Politeness and Clarity
Design Principles
With emails to clients, the extreme conciseness used for CxOs can be counterproductive. A balance is required to show that you understand the client's situation while clearly communicating your message.
When Sending a Proposal or Solution
- Subject: A subject line that conveys the benefit to the client. Not "Our Proposal," but "Proposal: 20% Cost Reduction Through Supply Chain Optimization."
- Body: Acknowledgment of the client's challenge → Summary of the proposal → Guide to the attached document → Next steps.
Sample AI Prompt:
Please draft a business English email based on the following conditions.
[Recipient] Head of Procurement at a client company. We have had three meetings.
[Objective] Send a proposal for supply chain optimization.
[Tone] Polite and professional. Show understanding of the client's challenges, but do not be overly deferential.
[Structure] Reference our last meeting → Summarize the proposal (1-2 sentences) → Explain the attached document → Propose the next step (suggest a meeting).
[Background Information] In our last meeting, a 20% reduction in logistics costs was identified as a key challenge. The proposal includes a cost analysis and three options. I want to set up a review meeting sometime next week.
[Instructions] Avoid outdated phrases like "Please find attached." Use natural, modern business English.When Reporting a Problem or Apologizing
Reporting a problem to a client is one of the most sensitive situations in business email communication. To maintain trust, it is crucial to avoid making excuses and instead present specific actions in the order of: facts → countermeasures → prevention of recurrence.
Sample AI Prompt:
Please draft a business English email based on the following conditions.
[Recipient] Department head at the client company.
[Objective] Report a delivery delay and present our response plan.
[Tone] Sincere and professional. Apologize concisely in one sentence. Do not make excuses.
[Structure] State the fact concisely in the first sentence → Explain the cause in one sentence → Clearly state the countermeasures and the new delivery date → If a partial alternative is available, offer it → Touch upon preventive measures → Encourage further questions.
[Background Information] The original delivery date was June 15th. Due to a supply chain issue, there will be a two-week delay. The new delivery date is June 29th. A partial delivery of alternative products is possible on June 20th.
[Instructions] Do not end with just "We are sorry for any inconvenience caused." Always include specific countermeasures. Use an active, not passive, tone.Prompt Tip: For apology emails, it's crucial to explicitly instruct the AI to 'not make excuses' and 'include specific countermeasures.' Without these instructions, AI tends to generate vague explanations like "due to unforeseen circumstances."
Emails to Internal Global Teams—Be Friendly and Clear
Design Principles
There are two common mistakes in emails to internal teams.
The first is being too polite, which creates a sense of distance. Overusing phrases like "Could you please kindly..." can sound distant, even with colleagues. The second is being too casual, which leads to ambiguity about deadlines and expectations.
- Tone: Friendly, but specific about the request and deadline.
- Time Zones: When working across multiple locations, specify the deadline with a reference point, such as "by Monday EOD London time."
Sample AI Prompt:
Please draft a business English email based on the following conditions.
[Recipient] Three team members in the London and Singapore offices. They are colleagues I communicate with daily on Slack.
[Objective] Request a review of materials for next week's strategy meeting.
[Tone] Friendly but clear. Maintain a casual tone appropriate for colleagues, but be specific about the deadline and expected actions.
[Structure] State the purpose in one sentence → Briefly explain the attached document → List 2-3 specific points for review in bullet points → Clearly state the deadline → Use a casual closing.
[Background Information] The strategy meeting is next Wednesday. The document is 30 pages. I specifically need feedback on the market forecast in Section 3 and the risk analysis in Section 5. The deadline is Monday EOD (London time).
[Instructions] Avoid overly polite phrases like "Could you please kindly." Phrases like "Could you" or "Would you mind" are sufficient. Be sure to specify the time zone reference.Emails to Business Partners—Polite but with Zero Ambiguity
Design Principles
In emails with business partners, balancing politeness and clarity is paramount. Ambiguous language, especially in emails concerning negotiations or contracts, can lead to future disputes.
Sample AI Prompt (Negotiation):
Please draft a business English email based on the following conditions.
[Recipient] Sales Manager at a supplier. We have a two-year business relationship.
[Objective] Propose a price review upon contract renewal.
[Tone] Polite and clear. Emphasize maintaining the relationship while being specific with the request. Use language that leaves room for negotiation.
[Structure] Express gratitude for the past business relationship → State the intention to renew the contract → Propose a price review (with specific numbers) → Provide rationale for the review (e.g., market price changes, increased order volume) → Set a deadline for a response → Close with a statement showing willingness to discuss flexibly.
[Background Information] The current contract price is $12/unit. The market price has dropped to $10.50. We are prepared to increase our annual order volume by 20%. Our desired price is $10.80/unit. We would like a response within two weeks.
[Instructions] Avoid strong language like "We demand." Use proposal-oriented phrases like "We'd like to propose" or "We believe there's an opportunity to."The 'Inspection Skill' for AI-Generated Emails—This Is What Sets You Apart
Having an AI write your emails is no longer a special skill. What truly adds value is the ability to judge how the AI's output will be perceived by the recipient.
5 Common Issues with AI Output and How to Fix Them
Issue #1: Overly Polite by Default
Without specific instructions, AI will generate text in a formal tone, like "I hope this email finds you well. I am writing to respectfully request..." For a CxO, this is redundant.
Fix: Explicitly state in the prompt: 'No standard greetings' and 'Get straight to the point.'
Issue #2: A Preference for Vague Expressions
"at your earliest convenience" sounds polite, but it doesn't communicate when you actually need a response.
Fix: Specify a concrete date, like "by Friday, June 20th." If time zones differ, clarify the reference point, such as "by June 20th, 5PM EST."
Issue #3: Too Much Passive Voice
Overusing the passive voice, as in "It has been decided that..." or "The report was reviewed by...," obscures responsibility and can make you sound weak.
Fix: Rewrite in the active voice, such as "We decided to..." or "I reviewed the report and..."
Issue #4: Mismatched Nuance and Tone
If you write "We'll do our best" intending to mean 'We'll try our best,' the recipient may interpret it as a firm commitment. AI cannot adjust for these subtle nuances without instruction.
Fix: Specify the 'level of commitment' in the prompt. For example: 'I want to express a positive intention to consider it, not a firm commitment,' or 'I want to clarify that this is a conditional agreement.'
Issue #5: Lack of Cultural Consideration
AI generates emails based on a 'general Western business' standard and does not automatically account for cultural nuances, such as considerations for Asian business partners (e.g., saving face, indirect ways of disagreeing) or European formalities (e.g., titles like Dr./Prof.).
Fix: Include the recipient's cultural background in the prompt. For example: 'To a technical director at a German company; use the title Dr.' or 'To a partner in Thailand; avoid direct refusal and present it as an alternative proposal.'
When 'Polite' Becomes 'Ineffective'—Common Pitfalls for Non-Native Speakers
Directly translating the politeness of Japanese business emails into English can result in overly formal language that creates distance or comes across as long-winded.
Common Expression | Problem | Alternative |
|---|---|---|
"I would be very grateful if you could possibly..." | Overly polite; can sound unconfident. | "Could you [action] by [date]?" |
"I am terribly sorry to bother you, but..." | Apologizing before making a request sounds weak. | "I have a quick request:" |
"Please kindly let me know at your earliest convenience" | Unclear deadline + 'kindly' is redundant. | "Could you let me know by Friday?" |
"I hope this email finds you well" | Redundant for CxOs; too formal for colleagues. | Omit and get straight to the point, or just use "Hi [Name]," |
"Herewith attached please find..." | Archaic, sounds like a legal document. | "I've attached [X] for your review." |
These overly formal expressions are frequently found in the default output of AI. Getting into the habit of checking for this 'excessive politeness' using this table as a reference before sending an AI-generated email will significantly improve the quality of your communication.
Ready to Sharpen Your Email 'Design' and 'Inspection' Skills?
By using the framework and prompt samples introduced in this article, you can elevate the quality of your emails starting today.
However, it's impossible to judge on your own 'how your email is being perceived by the recipient.' Does the conciseness for a CxO come across as rude? Is the tone of an apology email to a client appropriate? Are the nuances in an AI-generated email off the mark? These are areas that can only be properly assessed with feedback from a third party who understands the industry context.
At ELT, we offer one-on-one counseling and trial lessons with native-speaking instructors who hold professional qualifications in English language teaching, specifically for business professionals who use English in their daily work.
- Email 'Inspection' Experience: Bring an actual English email you've written for work and get professional feedback on how to improve its nuance and tone.
- Audience-Specific Writing Assessment: Have your emails to CxOs, clients, and teams evaluated to see if you are using the appropriate register for each.
- AI Prompt Optimization: Review AI-generated email outputs with an instructor and learn practical tips on how to refine them.
'How is my English email being perceived by the recipient?'—this is something you can never truly know on your own. Getting objective feedback is the most reliable first step to dramatically improving your email skills.




