Phone and Video Calls | Business English

Handle a professional call without hiding behind a script

A useful call has a purpose, controlled turn-taking and a result both sides understand. This module moves through three pressure levels. You begin with a visible cue card, repair interruptions on a video call, then complete two unscripted client calls at the checkpoint.

Level: B1. The examples use software and freelance work because technical details are easy to misunderstand, but the call structure also works in sales, support, operations and internal teams.

The three-level call progression

Level	Lesson	What changes	Evidence
1: supported	Open, State, Confirm, Close	Use a four-move cue card, then remove half the cues.	One complete recorded call and a written action summary.
2: interrupted	Video Call Repair	Recover a missed version, number and date without pretending you heard them.	A repaired call and accurate follow-up message.
3: unscripted	Call Checkpoint	Respond to an interruption, objection and unexpected follow-up.	Two mock calls, two transcripts, four repairs and two follow-ups.

The call shape professionals can follow

Open: greet the person, check the time and name the desired outcome.
State: separate confirmed facts from assumptions, then explain the effect in plain English.
Confirm: restate the decision, owner, date and any condition.
Close: say when the written summary or next update will arrive.

Do not begin with architecture, logs or acronyms. A non-technical client first needs to know what changed, what they may notice, what remains safe and what happens next.

Natural client call phrase bank

Job	Useful phrase	Less useful version
Set the purpose	Before we start, the outcome I need today is a decision on the release date.	I want to discuss many things.
Clarify a word	When you say “ready”, do you mean tested or already live?	I think I understand.
Repair audio	I caught “API change” but missed the version number. Could you repeat that part?	Your voice was bad. Say it again.
Simplify a problem	The service stopped accepting new requests, but saved data is safe.	The upstream API returned repeated 503s.
Explain a delay	Testing found a checkout risk. I recommend Monday, and I will update you at 3 p.m.	There are some issues, so it may be late.
Handle an objection	We can keep the date or the added scope. Keeping both would increase risk.	That is impossible.
Close	To confirm: I own the fix, you approve the copy, and the next update is Thursday.	Okay, we will see.

Two mock calls to keep in your portfolio

Call 1: first client conversation

A client wants a small booking application. You need to understand the users, approval flow, deadline and what “finished” means. During the call, the client gives a vague answer and adds one new requirement. Ask focused questions, summarise the scope and confirm what you will send next.

Call 2: delivery risk

Regression testing found a checkout issue two days before release. The client wants the original date. Explain the confirmed impact, what remains unknown, the safest options and the next update time. Do not invent a root cause or promise a date you cannot support.

For both calls, keep only three cue words. Record the first attempt, transcribe the part that became unclear, write two repairs and record again. Audio stays on your device.

Score the call, not your confidence

Criterion	1: repair needed	2: usable	3: controlled
Purpose	The reason for the call is unclear.	The purpose appears after some background.	The desired outcome is clear near the opening.
Plain English	Jargon hides the effect.	Most technical detail is explained.	The client effect, safety and next step are easy to follow.
Repair	A missed fact is guessed or ignored.	The speaker asks for repetition.	The exact missing detail is recovered and confirmed.
Questions	The answer avoids or memorises.	The answer addresses the question.	The answer is accurate, concise and adapts to push-back.
Close	No owner or date is confirmed.	Most actions are clear.	Owner, action, date and next update are explicit.

Start or continue the module

Your progress is saved on this device only.

1Phone Calls in English: Open, State, Confirm, Close21 min, Not complete
2"Sorry, You Cut Out": Video Calls and Repair Phrases22 min, Not complete
3Checkpoint: Could a Colleague Follow Your Call?20 min, Not complete

When you are ready to continue

You do not need a perfect accent or a memorised performance. Continue when a listener can identify the purpose, facts, decision and next action, and when your second recording is measurably clearer than the first. The checkpoint records evidence on your device but never locks the next lesson.

Discussion

No comments yet. Add the first useful question or observation.

You must log in to post a comment.