Skip to main content
< All Topics
Print

Custom Questions(Multilingual)

Knowledge Base Collector & Messaging Framework
🌐 Collector & Messaging Framework · Custom Questions Multilingual

Custom Questions
(Multilingual) Collector:
Qualify in Any Language, Deliver in English

The Multilingual Custom Questions collector runs the same linear question sequence as the standard type — with one addition: when OTTO detects a Spanish reply, it switches the entire conversation to a pre-configured Spanish flow. Your team receives English lead data regardless of which language the contact used.

Custom QuestionsMultilingualSpanish SMSLanguage Detection
What It AddsAutomatic language detection on the contact’s first reply — OTTO switches to a fully configured Spanish question sequence when Spanish is detected. No action required from the contact.
What Your Team ReceivesEnglish-language lead data in every email alert — regardless of whether the contact spoke English or Spanish. Language preference is flagged on the contact record.
When to Use It Over StandardWhen your market has significant Spanish-speaking volume and you want automatic detection rather than requiring contacts to select a language on an interstitial page first.

This variant builds on the Default: Custom Questions collector — read that article first if you haven’t. The five-stage framework is identical; this article covers what’s different in Stage 3 and Stage 4 when language detection is active.

How Language Detection Works

After the opt-in text is received (Stage 2), OTTO sends the first question in English. When the contact replies, OTTO analyzes the reply text. A Spanish word or phrase in any reply triggers the switch — OTTO transitions to the configured Spanish question sequence from that point forward.

Contact replies in English
Contact replies in Spanish
OTTO continues English question sequence
OTTO switches to Spanish question sequence immediately
English answers stored · English lead alert
Spanish conversation · English lead data delivered to team
No detection action needed
Detection is automatic — contact does nothing special
✓ Interstitial alternative

For high-volume bilingual markets, consider combining a language selection interstitial with this collector — the contact selects English or Spanish before the SMS opens, eliminating the one-English-prompt gap. See Interstitial Pages with Language Funnels.

What to Configure Differently

When building a Multilingual Custom Questions collector, you configure everything in the standard flow plus a parallel Spanish version of each question:

🇬🇧
English question sequence

Configure exactly as you would a standard Custom Questions collector. This is the default path for all English-speaking contacts.

🇪🇸
Spanish question sequence

A parallel set of Spanish-language questions — not a direct translation, but a localized version that reads naturally in Spanish. Each question maps to the same data field as its English equivalent.

✉️
Spanish Final Message

Configure a Spanish-language Final Message (Prepare Caller or confirmation) for contacts who complete the Spanish flow. The English Final Message applies to English contacts.

📧
Notification email (shared)

The same email alert address receives leads from both language paths. The lead data arrives in English — language preference is flagged so your rep knows what to expect on the callback.

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->