Multi-language IVR: detect language, per-language menus and jumping between IVRs

If you serve customers across several countries, you can build an IVR that detects the caller's language and routes them into a full menu in that language, instead of cramming everything into one flow.

Requirements

• Crece or Escala plan with IVR enabled.
• The visual editor (Flow type, not Simple) to use the language nodes.

Two ways to detect the language

1. Automatic: the "Detect language" node reads the caller's phone country code (Brazil/Portugal → Portuguese; US/Canada/UK/Australia/New Zealand → English; everything else → Spanish) and stores it in a variable.
2. Manual: a menu ("Press 1 for español, 2 for English, 3 para português") using Wait for digit, storing the caller's choice.

Steps to build the multi-language flow

1. Create a "root" IVR with the Detect language node (or the manual menu) as its first step.
2. Create a separate, complete IVR for each language — greeting, options, all text written natively in that language.
3. From the root IVR, on each branch (es/en/pt), add a "Go to another IVR" node pointing to that language's IVR. It's a one-way jump — the call continues inside the destination IVR.
4. Publish the root IVR and each language IVR separately.

Example

A caller dials in from a Portuguese number (+351). The Detect language node stores "pt", and that branch leads to a Go to another IVR node pointing at "Sales IVR PT", where the whole menu — audio and options — is in Portuguese.

Tips

• Set the default language and voice on each child IVR so its audio always comes out in the right language.
• If country-code detection isn't reliable for your customer base, add a manual menu as a backup.

Troubleshooting

• Calls always land in Spanish: check that Detect language sits before the jump, and that all three branches (es/en/pt) point to the right IVR.
• Destination IVR's audio comes out in the wrong language: check that specific IVR's default language and voice settings.