Projects · Advanced customization
Ask only what you don’t already know.
A project is already tailored per audience. But you can go two steps further — in logic, by hiding questions until they earn the ask, and in context, by handing the interviewer a profile of the respondent so it never asks what you already know.
Used together, these two levers turn a 20-question slog into four questions that move the study forward. Your respondents spend their time on the answers only they can give you — nothing else.
Two levers
Conditional logic, plus what you already know.
The first lever lives inside the form. The second lives around it. Most studies benefit from both.
Form-level logic
Show a question only when it earns the ask.
Any question can declare a @when condition that references another question’s id. If the condition fails, the question never appears. No dead air, no “skip if you answered no” prose — the form quietly reshapes itself.
Operators
Per-respondent briefing
Pre-load what you already know.
Upload a profile per respondent — role, territory, product mix, tenure, whatever you already have in a CRM or HRIS. The interviewer reads it before the conversation starts and skips questions the answer is already on file for.
No more “what’s your segment?” when you put them in the segment. No more “how long have you been here?” when HR already told you.
See it in action — Example 1
NPS follow-up only when it’s warranted.
A classic pattern. Ask for a score. Only surface the “why?” when the score is a detractor — so promoters aren’t pestered, and detractors see a text box waiting for the real answer.
*number(#nps|count:11) How likely are you to recommend us?
labels: "Not at all" .. "Extremely"
>textarea What's driving the low score?
@when nps <= 6Step 1 · Always shown
How likely are you to recommend us?
Step 2 · Only when nps ≤ 6
What’s driving the low score?
Hidden for promoters and passives.
Works anywhere you author RASL — the Studio, the add_question MCP tool, or when Ask generates a form from a brief.
See it in action — Example 2
Interviewing your own AEs — with their book pre-loaded.
Imagine you’re surveying your own sales team on a strategic question — why are we losing in mid-market? You already know who each of them is and what accounts they carry. So you brief the interviewer up-front, and the form asks only the questions you couldn’t answer from the CRM.
What we already know about this respondent
AE
Jordan Reyes · Mid-market West
Book size
42 accounts · $6.8M ARR
Tenure
3y 4mo
Products sold
Core platform, Analytics add-on
Segment focus
Mid-market (50–500 employees)
What the form actually asks
- 1
“On the last three mid-market deals you lost, what did the buyer say the deciding factor was?”
- 2
“Which of your accounts would close on Analytics in the next quarter if pricing matched the Core bundle?”
- 3
“Name one integration gap that's come up in more than one POC this quarter.”
Without context: 20 questions, most of which they already answered on some other form. With context: a handful that move the study forward.
Where we’re heading
Echo — the in-form interviewer — isn’t fully wired to consume a live respondent profile yet. Today you approximate this by pre-populating defaults on the form and decomposing the study so each person only sees the sharp questions meant for them. Tomorrow, one upload per respondent does the same job in the background.
See it in practiceHow they combine
Each lever removes a different kind of waste.
Audience segmentation picks the right questions for the right group. Respondent context strips away the ones you already know. Branching hides the rest until they matter. The end of the line is a form that respects the person filling it out.
Audience segmentation×Respondent context×@when branching=the shortest honest form
Keep exploring