Text Response Block
Published July 25, 2026
Use a Text Response when the participant needs to write an answer in their own words. It is best for intake context, feedback, notes, short explanations, recall questions, and answers you want to reuse later in the quiz.
Text Responses are flexible, but they are less predictable than fixed-choice blocks. If the next step depends on a clean yes/no, option, score, or segment, use a structured block such as Choice Buttons, Multiple Choice, Dropdown, or Yes / No.
Best used for
Client intake details
Lead qualification notes
Open-ended feedback
Knowledge recall
When to choose another block
Need reliable branching
Need a rating
Need a date
Need interpretation
Setup flow
- Add a Text Response from the Question Blocks palette.
- Write a focused prompt that makes the expected response clear.
- Decide whether the response should be required before the participant can continue.
- Optionally save the response to a variable when the answer should be reused in outcome copy, logic, exports, or downstream steps.
- Optionally enable the Answer Key if the question has exact accepted answers and should contribute to scoring.
- Preview the quiz and test the response in any scoring, variable, tag, or Jump Logic behavior that depends on it.
Settings reference
Required response
Answer Key
Basic+Immediate feedback
Basic+Response variable
Split Media
Basic+Jump Logic
ProScoring exact answers
The Answer Key is useful when a Text Response has one or more precise accepted answers. Enter each accepted answer separately and set the points awarded when the response matches.
Use exact-match scoring for knowledge checks, codes, short recall questions, or simple typed confirmations. Avoid it for subjective responses, long explanations, spelling-sensitive answers, or anything that needs interpretation. For those cases, collect the text and review it later, route with structured questions, or send the response into an Agent Step.
For scoring behavior across the quiz, see Scoring Logic.
Variables and personalization
Save a Text Response response to a variable when the answer should travel with the participant through the rest of the flow. This is helpful when you want outcome copy, follow-up context, exports, or later steps to reference what the participant typed.
Use a clear variable key that describes the answer, such as project_goal, biggest_challenge, or preferred_outcome. Keep the prompt aligned with that variable so the saved value is easy to understand in submissions and exports.
Routing guidance
Text responses can support routing, but free-form answers are naturally inconsistent. If routing needs to be deterministic, ask the branching question with a structured block first, then use a Text Response afterward to collect extra context.
Use Text Responses with Jump Logic when the rule depends on a saved variable, tag, score, or controlled answer pattern. For broader interpretation, pair the response with an Agent Step so the quiz can classify or summarize the answer before the final result.
Troubleshooting
Why did my typed answer not score as correct?
Should I branch directly from a Text Response?
Why is my response not available later?
Tips
- Ask one thing at a time. If you need several answers, split them into separate questions.
- Use examples only when they reduce ambiguity, such as expected format or level of detail.
- Keep deterministic decisions in structured blocks and use Text Responses for context.
- Use Answer Key scoring only for precise accepted answers.
- Save important text responses to variables so the answer is available outside the original question.
- Test the published flow with realistic answers, including misspellings and longer responses.
Next steps
Use fast structured choices when the next step depends on a reliable answer.
Configure options, scoring, tags, media cards, and Jump Logic.
Understand how tags and variables support personalization and exports.
Learn how points, totals, and outcome rules work across a quiz.
Interpret written responses with AI before recommendations or routing.

