Multi-Language IVR: Route English, Spanish, Tagalog

Build a two-step phone menu with a first prompt that lets callers pick a language, then route each choice straight to its agent group with a short queue and a matching voicemail. That’s the cleanest way to set up a multi-language IVR, and you can finish a basic English–Spanish–Tagalog build in about 30 minutes if your platform supports IVR, queues, schedules, and per-language voicemail. When you’re done, callers press 1 for English, 2 for Spanish, or 3 for Tagalog and reach the right team without a long tree.

What a multi-language IVR does (and when to skip it)

An IVR (a phone menu that plays options and takes keypad input) lets you steer calls without a receptionist. A multi-language IVR adds one simple first step: language choice. After that pick, the call goes right to the agents for that language, and any hold music or voicemail stays in that language too.

Use this when a meaningful share of callers need another language. If 20–40% of your callers pick Spanish, it’s worth a clean path. If only a handful do, skip the menu. Use a bilingual agent or publish a separate number for the minority language in ads and landing pages.

Default language strategy is simple: lead with the majority language, then offer the next most common. Give a fast path. One short line for each language, repeat once, then route to the default if there’s still no input.

We’ll carry one example: a home-services line that serves US callers in English and Spanish. English rings a US team. Spanish rings a bilingual team. You also add a Tagalog option for an offshore team to cover overflow.

Build a two-step bilingual IVR (English/Spanish)

{"type":"flow","title":"Two-step language IVR with overflow","caption":"Callers choose a language, ring for ~20s, overflow to a short queue, then voicemail; after-hours goes to the right voicemail.","nodes":[{"id":"a","label":"Caller","kind":"caller"},{"id":"b","label":"Main number","kind":"number"},{"id":"c","label":"Language IVR","kind":"ivr","sub":"1 Eng, 2 Esp"},{"id":"d","label":"EN ring group","kind":"target","sub":"20s + 45s queue"},{"id":"e","label":"EN voicemail","kind":"voicemail"},{"id":"f","label":"ES ring group","kind":"target","sub":"20s + 45s queue"},{"id":"g","label":"ES voicemail","kind":"voicemail"},{"id":"h","label":"After-hours rule","kind":"router","sub":"local hours"},{"id":"i","label":"Closed message","kind":"voicemail"}],"edges":[{"from":"a","to":"b"},{"from":"b","to":"c"},{"from":"c","to":"d","label":"Press 1"},{"from":"c","to":"f","label":"Press 2"},{"from":"d","to":"e","label":"no answer"},{"from":"f","to":"g","label":"no answer"},{"from":"c","to":"h","label":"after hours"},{"from":"h","to":"e","label":"EN callers"},{"from":"h","to":"g","label":"ES callers"}]}

By the end of this build, callers press 1 for English or 2 for Spanish, ring the right team for about 20 seconds, overflow to a short queue, and then land in the correct voicemail. Keep the tree shallow: language choice first, then a direct route.

Do the setup in this order:

1. Provision or pick a number. Use a new business number for this flow so you can test without breaking live calls. If you already have a main line, point it to your new IVR when you finish testing.

2. Create the IVR with two options. Add a single menu with “Press 1 for English. Para español, marque 2.” Keep input timeout to about 3–4 seconds. Enable one repeat, then default to English.

3. Record short prompts for each step. Record the language choice in both languages. Also record per-language “closed” lines and voicemails. See scripts below or use IVR prompt best practices to avoid mouth noise, long silences, or unclear digits.

4. Add the English route. Make a ring group (a set of answering targets) for the US team. Set ring time to 18–22 seconds. If no answer, overflow to a short queue (30–60 seconds). Keep hold music short so callers don’t wait forever and then hit voicemail during an agent transfer.

5. Add the Spanish route. Do the same for your bilingual team. Set the same ring timers. If you mix mobile phones and landlines, test early for ring-back delays and answer times.

6. Set ring timers and overflow. 18–22 seconds per target is usually one to three rings on a mobile and four on a desk set. After that, send the call to the small queue. If the queue still has no pickup in 30–60 seconds, go to voicemail in that language. Avoid dead-ends at all costs.

7. Add per-language queue and voicemail. Use Spanish hold music only if it’s short and clean. Make sure the queue exit goes to the Spanish voicemail box and not the English one. Keep each voicemail prompt under 10 seconds.

8. Add a whisper label for agents. A whisper (a short audio only the agent hears before connect) should say “Spanish Lead” or “English Service” so the agent opens with the right greeting. Keep whispers under two seconds so they don’t clip the caller’s hello.

9. Turn on call recording only with consent where required. Laws differ by country and by US state. If you record, say a short consent line before routing: “This call may be recorded. Para continuar, permanezca en la línea.” Only record what you need for QA and training.

10. Set an after-hours branch. Tie schedules to local time for the English and Spanish teams. When closed, skip queues and send callers straight to the right voicemail greeting for their language. Keep the closed message clear and short.

11. Test with real phones. Call from a US mobile and a landline. Press 1 and 2. Let it timeout. Reject the call at an agent phone to trigger overflow. Leave a voicemail and play it back. Check that the whisper, ring timers, queue length, and voicemail language all match the plan. Use a test script and mark results.

If your platform has per-target schedules and queues, the build maps cleanly: IVR → two routes → two ring groups → two queues → two voicemails, plus a closed branch.

Add a third language without long trees

Keep it shallow. Don’t add second-level menus inside each language. Add one more choice to the first step, then route straight to the agent group for that language.

In our example, add Tagalog as option 3. Route it to a SIP or browser agent group (a SIP endpoint is an internet phone address your agents answer in an app). Many offshore teams answer in a browser or SIP softphone. That avoids PSTN (the regular phone network) hops to mobiles, so audio is cleaner and post-dial delay is shorter. It also cuts costs for frequent cross-border calls. If this fits your setup, see Forward to SIP for a quick primer.

Use per-target schedules by time zone so off-hours go to the right voicemail in Tagalog. If your Tagalog team is in Manila and your English team is in Chicago, their “open” windows won’t overlap. Tie each language route to its own schedule and skip the queue when closed. For help on time windows, see Schedule-based call routing.

If one language gets a lot of volume from ads, consider separate entry numbers per language. This is DNIS (dialed number identification service — the number called), and it lets you send Spanish callers straight to the Spanish team with no menu. Keep the main number with the language menu for everyone else.

Multi-language IVR menu layout that stays short

Put language first. The menu should talk about language before anything else. Keep all language options on one line. Two or three languages max per line.

Keep prompts tight. Use 3–5 words per language. Speak digits clearly with small pauses. Say each line once, then repeat the whole choice once if no input. After the repeat, default to the majority language and route.

Map digits well. Put the majority language on 1. Put the next on 2, and the third on 3. Don’t reuse those digits for anything else in submenus. A caller who heard “press 2 for Spanish” shouldn’t later hear “press 2 for billing.”

Honor timers. Set 18–22 seconds per target before overflow. Keep total queue wait under 60 seconds. Longer queues make callers hang up or reach voicemail during a transfer. Shorter queues improve the chance that your overflow voicemail actually gets the call.

Write and record clear prompts (with Spanish/Tagalog/Hindi lines)

Pick one clear voice for all prompts. Speak at about 135–150 words per minute. Pause 0.3–0.5 seconds around digits so “press 1” is sharp and not “press-one.” Smile while recording — it helps tone even in short lines.

Recording tips:

• Use a quiet room and a headset or dynamic mic.
• Record close to the mic to avoid room echo.
• Mono, 8 kHz telephony quality is fine. Don’t over-process.
• Name files by language and step: “lang-select_en.wav”, “vm_es_closed.wav”.

Sample language-selection scripts:

• English: “For English, press 1.”
• Spanish: “Para español, marque 2.”
• Tagalog: “Para sa Tagalog, pindutin ang 3.”
• Hindi: “Hindi ke liye, 4 dabaiye.”

Keep per-language voicemail headers short, and in-language:

• English: “Please leave your message after the tone.”
• Spanish: “Deje su mensaje después del tono.”
• Tagalog: “Umandang mag-iwan ng mensahe pagkatapos ng beep.”
• Hindi: “Beep ke baad apna sandesh chhodiye.”

If you record calls, add consent where needed. Laws vary by country and by US state. Use a short bilingual line at entry so all callers hear it before routing. For example: “This call may be recorded. Para continuar, permanezca en la línea.”

Route to the right agents, hours, and fallbacks

Map each language to a group:

• English → US ring group.
• Spanish → bilingual group.
• Tagalog → offshore SIP/browser group.

Pick a routing method per group. Priority routing sends the call to a primary bilingual agent first, then others if they don’t pick up. Round-robin spreads calls across the team so no one person gets all calls. Simultaneous ring works for small teams, where any of three or four phones can grab the call fast.

Set schedules per target. Use local hours for each team. During off-hours, skip queues and go straight to the voicemail for that language. Don’t trap callers in a queue that no one is watching.

Keep a queue and a voicemail per language. Hold music can be the same across languages if it’s instrumental and short; the important part is the messages that play. Never send a Spanish caller to an English voicemail. Tie each path to its own box and label them clearly in your portal.

Use a whisper label so agents answer right. A whisper like “Spanish Lead” or “Tagalog Support” plays to the agent’s ear before the caller connects. It helps the greeting and faster triage.

Pass through the caller ID. Make sure your routes keep the original caller’s number to the agent phone, not your main number. If you mask it, agents can’t match callbacks. Do a quick test to see what your agents’ screens show.

Test every path before going live

Run a fast QA flow with real calls and real agent devices. DTMF (the keypad tones you send by pressing numbers) can fail if prompts or timing are off, so press the keys, don’t just “think through” the menu.

Test this set:

• Each DTMF option: 1, 2, and 3 if you added Tagalog.
• Wrong-key input (e.g., 9) and no input timeout.
• After-hours branches for each language.
• Overflow from ring group to queue, then to voicemail in the right language.
• Whisper heard by the agent and the agent’s greeting.
• Caller ID shows the original number at the agent phone.
• If recording is on, the files exist and start at the right point.

Use live call logs to confirm the IVR leg, the selected option, the target that rang, and any failover hop. If your platform gives you real-time logs, keep them open during tests and fix misroutes before launch. For deeper checks on production calls, see Call logs, CDRs, and debug. A short phone-based checklist helps speed this up — keep one handy like our test call forwarding checklist.

Cross-border checks matter if you route to PH/IN/BD/PK mobiles. Place real calls from a US mobile and a US landline, and from a local SIM in that country if you can. Listen for audio level, round-trip delay, and post-dial delay. If mobile-to-mobile hops add noise or lag, consider routing those agents on SIP or browser instead.

Put it live without over-complicating it

Skip a language menu if more than 90% of callers use one language. Lead with that language, and publish a separate number for the minority language in ads and emails. Keep to two or three languages on one line. If you need more, split by campaign or number so you don’t build a maze.

CallFlow supports IVR menus, per-target schedules, queues with hold music, SIP/browser agents, call recording, and whisper messages — enough to run a clean bilingual line without a long tree. Spin up a number and build this in about 30 minutes, then test end-to-end. If you’re ready to try it, register your account and set up your first flow at callflow.solutions/register. If you want help mapping your current menu to a short bilingual IVR, reach out at callflow.solutions/contact.