Loading tutorials…
Loading tutorials…
Typeform's one-question-at-a-time UX is what makes it convert — and what makes it brittle. This walks through how to structure questions, pick the right field types, and ship a survey that hits 60%+ completion rate.
Who this is forMarketers building their first or fifth Typeform. If you have ever shipped a Typeform and watched completion rate sit below 40%, the issues are usually structural, not creative.
What you'll need
Step 1
Every survey should have ONE primary outcome. If you cannot state it in one sentence, you will build a survey nobody finishes.
Pick the single outcome: "Capture qualified lead with budget/timing data," "Score customer satisfaction with NPS," "Segment new signups into use-case buckets." Only one.
If you find yourself wanting two outcomes, build two surveys. Combining halves completion rate on both.
Write the outcome at the top of your scratchpad. Every question must serve it. If a question is "nice to know" but not necessary for the outcome, cut it.
Step 2
First question sets the tone. Multiple-choice with 2-4 options beats free-text. Email last, never first.
Open with a multiple-choice question that reveals respondent intent: "What brings you here today?" with 3-4 options. Low cognitive load = high response rate.
Avoid opening with email. Email-first surveys lose 30-50% of respondents because they signal "we want to sell you something" before delivering value.
Welcome screen is optional — use it only when you can deliver real value in one line ("Get a custom growth plan in 90 seconds"). Generic welcome screens like "Hi! Take our quick survey!" hurt completion.
Avoid long-text fields in the first 3 questions. Long-text answers feel like work and drop completion sharply.
Step 3
Multiple-choice, dropdown, rating, opinion scale, picture choice, yes/no, short text, long text, email, phone, number, date, file upload, payment. Pick deliberately.
Multiple-choice (single or multi-select): default for any answer with 3-7 options. Fastest to answer on mobile.
Dropdown: only when options exceed 8 (countries, industries). Mobile UX is worse than multiple-choice.
Opinion scale (1-10) and Rating (stars): good for NPS and CSAT. Do not use for nuanced preference — too coarse.
Picture choice: high engagement but slow. Reserve for branding/aesthetic preference questions, not factual data.
Short text + email + phone: use the typed fields, not generic short-text — Typeform enforces format validation.
Long text: use sparingly. One open-ended question per survey, placed near the end.
Number: for budget, team size, age — never short-text. Number field unlocks calculator logic and integer validation.
Date: native picker. Do not ask "When are you planning to start?" as text.
Step 4
Build the easy/curious questions first, friction questions in the middle, and contact info last. Email at the end, never at the start.
Questions 1-2: low friction, high curiosity. "What is your biggest challenge with X?" Single-select.
Questions 3-5: substantive value or qualification. Use logic jumps to skip irrelevant blocks.
Questions 6-8: friction questions (budget, timing, team size). Respondents are now invested — completion rates hold.
Last 1-2 questions: contact info. Email, phone, name (optional). By this point, respondents have committed to the outcome.
Final thank-you screen: deliver the promised value. If you promised "growth plan," show it (or commit to email delivery within a clear window).
Step 5
Make ONLY business-critical fields required. Email and one qualification field. Everything else optional.
Default Typeform behavior is "not required." This is the right default — keep it.
Required: email, one qualification field (use-case or company size), and any field that triggers a logic jump downstream.
Optional: name, phone, "anything else?" Marking these required is the #1 cause of completion drop in the last 25% of the survey.
On the "Settings" tab of each field, toggle "Required" only when truly necessary. When in doubt, optional.
Step 6
Default thank-you = "Thanks!" Useless. Use thank-you screens to deliver promised value, route to next action, or self-segment further.
Add a thank-you screen that delivers on the survey promise: "Your growth plan is on its way to {{email}}" or "Book a 15-min walkthrough →" with a calendar link.
Use logic jumps to show different thank-you screens by segment. Hot lead → calendar link. Cold lead → resource library. Wrong-fit → redirect to community.
Avoid generic "Thanks for your response!" — it wastes the highest-attention moment in your funnel.
For lead-gen surveys: a Calendly embed on the thank-you screen typically books 8-15% of completers same-day.
Step 7
Build looks fine in desktop preview. Mobile is where 60-70% of responses come from. Test on real phones, both iOS and Android, before sharing the link.
In Typeform → Preview, copy the link and open on your phone. Walk through every question as if you were a respondent.
Watch for: question text that wraps awkwardly, option buttons that overlap, picture-choice images that load slowly, fields that auto-zoom on iOS Safari.
Open the preview on Android Chrome too — different default font rendering can break layout.
Time yourself completing the survey. If it takes more than 90 seconds, cut questions until it fits.
Test the thank-you screen. Calendar embeds especially behave differently on mobile.
Common mistakes
Opening with email or contact info
What goes wrong: Respondents bail before reaching the value question. Completion drops 30-50% vs. delaying email to the end. Lost-lead cost compounds with every form view.
How to avoid: Move email to the last or second-to-last question. Open with a multiple-choice question that signals "you are in the right place."
Too many questions
What goes wrong: Each additional question past 7 cuts completion 5-10%. A 14-question survey has roughly half the completion rate of a 7-question version.
How to avoid: Cut ruthlessly. If a field is not required to score the lead or take action, kill it. You can always email follow-up.
Marking too many fields required
What goes wrong: Respondents see a red "this field is required" error, get frustrated, and abandon. ~10-15% of submissions die at the first required-error block.
How to avoid: Only email and one qualification field should be required. Phone is never required in B2B.
Generic thank-you screens
What goes wrong: Highest-attention moment in your funnel wasted on "Thanks for your response!" You skip 8-15% of same-day conversion opportunity.
How to avoid: Deliver value or route to next action on the thank-you screen. Calendly embed, resource link, or segmented redirect.
Skipping mobile testing
What goes wrong: Form looks fine on desktop. On mobile Safari, the email field auto-zooms and the button shifts off-screen. Mobile completion drops to 20%. You don't notice until weekly review.
How to avoid: Test every form on real iOS and Android devices before publishing. Walk through the entire flow including thank-you screen.
Recap
Done — what's next
How to set up a Typeform account the right way
Read the next tutorial
Hand it off
Building one Typeform that converts is doable in a weekend. Building 5-10 across a funnel, with the right logic + integrations + thank-you flows, is a job. EverestX matches you with a vetted conversion-funnel specialist for $14-16/hr — most builds land at $80-200/form, then $200-600/mo for ongoing optimization.
See specialist rates
Lead-gen: 5-8 questions, under 90 seconds to complete. NPS or customer-feedback: 3-5 questions, under 60 seconds. Anything past 10 questions needs ruthless justification — completion drops sharply.
Only when you can deliver real value in one line. Generic welcome screens like "Hi! Take our quick survey!" hurt completion. If you cannot promise something concrete, skip the welcome screen.
Three usual causes: (1) email asked too early, (2) too many required fields, (3) survey is too long. Run through this tutorial's mistakes list — most surveys have at least two.
Not natively. Duplicate the survey, change the variable (length, field order, copy), and split traffic via UTM or with a tool like VWO/Optimizely. Typeform also reports completion rate per form so you can compare.
Typeform
Most Typeform accounts get created in 5 minutes and start leaking responses by week two. This walks through the right setup path — plan choice, workspace structure, brand kit, GDPR consent, and the integration baseline that prevents 80% of "the form looks weird" tickets later.
Typeform
Logic jumps are what turn Typeform from a survey into a smart funnel. Done right, they route every respondent to a personalized path. Done wrong, they create dead ends and respondents stuck on the wrong branch.
Typeform
Typeform Insights shows you where respondents drop off. Most teams glance at it once and miss the patterns. This walks through the diagnostic sequence specialists use to lift completion 15-30%.
Tally
Tally's block-based editor is forgiving — which is why most teams build forms that look fine and convert at 18%. This walks through the build path that lands forms at 35-45% conversion.