How to Dial an Extension or Get Through a Phone Menu Abroad

An extension is not part of the phone number

An extension is dialled after the call has already connected, by sending tones down the open line. It is not part of the telephone number and it cannot be included in one. This single fact explains most of the confusion people have with extensions, and getting it right solves most of the problems.

When you call a company, the number reaches their switchboard — a PBX. The PBX answers, and only then does it listen for digits to decide which internal phone to ring. Those digits travel as DTMF, dual-tone multi-frequency: the familiar beeps, each one a pair of audio tones sent over the voice channel itself.

So a number written as +1 415 555 2671 ext. 204 is really two instructions. Call +14155552671. Then, once it answers, send 204.

How to send an extension automatically

Both major phone platforms let you build the whole sequence into one saved contact, using two special characters.

Pause — the comma ,. Waits about two seconds, then sends the digits that follow. Use it when you know roughly how long the switchboard takes to answer and it is consistent. Add more commas for more delay.

Wait — the semicolon ; on iOS, or w on many Android diallers. Stops and asks you to confirm before sending the rest. Use it when the timing varies, or when you have to hear the menu before choosing.

What you want	What to save
Dial, wait ~2 s, send extension 204	+14155552671,204
Dial, wait ~6 s, send extension 204	+14155552671,,,204
Dial, then tap to send 204 when ready	+14155552671;204
Menu option 2, then extension 204	+14155552671,,2,,204

To type a comma or semicolon on iOS, press and hold the * key on the keypad — * held gives a comma, # held gives a semicolon. On Android, most diallers expose both under a long press of * or in the overflow menu when editing a contact.

Pause and wait characters belong only in a saved contact or in the dial pad, never in a stored E.164 number. A database field holding a phone number should contain +14155552671 and nothing else; the extension belongs in its own field. See E.164 format for why.

Why does pressing keys do nothing on my call?

If the menu does not respond to your key presses, the cause is almost always one of three things, in this order of likelihood.

The tones are not reaching the far end. On an internet call, DTMF can be sent in three different ways: as audio in the voice stream, as a separate signalling event defined in RFC 2833, or via SIP INFO messages. If your app and the receiving system disagree about which method to use, the far end hears nothing. This is a configuration problem between the two systems, not something you can fix by pressing harder. If a menu is unresponsive on an app call and responsive on a carrier call to the same number, this is why.

The tones are being distorted. Aggressive audio compression can mangle DTMF sent as audio, because voice codecs are optimised for speech and not for pure tones. This is why in-band DTMF is unreliable over low-bitrate codecs and why RFC 2833 exists.

You are pressing too early or too fast. Many systems ignore input during their greeting, and some require a moment between digits. Wait for the prompt to begin, then press deliberately.

How to reach a human on a foreign phone menu

Automated menus are designed to deflect calls, and abroad they are also in a language you may not read. A few approaches work more often than others.

Press 0, repeatedly. Zero is the most widely implemented shortcut to an operator, and on many systems pressing it several times in succession — or at each menu level — escalates to a human. On some systems * or # does the same.

Say nothing. Speech-driven menus usually route to an agent after two or three failures to recognise input. Silence is a reliable failure.

Press the option for a language you do not need. Menus that offer a language choice often have thinner automation on the secondary branch, which reaches a person sooner.

Call outside peak hours in the destination's timezone. Queue length is the biggest single factor in whether you get through at all, and a call placed at the destination's mid-morning behaves very differently from one placed at 9am local. The best time to call planner shows the destination's clock against yours.

Have the account number ready before you dial. Most menus ask for it, and fumbling for it while the timer runs is where short calls become long ones.

Extensions on international calls

Two things change when the switchboard is in another country.

The connect time is longer. International call setup takes several seconds more than a domestic call, and a comma-based pause tuned for a local number will fire too early. If a saved sequence works domestically and fails internationally, add commas, or switch to the wait character and send the digits by hand.

Direct inward dialling may make the extension unnecessary. Many organisations assign each internal phone its own full external number — direct inward dialling, or DID — so the extension is reachable as a normal number with no menu at all. If you have both a switchboard number and an extension, it is worth asking whether a direct number exists. It is faster every time and it avoids the DTMF question entirely.

Conference bridges and PIN codes

The same mechanism handles conference dial-ins, and it saves more time there than anywhere else because the sequences are longer.

A dial-in usually needs a number, then a meeting ID, then #, then sometimes a participant PIN and another #. Saved as one string it becomes:

+14155552671,,123456789#,,1234#

The two commas after the number wait for the bridge to answer, the meeting ID is sent with its terminating #, two more commas wait for the PIN prompt, and the PIN follows. If the bridge is slow to answer, add commas rather than guessing — an extra two seconds costs nothing and a sequence sent early has to be redialled entirely.

Where the timing is genuinely unpredictable, use the wait character instead and tap once at each prompt. It is slower but it never fails.

A caution worth taking seriously: a saved contact containing a conference PIN stores that PIN in your address book in clear text, and address books sync. For a recurring internal bridge that is usually fine; for anything sensitive it is not.

When the menu is in a language you do not read

Two things help more than translation.

Menu structures are conventional. Across most of the world, 1 is sales or account information, 2 is support, 9 is repeat, 0 is operator, and * returns to the previous level. You can navigate a menu in a language you do not speak with reasonable success on those conventions alone.

Numbers are spoken in a recognisable rhythm. Even without the language, the digit announced before each option is usually distinguishable, and counting the options as they are read gives you the position of the one you want.

If the call matters and the language is a genuine barrier, calling the organisation's international or English-language line — most large institutions publish one — is faster than fighting the domestic menu.

What a call to a menu costs

The billing unit matters here more than anywhere else, because menu time is dead time you still pay for.

A call that spends 90 seconds in a menu and 4 minutes with a person is 5 minutes 30 seconds. Billed per second, that is what you pay. Billed per whole minute, it is six minutes. Billed in three-minute increments — which some calling cards still do — it is nine.

Telvio bills per second, which matters most on exactly this kind of call. To see the arithmetic for a specific country and duration, use the call cost calculator.

When there is no extension and no menu

Some organisations are reachable only through a switchboard operator, and a few of them are reachable only in ways that are not obvious from the phone number at all.

Ask for the department, not the person. Switchboard operators route by department reliably and by name unreliably, especially across a language barrier where the name is unfamiliar. "Accounts" gets through; a surname frequently does not.

Note the extension you are transferred to. The moment an operator transfers you, ask what the extension is. Next time you can dial it directly with a saved sequence and skip the queue entirely. This is the single highest-value thing to do on a first call to any organisation you will call again.

Ask whether there is a direct line. Many people have one and simply do not advertise it. The question costs nothing and is answered honestly more often than not.

Check whether a callback is offered. Some systems offer to hold your place and call you back. On an international call this is worth taking every time: it converts an unpredictable wait into a call that costs nothing until it connects, and you are not paying per second to listen to hold music.

Bottom line

An extension is not part of a phone number. It is a set of DTMF tones sent after the call connects, and the way to automate it is to save the number with a comma for a timed pause or a semicolon for a manual wait — +14155552671,,204 for a six-second delay, +14155552671;204 to send on your tap.

When key presses do nothing, the usual cause is a mismatch in how the tones are transmitted rather than anything you are doing wrong; test the same number on a carrier call to confirm. To reach a person, press 0 repeatedly, stay silent on a speech menu, and call at a sensible hour in the destination's timezone. And if the organisation offers a direct inward number for the person you want, use it — it skips the menu, the tones and the waiting entirely.