Multilingual meetings

How to run a client call when nobody shares a first language

A practical way to run a client call when nobody shares a first language, from the agenda you send a day before to the notes you send after.

Key takeaways

  • Decide the working language and the fallback before the call, not during it.
  • Send the agenda, the names and the numbers in writing a day ahead.
  • Slow the call down on purpose: one speaker at a time, short turns, a recap after each topic.
  • Send written notes in every participant's language the same day.

To run a client call when nobody shares a first language, agree one working language in advance, send the agenda and every name and number in writing, run the call one speaker at a time, and confirm decisions in writing the same day. The call itself is the smallest part. Most of the work happens before and after it.

This guide is for people who already know their client well enough to book the call, and who now have to make it work: an account manager in Milan with a client in Osaka, a project lead in Berlin with a supplier in São Paulo, a founder who meets customers in three countries.

Which language should the call run in?

Pick the working language before you send the invitation, and say why. Often it is the language in which the most people are comfortable, not the one in which the most important person is fluent. If one side works in their first language and the other in their third, the second group will say less, ask fewer questions and agree to things they have not fully understood.

Write the choice into the invitation: "We will speak English. Please write in your own language in the chat at any time and we will answer." Then name a fallback. If the call goes badly, what happens? A short follow-up in writing, a second call with an interpreter, or a call split into two shorter ones. Deciding this in advance means nobody has to admit defeat during the call.

What should you send before the call?

Send the agenda, the attendee list and a short list of names, numbers and terms at least a day ahead. Names of people, companies and products, amounts and dates, and any term of art are what listeners get wrong first, in any language, with or without software. Seen in writing beforehand, they are recognised on the call.

A useful pre-read has four parts:

  1. The goal of the call in one sentence.
  2. Three to five agenda items, each phrased as a question or a decision.
  3. A glossary of the ten or fewer terms that matter, with the spelling you want used.
  4. The figures you will discuss, written as digits and as words, with the currency named.

Ask the other side to do the same. A client who sends you their own terms list has just told you where the misunderstandings would have been.

How do you run the call itself?

Slow it down on purpose. Four habits do most of the work.

One speaker at a time. Ask the host to give the turn by name. When two people talk at once, a listener working in a second language usually loses both.

Short turns. Aim for a few sentences, then stop. Long monologues are hard to follow, hard to translate, and hard to remember.

Recap each topic. At the end of every agenda item, one person says in plain words what was decided and who does what. Then the others confirm. This is the single best protection against two sides leaving with different pictures of the same meeting.

Write the risky things down as you say them. Put names, amounts and dates in the chat while you speak. Nobody has to ask twice, and the chat becomes a first draft of the notes.

Ask people to say when they have not understood. This only works if the host sets the tone: "If anything is unclear, say so. It is much faster than finding out next week."

What if someone goes quiet?

Silence is not agreement. In a call where some people work in a second language, a quiet participant is often still processing the last point. Ask by name and make the question easy to answer: "Sofia, is the Thursday date workable for your team?" is easier than "Any thoughts?".

Offer a second channel. Some people write much better than they speak. Telling the group "you can also answer in the chat" gives them a way in without singling them out.

What do you send afterwards?

Send written notes the same day: decisions, actions with an owner and a date, and open questions. Keep sentences short and avoid idioms, because the notes will be read slowly and sometimes run through a translation tool.

If the participants do not share a language, send the notes in each person's own language. That is the part most teams skip, and it is the part that stops a misunderstanding from living for a week. Ask for a one-line reply from each person: "Confirmed" or "I read it differently". A missing reply is not a yes.

Then keep a record of what went wrong. If a name was misheard or a term was misunderstood, add it to the glossary for next time. After three or four calls, the glossary does more than any tool.

Where does software fit in?

Software can help in two places: live captions or live translation during the call, and translated notes after it. Treat both as aids, not as authority. Test any tool on your own people, in your own meeting conditions, before a client sees it, and keep the written recap as the safety net.

This is the problem we are working on at VocalSpan: a meeting room where everyone speaks their own language and hears the others in theirs, with the notes in your language afterwards. It is early software. We tested it in a remote Italian–English call on 23 October 2026, and we show it live in a 15-minute call, joined from your own device. If you want to see it on your kind of meeting, you can book one.

Frequently asked questions

Should I use a human interpreter or software?

For contracts, legal or medical content, use a qualified human interpreter. For routine client calls, software can help, but test it on your own audio first and keep a written recap as the safety net.

How long should a call across languages be?

Plan for more time than a same-language call, because every point is said, understood and confirmed. Fewer topics per call works better than a longer call.

Written by

Aayush Anupam

Founder, VocalSpan

Aayush Anupam is the founder of VocalSpan. Aayush builds and tests VocalSpan's live speech translation for client meetings and writes about what works when people meet across languages.