How to explain technical steps over the phone

Why do technical instructions go wrong over the phone?

Explaining technical steps over the phone is hard because the helper and the caller are looking at different things. The helper pictures the screen from memory or from their own device, while the caller sees a screen that may have a different software version, a different app version, larger text, a dark theme, or a pop-up the helper never expected. Every instruction is filtered through the caller's own description, and people describe screens in their own words: “the little wheel,” “the thing at the bottom,” “it says something about storage.” Small mismatches compound quickly. One misread instruction puts the caller on the wrong screen, the next instruction no longer makes sense, and both people start guessing. Good phone guidance closes that gap with a simple loop: tell the caller exactly what to look for, have them confirm what they see in their own words, and only then give the next step.

The fix is not talking slower or louder. It is structure: a known starting point, one action at a time, and a quick check after every step. Federal plain language guidance on digital.gov makes the same point for writing: express only one idea in each sentence, pick the familiar word over the obscure one, and substitute everyday language for jargon.

Seven techniques that make phone instructions work

1. Start from a place you both know

   First, get the caller to a screen you can picture. On a phone that is usually the Home Screen. On a computer, it is the desktop with other windows closed or minimized. Ask them to tell you when they are there.

2. Use landmarks, not menu paths

   Describe where something is (top right corner, bottom row, under the large photo), what it looks like (a blue button, a small gear icon), and the exact words on it. “Tap the blue button at the bottom that says Continue” beats “proceed to the next step.”

3. Give one instruction at a time

   Stack two or three steps into one sentence and the caller will remember the first and guess the rest. This is the most common mistake on phone calls. Say one action, wait for it to happen, then say the next.

4. Confirm before moving on

   After each step, ask a question that needs a real answer, such as “What does the top of the screen say now?” A yes to “Did that work?” tells you very little, because people say yes to keep things moving.

5. Have them read what they see

   Ask the caller to read the screen aloud, word for word, including headings, button labels and error messages. Their reading is the closest thing you have to seeing the screen yourself.

6. Drop the jargon

   Words like browser, cache, toggle, URL and drop-down are second nature to support staff and fuzzy to many callers. Describe the action and the thing instead: “tap the words Forgot password, just under the sign-in box” rather than “click the reset link.”

7. Recap at the end

   Finish by summarizing what changed and what to do if it happens again. If the fix had more than three steps, offer to send written steps by text or email.

Sample phrases to use, and what to avoid

How do you give directions on a screen you cannot see?

Landmark navigation borrows from giving driving directions: describe things the caller can spot, in an order they can follow. A good screen landmark has three parts. Position tells them where to look (top left, bottom row, just under the search box). Appearance tells them what it looks like (a blue button, a small picture of a gear, a red circle with a number). The label gives the exact words, said exactly as they appear on screen.

• Corners and edges are the easiest landmarks. Everyone can find the top right corner. Far fewer people can find “the settings menu.”
• Count when things sit in a row. “The third icon from the left in the bottom row” works better than describing a tiny picture.
• Borrow the caller's words once you learn them. If they call it “the wheel,” call it the wheel too.
• Expect differences. Phone models, app versions, text size and dark mode all change what the caller sees. If your landmark is not there, ask what is in that spot instead.

What should you do when the caller gets lost?

Getting lost is normal, and the recovery matters more than the mistake. Stop giving new instructions and work back to a screen you recognize.

1. Reassure them: “That's fine, this happens all the time.”
2. Ask them to read the top of the screen and any buttons they can see.
3. If you recognize the screen, give one step back toward the route you planned.
4. If you do not recognize it, return to the Home Screen or desktop and restart that part of the task.
5. If they get lost twice on the same step, stop describing and switch to seeing the screen.

How should you handle passwords and codes on the call?

Some steps should never pass through your ears. Ask the caller to type passwords, one-time verification codes, card numbers and Social Security numbers themselves, and do not ask them to read those aloud.

When should you switch to seeing the screen?

Talking someone through a task works well for short, familiar fixes. Seeing the screen is better in these situations:

• You have asked “what do you see now?” and still cannot picture the screen.
• The task crosses several apps, websites or settings screens.
• Their device, app version or language differs from what you know.
• The caller has low vision, hearing difficulty or limited tech experience, so describing the screen is itself hard work.

Options include a video call with screen sharing, FaceTime screen sharing between Apple devices, remote support software that lets a technician take control, and view-only tools built for phone support. GuidedView is one of the view-only options: you text or email a link during the call, the caller approves, and you watch their phone or computer screen in your browser while you keep talking. The caller still does all the tapping. For a wider look, see ways to see someone's phone screen and how to see a customer's screen during a phone call.