Skip to main content
< All Topics
Print

Custom Questions, Captures Name + (Multilingual)

Knowledge Base Collector & Messaging Framework
🌐 Collector & Messaging Framework · Custom Questions, Captures Name (Multilingual)

Custom Questions,
Captures Name (Multilingual):
Named, Bilingual Qualification in One Collector

This variant combines all three capabilities: mandatory name capture as the first question, language detection that switches to a Spanish flow when detected, and English lead data delivered to your team regardless of which language was used. Full qualification, any language, named contact record.

Custom QuestionsCaptures NameMultilingualSpanish SMS
What It CombinesName capture (OTTO asks first) + language detection (switches to Spanish when detected) + English output (team always receives English lead data). All three in one collector.
Best Use CaseBilingual markets where rep personalization matters — legal intake, healthcare, home services in Spanish-speaking communities where the callback rep needs to address the contact by name.
What to BuildFour versions of each question: English + Spanish for the name prompt, and English + Spanish for each qualification question. Plan this before opening the platform.

This is the most fully-featured Custom Questions variant — combining Captures Name and Multilingual. Read both of those articles before building this variant — the configuration adds both layers simultaneously.

How It Flows

English-speaking contact
Spanish-speaking contact
Opt-in → OTTO asks “What’s your name?” in English
Opt-in → OTTO asks “What’s your name?” in English
Contact replies in English → English flow continues
Contact replies in Spanish → OTTO switches to Spanish name prompt
English Q1, Q2… Final Message in English
Spanish Q1, Q2… Final Message in Spanish
English lead alert to team — First Name field populated
English lead alert to team — First Name field populated — Language: Spanish flagged
📌 Planning requirement

Before building, write out every question in both English and Spanish. The Spanish versions should be localized — not just translated. “¿Cuál es tu nombre?” reads naturally. A literal machine translation of your English questions often does not. Have a Spanish speaker review your question text before activating.

The Five Stages

1
Entry Point — SmartLink or QR launches native SMS
Contact taps or scans. SMS app opens with pre-filled opt-in message. Optional interstitial page for language selection or offer display before SMS opens.
2
Pre-Filled CTA — contact taps Send, opt-in event fires
Phone number captured (carrier-verified) · TCPA consent logged · Entry point attributed · Geo data recorded · All in the same instant.
3
Initial Message — OTTO sends the first question or confirmation
Fires within seconds of the opt-in text. Content depends on collector type and variant — see above.
4
Navigation — contact replies, OTTO captures each answer
Linear sequence for question collectors. Every reply stored as a structured field. Partial answers saved if contact stops early.
Final Message — configured closing message fires
Prepare Caller, MMS coupon, confirmation, or TCPA compliance message — depending on use case. Email lead alert fires to your team simultaneously.
Search Icon Site Search Close Site Search
0 results
Text Auto Attendant->