Have a Question?
ITR (Multilingual)
ITR (Multilingual) Collector:
Bilingual Numbered Menus
with Automatic Language Routing
The ITR Multilingual collector runs parallel numbered menus in English and Spanish — OTTO detects the contact’s language from their reply and routes them into the correct language menu automatically. Each language path has its own branches, Final Messages, and email notification configuration.
Read ITR — Text & MMS Image Menus before this article. The Multilingual variant adds a parallel Spanish menu system to the standard ITR — everything about branching, MENU navigation, and Final Messages applies to both language paths.
The Parallel Menu Architecture
Building an ITR Multilingual collector means building two complete ITR systems that share the same entry point but diverge at the language detection point:
Full ITR configuration — main menu text, all numbered branches, sub-menus, Final Messages per branch, and email notification addresses. This is the default path for all contacts until Spanish is detected.
A complete parallel ITR in Spanish — same branch structure, Spanish menu text, Spanish Final Messages. Each branch can have a different Spanish Final Message and still routes to the same email notification addresses.
The MENU keyword works in both language paths — typing MENU returns the contact to the main menu in their detected language. No separate configuration required.
Branch-level email routing applies to both language paths. The Spanish-speaking contact who selects “Sales” routes to the same sales team email as an English-speaking contact who selects “Sales.” Language preference is flagged in the alert.
For the cleanest bilingual experience — zero English prompts for Spanish-speaking contacts — use an interstitial page with English/Español language selection buttons before the SMS opens. See Interstitial Pages with Language Funnels. The interstitial routes contacts into separate collectors per language rather than using detection inside one collector.
The Five Stages
Market size, conversion data, and the operational case for bilingual ITR menus in high-volume Spanish-speaking markets.
Read the Insight →Step-by-step setup for configuring the Spanish-language parallel menu in any multilingual collector.
Read the KB Article →How automotive dealerships use ITR Multilingual to route English and Spanish-speaking customers into the same branch structure with language-appropriate menus.
Read the Playbook →