Bad audio turns ordinary telehealth calls into accuracy problems. A patient joins from a car. A clinician uses a laptop microphone across the room. A family member talks from the kitchen. The line clips every time someone raises their voice.
The interpreter cannot fix every device. You can protect the interpretation by naming the audio problem early, asking for workable changes, and refusing to guess when the sound fails.
This guide is for interpreter education. It is not medical advice.
HHS provides context for audio-only telehealth in healthcare settings.
Bad audio is not background noise for interpreters. It is missing source text.
Say something before accuracy suffers
Do not wait until you miss a medication name or discharge instruction. If the audio is poor, intervene early.
TIP
Name the audio problem specifically: cutout, echo, background speech, distance from microphone, or overlapping speakers.
Use plain scripts:
- “Interpreter is having difficulty hearing the speaker. Please move closer to the microphone.”
- “Interpreter requests one speaker at a time.”
- “Interpreter requests that the speaker repeat the last sentence because the audio cut out.”
- “Interpreter hears background noise and may need repetition for accuracy.”
Keep the intervention short. Then return to the call.
You are not being difficult. You are preserving the message.
Identify the audio problem
Different problems need different requests.
| Problem | Request |
|---|---|
| Speaker far from microphone | ”Please move closer to the device.” |
| Background noise | ”Please reduce background noise if possible.” |
| Two speakers talking | ”Please speak one at a time.” |
| Audio cutting out | ”The audio is cutting out. Please repeat from…” |
| Echo | ”Interpreter hears echo. Please check whether two devices are open.” |
| Masked or muffled speech | ”Please speak slower and toward the microphone.” |
Do not diagnose the technology. State what you hear and ask for the change that supports accuracy.
Slow down high-risk details
Bad audio matters most during:
- medication names
- dosage instructions
- allergies
- phone numbers
- addresses
- dates
- warning signs
- consent language
- follow-up instructions
When one of those appears, slow the call if needed. “Interpreter requests repetition of the dosage” is better than carrying a half-heard number forward.
For medication-heavy calls, see medication reconciliation calls for OPI interpreters. For discharge instructions, see ER discharge calls for interpreters.
Manage family voices
Telehealth calls may include a patient, clinician, family member, caregiver, and interpreter. Sometimes the family member stands closer to the phone than the patient. Sometimes they answer for the patient. Sometimes they speak over the clinician.
Interpret what speakers say, and ask for turn-taking when overlap blocks accuracy:
- “Interpreter requests one speaker at a time.”
- “Interpreter could not hear the patient because another speaker was talking.”
- “Interpreter requests that the question be repeated to the patient.”
Follow your professional and agency protocols when family members take over. Do not police the call. Do protect audibility.
Use visual context if the platform gives it
In video visits, visual cues can help you understand who is speaking, whether the patient is pointing to a medication bottle, or whether the clinician is showing instructions.
Still, do not interpret what you cannot hear. If the patient holds up a bottle and the clinician reads the label, interpret the clinician’s words. If no one says the medication name out loud and the label is unreadable, ask for clarification.
Video helps. It does not replace speech.
Keep tools close, but do not hide the audio issue
Live transcripts, captions, Quick Lookup, and domain settings can help during rough audio. A transcript may catch a word you missed. Custom vocabulary may help a medication name appear correctly.
Tools do not remove the need to intervene.
If the audio cuts out, the transcript may cut out too. If two speakers overlap, captions may merge them. If the microphone distorts a number, the screen can show a confident wrong answer.
Use tools as backup. Use clarification as the safety step.
Document only according to policy
Some agencies ask interpreters to report technical problems. Some platforms have call-quality tags. Follow the workflow you were given.
In your own private notes, do not store patient details. If you track patterns for self-improvement, keep them generic:
- “telehealth, laptop mic, needed three repetitions”
- “pharmacy call, patient in car, dosage repeated”
- “video visit, family overlap”
That kind of note can help you prepare scripts without retaining protected information. Review HIPAA for interpreters if you work healthcare calls from home.
A calm audio script set
Keep these ready:
For distance: “Interpreter is having trouble hearing. Please move closer to the microphone.”
For overlap: “Interpreter requests one speaker at a time for accuracy.”
For cutout: “Interpreter lost audio after ‘[last heard phrase].’ Please repeat from there.”
For noise: “Interpreter hears background noise. Please repeat the medication name.”
For speed: “Interpreter requests a slower pace for the instructions.”
You can adapt the words to your agency style. The core is direct and neutral.
The goal is accuracy, not perfect audio
Telehealth audio will not always sound clean. Some patients have old phones. Some clinics use shared rooms. Some calls happen during pain, stress, or confusion.
You can still protect the call. Name the barrier. Ask for one change. Clarify high-risk details. Keep your tools close. Refuse to guess.
Bad audio is part of remote interpreting. Guessing does not have to be.
Related reading: