Skip to main content
< All Topics
Print

Custom Questions, Captures Name

Knowledge Base Collector & Messaging Framework
👤 Collector & Messaging Framework · Custom Questions, Captures Name

Custom Questions,
Captures Name:
Personalized Qualification from the First Reply

This variant runs the same linear question sequence as the standard Custom Questions collector — with one built-in difference: OTTO always asks for the contact’s name as the very first question, before any other configured questions run. The name is stored separately as a First Name field on the contact record.

Custom QuestionsCaptures NameLead QualificationPersonalization
What It AddsA mandatory name-capture step inserted before your first configured question. OTTO asks “What’s your name?” first — every time, for every contact — and stores it as the First Name field.
What You GetA named contact record — {first_name} available for personalization in outbound campaigns, Prepare Caller messages, and 1-to-1 follow-ups. Reps can address the contact by name on the callback.
The TradeoffOne extra question = slightly lower completion rate. Use this variant when rep personalization on the callback is worth the tradeoff. Skip it for simple coupon flows or anonymous list building.

This variant builds on the Default: Custom Questions collector. The only behavioral difference is Stage 3 — OTTO inserts a name question before any other question you’ve configured.

Stage 3 — What Changes

In a standard Custom Questions collector, Stage 3 sends your first configured question immediately after opt-in. In the Captures Name variant, OTTO inserts a fixed name question first:

Standard Custom Questions — Stage 3
Captures Name — Stage 3
OTTO sends your Q1 immediately after opt-in
OTTO sends “What’s your name?” first — always
First reply = answer to your Q1
First reply = First Name field on contact record
Your Q1 is the first configured question
Your Q1 runs second — after the name is captured
No name field unless you manually add a name question
First Name always populated on the contact record

When to Use Captures Name

Use it when

Your rep will make a personalized callback (“Hi Sarah — calling about your HVAC inquiry”). You want {first_name} available for outbound campaign personalization. The lead gen flow benefits from a human, named interaction.

Skip it when

Speed of opt-in matters more than personalization (coupon delivery, event registration). The follow-up is automated, not a personal rep callback. Every extra question reduces completion rate — only add the name step if you’ll use it.

✓ Using the captured name downstream

Once the First Name is on the contact record, it’s available as {first_name} in any outbound campaign dynamic keywords. A re-engagement send that says “Hi Sarah — you asked about HVAC back in March” outperforms a generic blast at every metric. The name capture investment pays back on the first outbound campaign.

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