Have a Question?
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.
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:
When to Use Captures Name
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.
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.
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
Why OTTO-qualified named leads answer callbacks at dramatically higher rates than anonymous form fills.
Read the Insight →How to use the captured {first_name} field in personalized outbound campaign messages.
Read the KB Article →Events where capturing the attendee’s name at opt-in is essential — open houses, tradeshows, event registrations.
Read the Playbook →