Most "business English" guides hand you a wall of phrases and let you guess which ones to actually use. The real problem isn't memorizing phrases — it's matching the register to the moment. A phrase that's perfect in a Slack message can sound stiff in a presentation, and the same phrase pasted into a first-contact client email can sound rude in a chat with your teammate.
This guide gives you the highest-frequency phrases you'll need across five workplace scenarios — meetings, emails, calls, small talk, and presentations — sorted by register so you know exactly which one to reach for. Every section has a built-in test.
How professional English really works
There's no single "professional" register. There are three, and native speakers switch between them constantly:
| Register | When to use it | Example |
|---|---|---|
| Formal | First contact, external clients, written escalations, presentations to senior people | "I would like to follow up on..." |
| Neutral | Most internal communication — meetings, team emails, status updates | "I wanted to follow up on..." |
| Casual | Slack with teammates, hallway chat, 1:1s with peers | "Just following up on..." |
The trap most B1 learners fall into is defaulting to formal everywhere. It sounds like a translated textbook. Native colleagues read it as cold or distant.
The rule: mirror the register you receive. If a colleague writes "Quick q — can you send that file?", reply in kind. Don't escalate to "Dear Colleague, In response to your inquiry..."
In meetings: contribute, agree, disagree, interrupt
Four moves you'll make in 90% of meetings.
Making your point (without dominating)
Match each pair
Agreeing — with weight
"I agree" is fine but flat. To sound like you've actually thought about it:
- "That's a good point — I'd add that..."
- "Exactly, and the other piece is..."
- "I think you're right, especially because..."
Disagreeing — politely but clearly
This is where B1 speakers most often get stuck. The trick is to soften the disagreement, not the substance:
Never start with "No" or "You're wrong." Even native speakers don't.
Interrupting (without being rude)
Sorry to jump in, is the universal opener. Variants:
- "If I could just add something quickly..."
- "Quick clarification — ..."
- "Just to build on that..."
In emails: opening, requesting, following up, closing
Email is the single highest-frequency business-English surface. Get four building blocks right and you cover 95% of cases.
Openings (replace "Dear Sir/Madam")
| Situation | Use |
|---|---|
| Person you've never met (formal) | "Hello [Name]," or "Dear [Name]," |
| Internal colleague | "Hi [Name]," |
| Quick reply in a thread | (no greeting — straight to the answer) |
"Dear Sir/Madam" reads as outdated and impersonal in 2026 — use a name whenever you can find one.
Making a request
The polite-question structure native speakers actually use:
- "Could you send me the report by Friday?" (neutral — perfect default)
- "Would you be able to send..." (slightly more formal)
- "Can you send..." (casual — fine for teammates)
Try it: fill in the polite opener.
kindly forward the deck to the design team by Thursday?
Notice: the present perfect is often the right tense for "I've already done X, now over to you" emails. See present perfect vs past simple for why "I have attached the file" beats "I attached the file" in opening lines.
Following up
The follow-up email is its own art form. Native colleagues expect a clear ask, not a guilt trip:
- "Just following up on my note from Monday — any update?"
- "Wanted to circle back on this before EOW."
- "Bumping this in case it got buried."
Avoid "I am still waiting for your response" — it reads as passive-aggressive in English even if it's neutral in your first language.
Closings
Match each pair
On calls: starting, clarifying, ending
Phone and video calls collapse three problems into one: you can't see body language, you can't reread, and you can't pause. Memorize the openers and closers so you can spend your attention on the content.
Starting
- "Hi, this is [Name] from [Company] — is this a good time?"
- "Thanks for jumping on. Just to set context — ..."
- "Can everyone hear me okay?"
Clarifying — when you didn't catch something
This is the most useful skill on calls. Don't pretend you understood. Native speakers use these constantly:
- "Sorry, could you repeat that?"
- "Just to make sure I follow — you're saying...?"
- "Could you spell that for me?"
- "Sorry, my line cut out for a second."
Could you repeat that? — practice the falling intonation; it's a polite request, not a confused question.
Ending
- "Great, I think we've got what we need. Anything else?"
- "Thanks, let me circle back with the team and follow up by [day]."
- "Talk soon."
In small talk: starting and exiting professionally
Small talk at work is short. It's a verbal handshake, not a conversation. The biggest B1 mistake is treating "How's your week going?" as a real question. (See how to respond to "How are you?" for the underlying culture rule.)
Safe openers
- "How's your week going?"
- "Did you have a good weekend?"
- "Any plans for the long weekend?"
- "How's the project going?" (work-adjacent, low risk)
Safe responses
- "Pretty good, thanks — yours?"
- "Busy but good. You?"
- "Can't complain. How about you?"
Exiting gracefully
You need this more than the opener. Memorize one and use it every time:
- "Anyway, I should let you get back to it — good to chat."
- "I'll let you go. Catch you later."
- "I have a call in five — let's pick this up later."
In presentations: opening, transitions, handling questions
Presentation phrases are the most formulaic of the five scenarios — which is good news. Memorize one of each and you're set.
Opening
- "Thanks everyone for joining. Today I'll walk you through..."
- "Quick agenda: three things — first..., second..., and finally..."
Transitions
- "Moving on to..."
- "That brings me to..."
- "Building on that — ..."
Handling questions
When you don't know the answer:
- "That's a great question — I'll need to check and get back to you."
When the question is hostile:
- "I hear that concern. Let me address it head-on — ..."
When you didn't understand:
- "Could you rephrase that for me?"
Quick test: pick the right register
You receive this Slack message from a senior colleague you don't know well:
"Hey, quick one — can you share the Q2 numbers by EOD?"
Which reply is best?
Where to go from here
Phrases get you started. Real fluency comes from practicing them in scenarios until you stop translating in your head. If the register-switching above felt like work, that's your mental-translation loop — there's a deeper fix in how to stop translating in your head.
When you're ready to drill these in structured practice — with feedback on email tone, meeting interruptions, and call openers — the Business English curriculum walks you through every scenario with role-plays and AI conversation practice.