English for Phone and Video Calls

Open and identify the purpose

A strong opening answers three questions quickly: Who are you? Why are you calling? What should happen next? You do not need a ceremonial introduction. You need enough context that the other person can place the call.

For an outgoing phone call

Useful shape: name + organization or shared context + reason.

"Hi, this is Lena Ortiz from Northline. I'm calling about the delivery change for order 4182. Is now still a good time for a quick two-minute check?"

If the person does not know you, add one more identifying detail. If they do know you, cut it. "This is Lena" may be enough. The right amount of introduction depends on the relationship, not on a universal business-English rule.

For a video call

The meeting title and participant names may already provide some context, so your opening can spend more time on the purpose:

"Hi everyone. I'm Lena from operations. I'm here to confirm the revised delivery date and the two items we still need from purchasing."

If you join late, do not spend a minute apologizing. Re-enter with a short repair:

"Sorry I'm late. I've got the agenda open. Are we still on the delivery date, or have you moved to the invoice issue?"

Try this before your next call

Write only three prompts: identity / purpose / first question. Then say the opening twice without reading a full script. Your second version should be shorter than your first.

Check sound and names

Do the channel check early, before important details begin. "Can you hear me?" is useful, but it is not the only check you need. A call can be technically connected while one voice is too quiet, distorted, echoing, or cutting out.

For names, avoid pretending you understood when you did not. A short check is usually less awkward than using the wrong name for twenty minutes:

"Could you say your surname one more time?"
"Kowalski."
"Kowalski. Thanks. Am I saying that correctly?"

Ask for repetition precisely

On a call, "Sorry?" can work once. Repeating it five times gives the other person no clue about what failed. A better repair identifies the missing piece.

The bad-connection repair

Dev: "We can ship the replacement on Thursday, but the customs form needs—"
Maya: "Sorry, the line dropped after 'customs form needs'. Could you repeat just that part?"
Dev: "Sure. The customs form needs your tax number before we can ship."
Maya: "Got it: tax number before shipment. Thanks."

Maya does not ask Dev to restart the whole explanation. She marks the exact boundary: after "customs form needs". That reduces effort for both speakers and gets the missing information faster.

Choose the repair that matches the problem

• Audio gap: "I lost the last few words after 'Friday'. Could you repeat that part?"
• One unclear word: "Did you say 'renew' or 'remove'?"
• Too fast: "Could you say the reference number a little more slowly?"
• Meaning is unclear: "When you say 'final', do you mean approved internally or ready to send to the client?"

The last example is no longer mainly a call-mechanics problem; it is general clarification. For the broader skill of checking meaning, assumptions, and understanding, use How to Ask for Clarification in English Without Sounding Lost.

Phone-specific: you may need to name the connection itself: "The line is breaking up." Video-specific: you can name what you see: "Your video froze, and I missed the sentence after 'budget'." Do not blame the other person's English when the channel is the obvious problem.

Confirm numbers, dates, and spelling

Some information is cheap to misunderstand in conversation and expensive to get wrong later: prices, quantities, dates, times, addresses, names, email addresses, version numbers, and reference codes. Treat these as fragile details. Repeat them in a form that makes a mismatch easy to hear.

"Fifteen" versus "fifty"

A: "The minimum order is fifty units."
B: "Just to confirm: fifty, five-zero, not fifteen, one-five?"
A: "Correct. Five-zero."
B: "Perfect. Minimum order: fifty units."

You do not need to spell out every number this way. Use the extra confirmation when the cost of error is high or two forms are easy to confuse.

Spell an email without turning it into alphabet soup

Nora: "Can I send the file to you? What's the best email?"
Omar: "Sure. It's [email protected]."
Nora: "Let me check that: Omar dot Naji — N-A-J-I — at velora dot I-O?"
Omar: "Exactly."
Nora: "Great. I'll send it while we're still on the call."

If one letter is still unclear, use a word to disambiguate it: "That's P as in Paris." If your organization or industry has an approved spelling alphabet, use that. Do not assume one phonetic alphabet is universally required. Aviation, for example, uses a defined ICAO alphabet in specific radio-communication contexts; ordinary workplaces may use different conventions or none at all.

Dates need a second dimension

"Next Friday" can become surprisingly expensive across countries, calendars, and time zones. Add the calendar date when it matters:

"So that's Friday, 28 August, at 10 a.m. Berlin time — correct?"

For a deadline, confirm both what is due and when: "You need the signed PDF by 5 p.m. on Tuesday, not the full report. Correct?"

Put someone on hold or transfer

Hold and transfer language has two jobs: explain what you are about to do and stop the other person wondering whether the call died.

Before a hold

"I need to check that order number in our system. Would you mind holding for a moment while I look it up?"

If you expect a longer wait, give the person a choice instead of trapping them in silence:

"This may take a few minutes. Would you prefer to hold, or should I call you back once I have the answer?"

Before a transfer

"Priya handles the contract side. I can transfer you to her. Before I do, would you like me to give her the two-minute summary so you don't have to start again?"

Only promise a warm handoff (a handoff with context) if you can actually do it. Some systems support consultation before transfer; others do not, and permissions or call type may change what is available. Microsoft Teams, for example, currently documents both direct transfer and a "consult" flow for supported one-to-one calls.

Video calls are different

In a normal video meeting, "I'll put you on hold" may sound strange unless you are actually using a hold function. More often, you are pausing the conversation or bringing someone else in:

• "Give me one moment while I message Arjun and see if he can join."
• "Could we hold that question for two minutes? I want Nina to hear it when she joins."
• "I'm going to add Sam to the call. I'll quickly tell him where we are when he joins."

Narrate a screen share

Screen sharing creates a new problem: you know exactly where you are looking, but the other person may be staring at a different tab, a loading screen, a tiny window, or the wrong part of the page. Narration turns your private cursor movement into shared context.

Use announce → confirm → locate → act

"I'm sharing the browser window now. Can you see the dashboard?"
"Yes."
"Great. I'm in the top-right corner under 'Billing'. I'm opening the August invoice now. The line I want to check is the second item, 'Implementation support'."

Do not race three steps ahead while the share is still loading. Microsoft Teams and Zoom both document screen-sharing controls, but the exact behavior, available share types, permissions, and audio options vary by app, account, device, and setup.

When the share fails

"It looks as if the share didn't start on your side. I'll stop and try the window again. Tell me when you can see the invoice."

That sentence does three useful things: names the problem, says what you will do, and gives the other person a clear signal for when to continue.

Recover after interruption or lag

Not every interruption is rude. On calls, people overlap because they cannot see a speaker taking a breath, because video arrives late, or because both people think the other has finished. Your job is to repair the floor quickly instead of turning the overlap into a politeness crisis.

If you both start speaking

• "Sorry, we started at the same time. You go ahead."
• "Go ahead — I'll come back to my point after."
• "I think there's a little delay. Finish your thought, then I'll jump in."

If the channel cuts a sentence

Phone: "I think the line cut out. I heard 'we can approve it if...' and then lost you."

Video: "You froze for a second. I heard up to 'the client approved the design'. What came after that?"

If you were interrupted and need your point back

"No problem. Coming back to the deadline for one second: I still need to confirm who owns the final check."

That is often better than "As I was saying...", which can sound annoyed in some contexts. If your real difficulty is entering a group discussion, holding the floor, or making a compact meeting contribution, use How to Speak Up in English Meetings. This W04 guide stays focused on call-specific lag, audio loss, and mixed spoken-digital timing.

Close with decisions and next steps

A call can feel smooth and still fail if everyone leaves with a different version of the decision. The close is where you convert conversation into an explicit shared state.

Use decision → owner → date → final check

Elena: "Before we finish, let me check the three actions. I'll send the revised quote by 3 p.m. Thursday. You'll confirm the quantity Friday morning. The Monday delivery date stays unchanged. Is that all correct?"
Marcus: "Yes, that's right."
Elena: "Great. I'll put those three points in a short email now. Thanks, Marcus."

That is the concise close: no replay of the whole meeting, just the decisions that someone could later misunderstand.

If something is still open, say so instead of smoothing it into a fake agreement:

"We haven't decided the launch date yet. Sofia will check engineering capacity and reply by noon tomorrow. Everything else is agreed."

Use the other person's confirmation as a test

"Does that sound right?" is better than assuming silence means agreement. For high-stakes details, ask for a specific confirmation: "Can I confirm that you own the final approval?" or "Is Thursday the committed date, or still the target date?"

When the call is part of customer support, sales, complaints, or de-escalation, the language around promises, remedies, escalation, and customer emotion becomes a different job. Use English Speaking for Customer Service and Sales for that owner. This page does not teach support policy or de-escalation.

Voicemail and follow-up

A useful voicemail is not a spoken email. Give the listener enough information to decide what to do without replaying a two-minute monologue.

Use name → reason → action → contact

"Hi Ana, this is Daniel Cho from Merrow. I'm calling about tomorrow's supplier call. We need to move it from 11 to 11:30. Please let me know if that still works for you. You can call me back on the number in my email, or just reply there. Thanks."

If you need to leave a phone number, say it once at a natural pace and repeat it in chunks if the system gives no written caller information. If you are not sure what information the recipient can already see, do not make assumptions about the voicemail platform.

Follow up with the smallest useful written record

Subject: Thursday call — agreed next steps

Thanks for the call. We agreed that I will send the revised quote by 3 p.m. Thursday, you will confirm quantity Friday morning, and Monday's delivery date remains unchanged. The launch date is still open; Sofia will confirm that separately.

The written follow-up should preserve the decision, not transcribe the conversation.

An eight-minute call practice routine

1. Pick one real scenario: supplier delay, project handoff, interview scheduling, invoice question, or internal update.
2. Choose two fragile details: one number/date and one name/email/reference code.
3. Open in 30 seconds: identity, purpose, first question.
4. Inject one channel problem: pretend you lost five words, heard an ambiguous number, or cannot see the shared screen. Repair it precisely.
5. Add one handoff: place the imaginary caller on hold, transfer the issue, or bring a colleague into a video call using language that matches the action.
6. Close in 20 seconds: decision, owner, date, final check.

Repeat the same scenario once. On the second pass, do not add more phrases. Make the repair and the close shorter.