
Most professionals lose time and opportunities because their emails are vague, too long or oddly toned. This guide gives you reusable structures, phrases and checklists so every business email you send gets a fast, useful reply.
If you are also learning a second language — Japanese, Chinese, Korean or German — the same email skills transfer directly. That is where Corodomo helps: paste a YouTube link or upload a video, and it auto-generates bilingual subtitles, so you can study how real professionals phrase requests, apologies and follow-ups. You can look up any word in detail, practise pronunciation with CoroAI, then lock the new phrases in with flashcards and vocabulary tests. Think of it as a phrase bank you build yourself, from real business conversations.
A results-driven email answers three reader questions fast: What do you want? Why does it matter to me? What do I do next? If the reader has to hunt for those answers, the email gets postponed — and postponed emails rarely get answered.
Use a fixed five-part skeleton. It works for a two-line message or a full project update, and it stops you from rambling when you are tired or writing in a second language.
Keep the whole message under 150 words unless the reader expects a report. Long emails feel like homework; short emails feel like progress. If you truly need more space, put the extra detail in bullet points after the ask, so skimmers still get the point.
Weak version: "Hi, I was just wondering if maybe you had a chance to look at the thing I sent earlier?"
Strong version: "Hi Maria — could you approve the Q3 budget by Thursday 12:00? The file is attached; only section 2 needs your input."
The subject line is a sorting tool, not a title. Your reader scans a list of 40 subjects and decides what to open. A good subject says the topic and the action, so the reader already knows what is inside.
A reliable formula is: [Topic] — [Action] by [Date]. You can drop the date for informational emails, but keep the topic specific. "Quick question" tells the reader nothing and often gets ignored.
| Weak subject | Strong subject | Why it works |
|---|---|---|
| Meeting | Client kickoff — confirm Tuesday 10:00? | Topic + decision needed |
| Invoice | Invoice #4471 — payment due 30 June | Reference number for searching |
| Following up | Proposal follow-up — your feedback by Friday? | Names the action and deadline |
| Important!! | Contract draft — two clauses need your sign-off | Specific, calm, actionable |
Openings should do two jobs: confirm the relationship and set the context in one line. "I hope this email finds you well" is harmless but empty — it delays the point. Replace it with a line that shows you remember the relationship: "Thanks for the call on Monday — here is the summary and the one decision we still need."
Opening to replace: "Dear Sir/Madam, I hope this email finds you well. I am writing to you today because..."
Opening to use: "Hi Daniel — following our call, here are the three items we agreed on and the one approval I need from you."
English business tone sits between two failure modes. Too soft ("I was just wondering if perhaps you might maybe...") and the reader cannot tell whether you need anything. Too blunt ("Send me the file.") and the reader feels ordered around. The target is warm and direct: friendly words, clear verbs.
Three tools do most of the work. First, modals: could and would soften a request without hiding it. Second, "I" statements instead of accusations: "I still need the figures" beats "You forgot the figures". Third, a short reason: people accept requests more easily when they understand the impact.
Watch for accidental aggression. Words like "obviously", "as I said", "again" and "you failed to" read as blame, even when you mean them neutrally. In writing, the reader supplies the tone — and tired readers supply a harsh one.
| Too soft | Too blunt | Balanced |
|---|---|---|
| If you maybe have time... | Do this today. | Could you send this by end of day today? |
| Sorry to bother you again... | You still haven't replied. | Just checking in — is Thursday still realistic? |
| I might be wrong, but... | That's incorrect. | I read section 4 differently — can we confirm? |
| No problem at all, no rush! | This is urgent. | This would help us hit the Friday launch. |
A request needs four parts: the action, the owner, the format and the deadline. Miss any one and you get a reply asking for it — which costs you a full day. "Can you look at the deck?" fails all four tests. "Could you add your comments to slides 5–8 in the shared deck by Wednesday 15:00?" passes.
Deadlines work better with a reason attached. "By Friday, because the printer needs two working days" is far easier to accept than "ASAP". Avoid "ASAP" entirely: it means "urgent to me, vague to you", and it pushes the reader to guess your priorities.
When the request is big, offer a choice. "Would Thursday or Monday suit you better?" gives the reader control while still moving things forward. This is especially useful across cultures, where a direct "no" may be uncomfortable and a choice is easier to answer.
| Element | Weak | Strong |
|---|---|---|
| Action | take a look | add comments to slides 5–8 |
| Owner | (unclear) | you |
| Format | somehow | in the shared deck, tracked changes |
| Deadline | soon | Wednesday 15:00 CET |
Most deals are lost in the follow-up, not the first email. The rule is simple: follow up once with new information, not with pressure. "Just bumping this" adds nothing. "Adding the updated pricing we discussed — does Thursday still work?" gives the reader a reason to reply.
Space follow-ups sensibly: two to three working days for internal colleagues, about a week for external partners, unless there is a stated deadline. After two unanswered follow-ups, switch channel — a short call or message often resolves in two minutes what email cannot resolve in two weeks.
Saying no is a core business skill. A good refusal has three parts: acknowledge, decline clearly, offer an alternative. "Thanks for thinking of me. I can't take on the audit this month — I could review the draft in early July instead." You protect the relationship and you stay honest.
Follow-up template: "Hi Priya — checking in on the vendor contract. Since the renewal date is 15 July, could you confirm by Friday? If the legal review is still open, I can send a short summary of the two open clauses to speed it up."
Reading templates helps, but you only own a phrase when you can produce it under pressure. Video is an efficient way to build that muscle. Real meetings, negotiations and interviews contain the same phrases you need in writing — and hearing the tone teaches you more than reading a list.
Here is a practical routine you can run in 20 minutes a day. Pick a short business video in your target language, watch it with bilingual subtitles, and collect five phrases. Then use each phrase in a real or simulated email the same day.
If you are learning Japanese, the same method works well for keigo email patterns. For example, 仕事 (shigoto – work) appears constantly in business contexts, and knowing how it combines with polite forms will make your Japanese emails sound far more natural. You can also study individual characters such as 勉 and 学, which together form the word for study — useful vocabulary when discussing training or onboarding.
Corodomo supports this loop directly: bilingual subtitles for comprehension, detailed word lookup for accuracy, speaking practice with CoroAI for pronunciation, and four vocabulary tests — choose the correct meaning, listen and type, type the reading, and write an example sentence. The last test is the one that changes your writing, because you produce a sentence instead of recognising one.
| Phrase | Reading | Meaning |
|---|---|---|
| 勉強 | benkyō | study |
| 仕事 | shigoto | work, job |
| お世話になっております | osewa ni natte orimasu | standard polite business greeting |
| 確認 | kakunin | confirmation, check |
Aim for 80–150 words for a standard request. The email only needs the context, the ask, the essential detail and the deadline. If you need more, use short bullet points after the ask so the reader can skim. Anything over 300 words usually belongs in a document, not an inbox.
It is not wrong, but it is empty and delays your point. Replace it with a specific line that shows context: "Thanks for the call on Monday — here is the summary." That builds rapport faster than a generic greeting.
Add something new each time: an updated file, a date, a decision. Wait two to three working days internally and about a week externally. After two follow-ups, switch to a call or a short message. Never use "as per my last email", which reads as blame.
Give one specific date and time, plus a short reason. For example: "Could you confirm by Thursday 15:00? The printer needs two working days." Add the time zone if your reader is in another country. Avoid "ASAP" because it is vague and creates stress.
Use short business videos with bilingual subtitles, collect five phrases per session, and immediately write a two-line email using two of them. Say each phrase aloud to fix the rhythm, then test yourself with flashcards the next day. Corodomo supports this with subtitles, word lookup, speaking practice and vocabulary tests.
Professional emails get results when the reader can act within seconds. Use the five-part structure, put the ask and the deadline near the top, and keep the tone warm and direct rather than vague or blunt.
Build a personal phrase bank from real sources. Video with bilingual subtitles gives you authentic business language, and tools like Corodomo let you turn what you hear into phrases you can actually write — with word lookup, speaking practice, flashcards and four vocabulary tests.
Finally, review before you send. Check the subject line, the single ask, the deadline and the closing line. Three small points to remember: one email, one request; a specific deadline with a reason; and a follow-up that always adds something new.
Try Corodomo: Learn languages · Learn via Video · Exam practice