For a telehealth visit with no sound or video, check the selected microphone, speaker, and camera first. Then review the approved platform's permissions and connection status. If the visit still cannot proceed, follow your practice's authorized fallback workflow rather than switching to an unapproved application.
Technical problems are frustrating for both staff and patients. A short preparation routine can prevent avoidable delays, while a clear escalation plan keeps the team from improvising during an encounter.
Prepare the workstation before the first visit
Use the telehealth platform's test feature, if available, on the actual workstation and connection used for visits. Test with nonpatient content. Confirm that audio can be heard in both directions and that the camera produces a usable image.
Check lighting, seating, and privacy. Position the camera so patient records, whiteboards, and other people are not visible behind the clinician. Headphones may help prevent echo and improve privacy, but the selected audio device still needs to be verified.
Use a supported browser or application version. Have IT coordinate updates and compatibility checks rather than installing an unfamiliar extension because a popup suggests it.
Troubleshoot the symptom you actually have
1. The patient cannot hear the clinician
Check whether the microphone is muted in the telehealth application and on the headset itself. Confirm that the correct microphone is selected; a workstation may have several available inputs.
Speak briefly while observing the platform's audio indicator, if it provides one. If the microphone works in an approved local test but not in the visit, application or browser permissions may need attention.
2. The clinician cannot hear the patient
Confirm the selected speaker or headset and its volume. Check whether sound is being sent to a monitor, disconnected Bluetooth device, or other unintended output.
Ask the patient, in plain language, to check their mute control and volume. Work through one change at a time so they do not lose the session while navigating settings.
3. The camera is unavailable or shows a black image
Check for a physical camera shutter and confirm that the correct camera is selected. Close other video applications that may be using it, after saving work and ending those sessions.
Review operating-system and browser permissions for the approved application. Microsoft documents separate Windows camera controls for applications and desktop software. If settings are managed or unavailable, ask IT rather than attempting to bypass the restriction.
4. There is echo or feedback
Two devices joined to the same visit in one room can create feedback. Follow the platform's instructions to use one audio connection, and consider a supported headset. Ask whether another nearby device is also transmitting audio.
5. Video freezes or audio breaks up
Determine whether the problem affects one participant or both. Ask about connection changes and other high-bandwidth activity, such as large uploads, without requesting access to the patient's private network.
On the practice side, compare an approved wired connection where practical and ask IT to investigate recurring issues. Connection quality involves more than download speed; instability can interrupt a visit even when a speed test looks acceptable.
Give patients simple instructions before the appointment
Send platform-specific preparation instructions through your approved communication channel. Explain how to join, what device or browser is supported, how to test equipment, and which known phone number to call for help.
Offer instructions that patients can understand without technical vocabulary. Ask them to choose a private location and arrange any accessibility or language support they need. Do not ask patients to email passwords, authentication codes, or screenshots containing unnecessary health information.
Confirm the practice's process for identity verification and any consent or documentation requirements before the visit. Technical preparation does not replace those steps.
Plan an authorized fallback
An audio-only call or a rescheduled appointment may be appropriate in some circumstances, but clinical suitability, patient needs, applicable rules, payer policies, and practice procedures must guide that decision.
Do not assume that a failed video connection makes every alternative acceptable or reimbursable. Define who decides on the fallback and how staff document the change.
For urgent clinical concerns, follow your clinical escalation procedure. Troubleshooting should not delay necessary care.
Frequently asked questions
Should we use a different video app if ours fails?
Only if your practice has approved it for that use. Review the service, configuration, applicable agreements, and workflow before relying on it for patient visits.
Can a good speed test rule out connection problems?
No. A speed test is a snapshot. Intermittent Wi-Fi issues, congestion, and connection instability can still affect a session.
What should staff record for IT?
Record the time, workstation, platform, error, affected participant, and steps already tried. Avoid unnecessary patient details in ordinary support tickets.
Make telehealth preparation repeatable
Consolidated IT Solutions can help assess workstations, connectivity, and supported configurations for your telehealth workflow. Request an Assessment to address recurring technical interruptions.
Sources and further reading
Microsoft Support: Manage app permissions for a camera in Windows. https://support.microsoft.com/en-us/windows/privacy/manage-app-permissions-for-a-camera-in-windows
HHS Telehealth: Preparing for a video visit. https://telehealth.hhs.gov/patients/preparing-for-a-video-visit
Follow your telehealth vendor's current audio, video, browser, and connection requirements for product-specific instructions.