Making Phone Calls When You Stutter

Ask a room of adults who stutter which situation they avoid most and the phone wins. Not presentations. Not dates. The phone: a two-minute call to a dentist that has been sitting on a list for three weeks.

This page is about that call. What happens before you dial, what to say in the first ten seconds, what to do when the line goes silent and you are stuck, and how to tell the difference between sending an email and hiding behind one.

Why the phone is harder than the room

It is not in your head, and it is not a confidence problem. The phone genuinely removes the things you use to manage a block.

There is no face. In a room you can see the other person waiting, and they can see you working. On a line, they see nothing. Your pause is indistinguishable from a bad connection.

Silence has a different meaning. In conversation, a pause is thinking. On the phone, a pause is a fault. The other person’s instinct after two seconds is “hello?” — which lands exactly when you are mid-block and least able to answer.

You cannot use your body. A lot of what gets you through a block in person is physical: a hand movement, a breath the other person can see, a shift in posture that says stay with me. None of it transmits.

The opening is fixed. Almost every call starts the same way, and that way includes your name. The single hardest word most people who stutter own is the one the phone demands in the first three seconds.

Knowing why it is harder matters, because it moves the problem. You are not failing at an easy thing. You are doing a genuinely harder version of something, with fewer tools.

Before you dial: the three-minute preparation

Three minutes, not thirty. Preparation that takes half an hour becomes another way to not make the call.

1. Write the first sentence. The exact words, including your name. Only the first sentence.
2. Read it aloud and mark the heavy words. Whatever feels loaded today. The list is different tomorrow, which is why you do this now rather than trusting memory.
3. Write a second route for each heavy word. “Appointment” becomes “a time to come in”. You are not building a permanent detour. You are making sure a block cannot end the sentence.
4. Say the whole thing aloud, three times. Out loud. Reading it in your head rehearses nothing, because the block does not live there.
5. Decide now what you will say if you block. One short line, chosen while you are calm.
6. Dial inside thirty seconds. Preparation has a shelf life. Waiting turns it back into dread.

The fifth step is the one people skip and the one that does the most work. A block is survivable. A block plus a scramble for words to explain the block is what turns thirty seconds into a bad afternoon.

A script for the first ten seconds

The opening carries almost all of the pressure, so it is worth engineering.

Put a word in front of your name. Blocks land hardest on the first sound of the first word of a turn. Give that slot to something disposable.

• Harder: “Sam speaking.”
• Easier: “Hi — it is Sam here.”

By the time your name arrives you are already producing sound, already moving, and the machinery is running. This is not a trick to hide anything. It is the same reason a runner does not start a race from a standstill in the blocks with cold legs.

Say why you are calling before you say anything complicated. “I am calling about an appointment” gives the other person a frame. A frame makes them patient, because they can now predict roughly where you are going and they stop listening for errors.

Slow the first line down more than feels natural. Not the whole call. The first line. The pace you set in the opening is the pace the other person matches, and it is much easier to speed up later than to slow down mid-call.

Have your reference numbers written in front of you. Strings of digits and postcodes are their own category of hard, and hunting for one while blocked is the worst combination available.

What to do when the line goes quiet and you are still blocked

You are three words in, stuck, and the other person has just said “hello?” twice. This is the moment everybody plans around and nobody plans for.

Do not hang up. It is the strongest urge in the situation and it is the one that costs most, because the call is still there tomorrow and now it has a bad memory attached.

Say the line you chose. “One second, I stutter sometimes.” Five words. Almost everyone responds well, because you have converted an alarming silence into an explained one. The other person’s job changes from diagnosing a problem to waiting, and people are much better at waiting.

Then stop pushing. A block is not a door that opens with force. Let the air go, let the tension in your jaw and chest drop, and start the word again gently — a soft first sound rather than a hard one. This is the technique a speech-language pathologist would call an easy onset, and the phone is where it earns its keep.

Do not apologise repeatedly. One acknowledgement is information. Four is an invitation for the other person to feel awkward, and their awkwardness comes straight back to you.

If you want the mechanics of releasing a block rather than forcing through it, the techniques section covers each one on its own page.

Automated menus, and the trick of pressing zero

Voice menus are a special case, and they are worth treating separately because they are not people. They have a timeout of about three seconds and no capacity to wait.

• Press zero. Many systems route to a human on zero at any point in the tree, whether or not they say so.
• Say nothing. Most systems escalate to a human after two failed prompts. Silence is a valid strategy and it is often the fastest one.
• Use the keypad whenever it is offered. “Or press 2” exists on most branches even when the recording emphasises the spoken option.
• Use the website or the chat first. For an automated system this is not avoidance. It is choosing a channel that works, in a situation where the other end is a machine that cannot adapt.

That last point has a limit, and the last section of this page is about where it sits.

Work calls, and what you owe your colleagues

Nothing. You owe your colleagues nothing.

You may still decide to tell them, because it is easier than not telling them. If you do, keep it short and do not make it a request for accommodation unless you actually want one:

“Quick thing — I stutter. If I go quiet on a call, I am still there. Just leave a gap.”

That is the whole disclosure. It takes four seconds, it explains the thing they were going to notice anyway, and it tells them exactly what to do, which is the part most people want and do not know how to ask for.

What tends not to work is a long explanation. Length signals that this is a big deal that requires management, and the reaction you get back will match. Short and matter-of-fact gets short and matter-of-fact in return.

If the call is one you are dreading specifically because of who is on it, that is a different problem from the phone itself, and living with a stutter at work is the better section for it. On the legal side, the National Stuttering Association covers workplace rights in the United States and STAMMA covers the UK, and both are better on that subject than we are.

Rehearsing the call before you make it

Everything above is easier if the call is not the first time you have said the words out loud.

Rehearsal works here for an unglamorous reason: the first attempt at any sentence carries the most tension, and there is no rule saying the first attempt has to be the real one. Say the opening line to an empty room. Say it to a recording you delete. Say it while walking. The tenth version of “Hi, it is Sam here, I am calling about an appointment” is a different physical experience from the first, and the phone call gets the tenth.

This is also the honest answer to why an app is useful for this at all. Not because software knows something a person does not, but because rehearsal needs to be available at eleven at night when you remember the call you did not make, and a speech-language pathologist is not.

When to send the email, and when that is avoidance

Here is the part that most pages about this leave out, because it does not sell anything.

Sometimes the email is the right call. Not everything needs a voice. Booking a table, changing an appointment, confirming a delivery — plenty of people who do not stutter handle all of it in writing, and choosing the same channel is not a failure. It is a Tuesday.

The test is simple, and you already know the answer when you ask it:

Would you send the email if you did not stutter?

If a colleague who has never blocked in their life would also email, email. If they would pick up the phone and you are not, that is avoidance, and avoidance is the thing that actually costs you. It is quiet, it compounds, and it shrinks the range of things you do without ever announcing itself. One skipped call is nothing. Four years of skipped calls is a different job, a different social life, and a smaller map.

So the rule is not “always call”. The rule is: make the choice on purpose. Decide it as a decision, not as a reflex, and notice when the reflex is answering for you.

If the answer today is the email, send the email. Then pick a call that does not matter much — a shop, an opening-hours question, something with no consequence — and make that one instead. The practice is the point. The stakes are not.