To learn English for emails quickly, learn the words that make a message easy to act on: confirm, request, review, attach, clarify, approve, pending and follow up. A good professional email does not need complicated vocabulary. It needs a clear subject, the reason for writing, accurate facts, one understandable request or update, and an appropriate ending.
If you searched for how to write emails in English, professional email phrases, business email vocabulary, email examples for work, polite English email phrases, or how to write a follow-up email, this guide provides sixty reusable expressions, original model emails, tone comparisons, grammar repairs, privacy guidance, a seven-day learning plan and a test. It focuses on actual email actions and clarity, complementing broader business English and formal-versus-informal language guides.
Quick answer — an email in five parts: (1) Subject: name the specific topic. (2) Greeting: use a suitable recipient’s name or a neutral greeting. (3) Purpose: state why you are writing in the opening lines. (4) Action and facts: give the necessary details and any real deadline or request. (5) Close: identify the next step and sign off appropriately. Never say you attached, confirmed or approved something that has not actually happened.
Why emails need a different vocabulary method
Emails are often read quickly, forwarded, searched and used as records. A sentence such as “The report is ready” may influence another person’s action, so the difference between draft, reviewed, approved and published matters. Friendly wording cannot repair an inaccurate status.
Email writing also requires more than choosing formal synonyms. A sentence can sound polite yet be ambiguous: “Please do the needful as soon as possible.” It does not identify the action or deadline. “Could you check the invoice total and send any correction by the agreed date?” tells the reader what to do.
The British Council English for Emails course covers addresses, starting and finishing messages, arrangements, enquiries, organising writing, proofreading and etiquette. These functions are a useful framework for learning practical email vocabulary instead of memorising isolated words.
Sixty useful English email phrases and terms with examples
The expressions below are original examples grouped by purpose, not a statistical popularity ranking. Some are suitable for neutral business messages; some are more formal. The best choice depends on the reader, relationship and stakes. Avoid sharing confidential details in a public message, regardless of which phrase sounds polite.
1. Subject lines and clear purpose
- 1. Meeting confirmation — state a clear email purpose in a subject. Subject: Meeting confirmation — Thursday 12 November
- 2. Request for information — identify an enquiry. Subject: Request for information about the service
- 3. Follow-up on … — identify an existing conversation. Subject: Follow-up on the revised timetable
- 4. Action required: … — label a real requested action without false urgency. Subject: Action required: confirm delivery address
- 5. For your review: … — send something for examination. Subject: For your review: updated report
- 6. Update on … — identify a progress message. Subject: Update on the pending request
A subject line should help the reader recognise the purpose without opening the message. “Update” is often too vague; “Update on the Thursday meeting” is more informative. Action required should be used only when the recipient genuinely needs to act. False urgency can damage trust, and a subject line should not reveal sensitive personal details in a context where other people may see it.
2. Opening an email
- 7. Hello [name], — use a neutral greeting. Hello Ms Lee,
- 8. Dear [name], — use a more formal greeting. Dear Dr Tan,
- 9. I hope you’re well. — use an optional courteous opener. I hope you’re well. I’m writing about our meeting.
- 10. I’m writing to confirm … — state a confirmation purpose. I’m writing to confirm the agreed time.
- 11. I’m contacting you about … — introduce the topic. I’m contacting you about the invoice.
- 12. Thank you for your message. — acknowledge previous contact. Thank you for your message about the schedule.
An opening is useful when it identifies the reader and explains why the message matters. “Hello” works in many professional relationships; “Dear” may be preferable for formal correspondence. A phrase such as “I hope you’re well” is optional, not a substitute for a clear purpose. In many situations, a concise “I’m writing to confirm …” is the most helpful first sentence.
3. Making requests without ambiguity
- 13. Could you please …? — make a courteous request. Could you please review the attached draft?
- 14. Would you be able to …? — ask whether an action is possible. Would you be able to confirm the venue?
- 15. Please let me know … — request information. Please let me know whether Thursday works.
- 16. Could you clarify …? — remove an ambiguity. Could you clarify the final delivery charge?
- 17. I would appreciate … — express a courteous request or gratitude. I would appreciate confirmation of the date.
- 18. Would you mind …? — make a polite request with -ing. Would you mind checking the figures again?
A request should identify what, why when needed, and when if a legitimate deadline exists. “Please review this soon” is less useful than “Could you review the draft by the agreed deadline?” Do not add a made-up date to create pressure. “Would you mind checking …?” normally takes an -ing form, while “Could you check …?” uses the base verb.
4. Discussing timing and arrangements
- 19. Could we arrange a call? — propose a discussion. Could we arrange a short call next week?
- 20. Would Thursday work for you? — offer a time. Would Thursday afternoon work for you?
- 21. The proposed time is … — identify an unconfirmed suggestion. The proposed time is 3 pm on Thursday.
- 22. The agreed deadline is … — record a genuinely agreed due date. The agreed deadline is Friday at 5 pm.
- 23. This date is provisional. — mark an unconfirmed plan. Please note that this date is provisional.
- 24. Please confirm your time zone. — avoid remote scheduling confusion. Please confirm your time zone before we schedule the call.
The words proposed, agreed, confirmed and provisional have different meanings. A proposed meeting time is not booked merely because one person suggested it. If the message is being read in another country, an exact date, clock time and time zone reduce ambiguity. Do not rely on “tomorrow afternoon” for an international meeting unless context is certain.
5. Attachments, links and documents
- 25. I’ve attached … — identify a real attachment. I’ve attached the revised report.
- 26. Please find attached … — use a conventional formal phrase. Please find attached the agenda.
- 27. Here is the link to … — identify a resource. Here is the link to the approved document.
- 28. Could you review the latest version? — request use of the correct document. Could you review the latest version of the draft?
- 29. I’ve highlighted the changes. — guide review to edited material. I’ve highlighted the changes in the file.
- 30. Please check you have access. — request a permission check. Please check that you have access to the shared folder.
An email should say “I’ve attached the report” only if the file is actually attached. A link is not an attachment, and access permission may be missing. File version names matter: the latest draft may not be the approved final document. Never send confidential records to a guessed address simply because the sentence is phrased politely.
6. Updates, decisions and uncertainty
- 31. The request has been received. — report receipt without implying approval. The request has been received and is awaiting review.
- 32. The review is in progress. — report unfinished work. The review is in progress.
- 33. The decision is pending. — state that a decision remains open. The decision is pending approval.
- 34. The proposal has been approved. — state authorisation only when verified. The proposal has been approved by the relevant team.
- 35. I don’t have a confirmed figure yet. — acknowledge uncertainty. I don’t have a confirmed figure yet, so I won’t guess.
- 36. I’ll check the source first. — describe verification before a claim. I’ll check the original source before sharing the number.
A request received is not a request approved. A review in progress has not been completed. “No confirmed figure” is a truthful limitation and may be better than an invented answer. Avoid promising that someone else will approve a proposal or that a deadline is guaranteed unless the responsible authority has confirmed it.
7. Explaining a problem or correction
- 37. I noticed a discrepancy. — raise a specific difference. I noticed a discrepancy between the quote and invoice.
- 38. There appears to be an error. — flag a possible mistake. There appears to be an error in the date.
- 39. The earlier version was incorrect. — acknowledge a verified error. The earlier version was incorrect; the updated figure is shown below.
- 40. Please disregard the previous attachment. — correct a document reference. Please disregard the previous attachment and use the corrected file.
- 41. I apologise for the confusion. — offer an appropriate apology. I apologise for the confusion caused by my earlier message.
- 42. Could you confirm the correction? — ask the reader to check. Could you confirm that the corrected date is accurate?
When correcting an email, identify the precise difference and supply the corrected information. A message can be apologetic and clear: “The earlier date was incorrect. The confirmed date is Friday, 13 November.” If you have not verified the new date, say that instead. A professional correction should not hide the factual change behind vague regret.
8. Replies, follow-ups and boundaries
- 43. Thank you for the update. — acknowledge new information. Thank you for the update on the request.
- 44. I’m following up on … — refer to an earlier contact. I’m following up on the case submitted last week.
- 45. Could you share the current status? — ask for progress. Could you share the current status of the review?
- 46. I won’t be able to attend. — decline an event. I won’t be able to attend Thursday’s meeting.
- 47. That falls outside my role. — describe a boundary accurately. That falls outside my role, so I’ll direct the question to the right team.
- 48. I would prefer to discuss this privately. — request a more suitable channel. I would prefer to discuss this privately rather than in a group thread.
A follow-up refers to a specific earlier message, reference or commitment. It should ask for the actual current status instead of assuming a person ignored the first message. Professional boundaries can be expressed without accusation: “That decision belongs to the approvals team.” A private issue should be moved to a suitable secure channel rather than handled in an unnecessary group thread.
9. Closing and next steps
- 49. The next step is … — give the reader a specific action. The next step is to verify the totals.
- 50. Please reply by … — state a real deadline. Please reply by Friday at 4 pm if that is the agreed deadline.
- 51. Let me know if anything is unclear. — invite clarification. Let me know if any part of the instructions is unclear.
- 52. Thank you for your time. — close courteously. Thank you for your time and assistance.
- 53. Kind regards, — use a common neutral-professional closing. Kind regards, Maya
- 54. Best wishes, — use a warm closing where appropriate. Best wishes, Daniel
The closing should tell the reader whether anything remains to be done. “The next step is …” makes action explicit, and “Kind regards” is a common professional sign-off. Reply by Friday is a real deadline only if it reflects an actual requirement. The number of lines in a message matters less than whether the reader can identify purpose and action.
10. Recipients, privacy and safe email habits
- 55. To: — identify the main recipient field. Put the intended primary recipient in the To field.
- 56. Cc: — identify visible copy recipients. Use Cc for people who should receive a visible copy.
- 57. Bcc: — identify a blind-copy recipient field. Use Bcc carefully when its function suits the message.
- 58. Reply — respond to the sender or applicable addressees. Use Reply when only the sender needs your answer.
- 59. Reply all — respond to all relevant visible recipients. Check whether Reply all is necessary before using it.
- 60. Verify the recipient address. — check before sharing information. Verify the recipient address before sending a private document.
To, Cc and Bcc are not interchangeable recipient fields. Cc normally shows copied recipients to other recipients, whereas Bcc hides a blind-copy recipient from the other recipient lists in normal email operation. Reply all can disclose a response to people who do not need it, and email threads may be forwarded. For confidential or sensitive details, follow the organisation’s verified secure-communications process.
How to write a professional email in five steps
First, decide the job of the message. Are you asking a question, sharing information, reporting a problem, asking for approval or confirming a plan? Write that job in one short sentence. If you cannot explain why the recipient needs to read the email, consider whether the message has a clear purpose.
Second, give the email a specific subject. “Request to confirm the revised meeting time” helps more than “Important”. Avoid making every ordinary email “URGENT”. For a private topic, the subject should be informative without revealing confidential details to anyone who might see an inbox preview.
Third, state the main point immediately. The first paragraph should answer: “Why am I being contacted?” You can follow with the necessary facts, but do not make the recipient read three screens before discovering what you need.
Fourth, ask for an action or explain the status. A request may need a document, decision, date or clarification. A status update should state what is complete, what remains pending and who has the next action. Include only verified information.
Fifth, close courteously. “Thank you for your time” or “Kind regards” is sufficient in many professional contexts. A closing does not need to repeat the whole message.
These principles help everyday workplace communication as well as enquiries, customer support and project updates.
Email 1: requesting information clearly
Subject: Enquiry about the appointment process
Hello,
I’m writing to ask about the process for arranging an appointment with your service. Could you let me know which details are required, whether an online booking option is available, and where I can find the official terms?
I would appreciate a link to the relevant information so I can check the requirements before submitting a request.
Thank you for your assistance.
Kind regards, [Name]
This is an original template. It does not suggest the provider actually offers online booking. It asks a specific set of questions and requests a reliable source. Replace the recipient and details with the real situation.
Vocabulary to notice
I’m writing to ask names the purpose; could you let me know introduces a request; whether expresses a question with alternatives; official terms identifies the source to verify; before submitting specifies sequence.
The writer does not say “Please confirm my appointment” because no appointment has been made. Email vocabulary should preserve the actual stage of the process.
Email 2: confirming a meeting after agreement
Subject: Confirmation — Project review on Thursday, 12 November
Hello Maya,
Thank you for agreeing to the project review. I’m writing to confirm the details we discussed: Thursday, 12 November, at 3 pm Singapore time, using the agreed video meeting link.
The agenda is to review the revised draft, identify outstanding questions and confirm which decisions require approval.
Please let me know if any of these details differ from your understanding. I’ll share the final agenda once it has been reviewed.
Kind regards, Daniel
The names, date and meeting are fictional. Notice that the message confirms only what was agreed. The agenda is not described as final if it still needs review.
A real cross-border meeting should identify the date, clock time, time zone and venue or conference link. “Tomorrow at three” may be ambiguous when recipients live in different locations or read the email later.
Email 3: requesting a review without implying approval
Subject: For review — Revised invoice summary
Hello team,
I’ve attached the revised invoice summary for review. The total in the first draft did not match the individual line items, so the figures have been checked and updated.
Could you review the attached version and confirm whether any corrections are still needed? The document has not yet been approved, so please do not treat it as final.
Thank you for your help.
Kind regards, Mira
The example assumes a fictional attachment. If you copy it into a real email, check that the file is genuinely attached, the figures are accurate and the review status is correct.
Review means examine; approve means authorise. They are not interchangeable. A project may be reviewed several times before approval. Saying “ready for review” is more truthful than “ready to publish” when authorisation is missing.
Email 4: a polite follow-up
Subject: Follow-up — Request submitted on 3 November
Hello,
I’m following up on the request I submitted on 3 November concerning the delivery details. I have not yet received a confirmed update.
Could you let me know the current status, whether any additional information is needed from me, and what the next step will be?
Thank you for your time.
Kind regards, [Name]
A good follow-up contains a relevant date or reference and a clear request. It does not assume that the recipient deliberately ignored the previous message.
If you have a specific case number, include it through the appropriate secure process. Avoid forwarding private identification documents in a long group email simply to prove you followed up earlier.
Email 5: correcting an earlier message
Subject: Correction — Meeting time in my previous email
Hello everyone,
I need to correct the meeting time stated in my earlier email. I previously wrote 2 pm; the confirmed time is 3 pm Singapore time on Thursday, 12 November.
I apologise for the confusion. Please use the corrected time and disregard the earlier time reference.
Thank you, [Name]
This model is fictional. The wording is useful because it identifies old information, correct information, the relevant date and time zone, and what readers should now do.
When a correction concerns money, safety or a contract, it may require more than a simple email. Follow the actual organisation’s correction and approval procedures. Email language helps communicate the repair; it does not authorise a change.
Email 6: declining a request respectfully
Subject: Re: Invitation to the project meeting
Hello Amira,
Thank you for inviting me to the meeting. Unfortunately, I won’t be able to attend at the proposed time.
If it would be helpful, I can review the agenda afterward through the usual team process. Please let me know which next step would be most useful.
Best wishes, [Name]
This example does not invent a reason for the absence or promise that the meeting will be moved. A respectful decline can be short. Do not imply that someone else has agreed to take your place without checking.
How to make English email requests more precise
A request has several parts: action, object, deadline when real, and purpose when needed.
Weak: “Please send the thing ASAP.”
Better: “Could you send the revised invoice summary through the approved channel?”
More specific, if a deadline is agreed: “Could you send the revised invoice summary by 4 pm on Friday, 13 November, Singapore time?”
A date and time should not be added merely to make a template look complete. The actual sender must verify the deadline and use the correct recipient’s time zone.
If the request is complex, use a short list with one action per item rather than a dense paragraph that hides several demands. For example, ask the recipient to check figures, highlight discrepancies and confirm the status separately.
Six high-value request verbs
Confirm — verify that information is correct or agreed.
Clarify — remove uncertainty about wording or meaning.
Review — examine material.
Approve — authorise a decision.
Provide — supply a document or information.
Update — communicate new or changed information.
Choose the verb for the real action. A recipient cannot approve something if they have no authority, and a sender should not call a document confirmed if only one person proposed it.
Formal versus informal email English
A friend might receive “Hey, can you send the file?” while a new business contact might receive “Hello, could you send me the document, please?” Both can be natural. Formality is a matter of relationship, conventions and purpose, not a contest to use the longest word.
Contractions such as I’m, we’ve, don’t and I’ll are common in many neutral professional emails. Some legal or highly formal documents may prefer fully written forms. A good tone remains human and clear.
Avoid corporate language that obscures action. “Kindly expedite the necessary operational modalities” is usually less helpful than “Please confirm who will complete the review and by when.”
For a dedicated register comparison, visit Formal and Informal English Phrases. This article focuses specifically on email structure and reader actions.
To, Cc, Bcc and Reply all: practical email terms
The To field normally identifies the primary addressee. Cc means carbon copy and normally makes copied recipients visible to the other recipients. Bcc means blind carbon copy and normally hides those addresses from other recipients’ header lists.
A sender should not treat Bcc as a guarantee of complete confidentiality: a blind-copied person can still forward the message or reveal it, and different systems have their own behaviour. Consider whether it is appropriate to send the email at all.
Reply often addresses the sender, while Reply all includes the visible relevant recipients according to the mail programme. Before choosing Reply all, check whether everyone needs the answer. A message with private documents or a sensitive response should use the suitable approved channel.
Forward sends an existing message or content to another person. Do not assume you have permission to forward confidential correspondence. The email interface may make forwarding technically easy even when sharing the information is inappropriate.
Attachments and links: the language of document sharing
“I’ve attached the report” means the attachment is genuinely present. If you provide a link instead, say “Here is the link to the report.” These are not synonyms.
A shared link may have permissions that prevent access. A reader might reply “I can’t open the file.” A helpful response is: “Thank you for letting me know. I’ll check the approved sharing permissions and send an appropriate link.”
Be mindful of document versions: draft, revised draft, approved version, final copy, and superseded version describe different stages. A file called final-v3 may still be unapproved. The true status should come from the actual workflow, not a filename.
Before sharing, check the recipient address, file contents, access permissions and whether the document contains private information. Use an approved secure method when data is sensitive.
Replying to uncertainty without making false promises
Suppose someone asks “Has the refund been approved?” but you only know that the request was received. A helpful response is: “The request has been received, but I cannot confirm approval yet. The relevant team is reviewing it.”
The word pending can make the status clear, but explain what is pending. “Pending” alone might refer to payment settlement, a manager’s decision or a document review.
You can also say: “I don’t have a verified completion date yet.” That is more useful than inventing “It will definitely be finished tomorrow.”
A professional email should distinguish what happened, what is expected, what is requested, and what remains unknown. Vocabulary can help readers make that distinction.
Keeping emails readable on a small screen
Many recipients read email on a phone. Long paragraphs with several requests may be difficult to scan. Begin with the main purpose, use short paragraphs, and make the requested action visible.
An efficient update might contain:
- Status: “The document has been reviewed but is not yet approved.”
- Issue: “One figure still needs verification.”
- Action: “Could you confirm the correct number?”
- Timing: “We will update the schedule after the figure is verified.”
- Contact: “Please reply through this thread if anything is unclear.”
These are examples of structure, not formatting that every organisation must use. A simple personal message may need only two sentences. Write for the reader’s needs rather than aiming for a minimum word count.
Email proofreading: five checks that catch real mistakes
1. Recipient: Is this the right person and address? Have you accidentally included unnecessary recipients in Cc or Reply all?
2. Purpose and action: Will the reader know exactly why you wrote and whether they need to reply?
3. Dates and numbers: Are the figures, units, full dates and time zones correct? Did fifteen accidentally become fifty?
4. Attachments and links: Does the referenced document exist, open correctly and have the right access permissions?
5. Status and tone: Are you calling a review “approved”? Are you using an unverified fact or a deadline you did not agree? Is the tone courteous without being vague?
The British Council’s English for Emails series includes units specifically focused on organising messages, proofreading and etiquette. These tasks are more useful than simply replacing everyday verbs with formal-sounding synonyms.
A 15-minute email vocabulary routine
Minutes 1–3: Choose one purpose, such as confirmation, enquiry, review, correction or follow-up.
Minutes 4–6: Learn five phrases that match the purpose. Identify the verb each uses and what it asks the reader to do.
Minutes 7–10: Write a short fictional email with a subject, purpose and action. Make sure the facts are explicitly hypothetical or accurately verified.
Minutes 11–13: Edit for brevity, grammar and status accuracy. Check that the language does not invent an attachment, decision or deadline.
Minutes 14–15: Hide the example and rewrite the email in a new scenario. Mark phrases you could not retrieve independently and review later.
This tests whether vocabulary is becoming flexible rather than merely familiar on the page.
Seven-day email writing learning plan
Day 1 — Subject and purpose: practise writing six useful subject lines and first sentences.
Day 2 — Requests: compare could you, would you mind, please confirm and I would appreciate. Make each request specific.
Day 3 — Dates: draft an appointment confirmation with an exact date, time and time zone. Do not treat a suggestion as an agreement.
Day 4 — Attachments: practise references to genuine attachments, links, file versions and access permissions.
Day 5 — Status: write accurate updates distinguishing received, in progress, pending, approved and completed.
Day 6 — Corrections and privacy: rewrite an email with an incorrect figure and check recipient fields. Do not share sensitive details in a mock group thread.
Day 7 — Transfer: draft a new professional message without a template. Check whether another reader can identify purpose, action, verified facts and next steps.
Twenty-question professional email vocabulary quiz
Cover the model answers and supply an appropriate phrase.
1. You need a meaningful subject for a review. → For your review: updated report. 2. You want to start a neutral email. → Hello [name], 3. You want to confirm a time. → I’m writing to confirm … 4. You need more information. → Could you please clarify …? 5. You want a courteous request. → Would you be able to …? 6. You are suggesting a meeting rather than confirming it. → The proposed time is … 7. The time is not final. → This date is provisional. 8. You have genuinely included a file. → I’ve attached … 9. You want someone to examine a draft. → Could you review the latest version? 10. A request arrived but isn’t approved. → The request has been received; approval is pending. 11. The team is still working. → The review is in progress. 12. You don’t know a verified figure. → I don’t have a confirmed figure yet. 13. You found a mismatch. → I noticed a discrepancy. 14. You are replacing a wrong file. → Please disregard the previous attachment. 15. You need to acknowledge an error. → I apologise for the confusion. 16. You are following up. → I’m following up on … 17. You want the latest status. → Could you share the current status? 18. You need the reader to act. → The next step is … 19. You need a professional closing. → Kind regards, 20. You want to avoid sending to unnecessary people. → Check To, Cc, Bcc and Reply all before sending.
The model answers are examples rather than unique correct solutions. Make your own version for a different email purpose without copying the original wording.
Common mistakes in business email English
- “Please advice” instead of “Please advise” when using the verb.
- “I attached the document” when there is no attachment.
- “The proposal is approved” when it has only been reviewed.
- “Revert back ASAP” when a clearer request is “Please reply by the agreed deadline.”
- “Please explain me” instead of “Please explain it to me.”
- “I wait your reply” instead of “I look forward to your reply” or “I’ll wait for your response.”
- A vague subject line: specify the document, task or request where appropriate.
- A made-up deadline: use only verified or agreed dates.
- Reply all by default: include only necessary recipients.
- Overly elaborate formal language: clear and courteous often beats long and obscure.
Frequently asked questions
### How do I write a professional email in English? Use a clear subject, suitable greeting, immediate purpose, relevant details, an understandable request or update and a courteous sign-off.
### What are the most useful business email phrases? “I’m writing to confirm”, “Could you clarify”, “Please let me know”, “I’ve attached”, “The review is pending”, and “The next step is” are widely useful.
### What’s a polite way to ask for a reply? “Could you let me know whether Thursday works?” or “I would appreciate your confirmation” can be natural, depending on the situation.
### Is ‘Dear’ required in every formal email? No. “Hello [name]” is common in many professional relationships; expectations vary by organisation and context.
### Can I use contractions in a work email? Often yes. “I’m writing to confirm” is natural in neutral professional English, though some highly formal settings prefer full forms.
### What does ‘Cc’ mean? A visible copy to additional recipients in ordinary email headers. It does not make the message private.
### What does ‘Bcc’ mean? A blind copy field that normally hides the recipient from other recipients’ displayed lists. It is not a complete security guarantee.
### Why should I avoid Reply all? It may expose your response to people who do not need it. Check the recipient list and the sensitivity of the content.
### What’s the difference between reviewed and approved? Reviewed means examined; approved means authorised. A reviewed document is not necessarily approved.
### How can I remember professional email phrases? Learn them by communication purpose, practise a new short email, hide your example and rewrite it after a gap.
Sources and related guides
The British Council English for Emails lessons cover greetings, email arrangements, enquiries, proofreading and etiquette, with interactive practice for A2–B1 learners. For email register, see Cambridge Dictionary’s Formal and Informal Language guide.
Continue with Formal and Informal English Phrases for register, Business English for Work for broader workplace language, and English for Phone Calls and Video Meetings for spoken follow-ups. The Vocabulary Learning Hub connects the wider series.
Start now: take one ordinary message and rewrite its subject and first two sentences so the reader immediately knows the purpose, the verified facts and the next action. That’s professional English that works.