Question types
Every step in a flow has one of six types. The type determines what the visitor sees, what gets stored on the lead, and what pricing rules can do with the answer.
Single choice
Section titled “Single choice”One option from a list. This is the workhorse type — most pricing questions are really “which of these describes the job?”
Answers are exact values, so rules use equals or not_equals.
Multiple choice
Section titled “Multiple choice”Any number of options from a list. Good for add-ons and extras: “Which of these do you need?”
The answer is a list, so rules use contains_any, contains_all or
not_contains. A common pattern is one rule per option, each adding its own
amount.
Number
Section titled “Number”A numeric entry — square metres, bedrooms, headcount, units. This is the type
that unlocks the quantity-driven pricing kinds: per_unit and tiered both
read their quantity from a Number step.
Rules can also compare it with gt, gte, lt, lte and between.
Free text. Useful for context you want on the lead — “Anything else we should
know?” — but weak for pricing, since rules can only match it with equals,
starts_with or ends_with.
Treat text steps as notes for the human who follows up, not as pricing inputs.
Captures the visitor’s email address. This is what turns a completed flow into a lead and determines where the customer’s copy of the estimate is sent.
Message
Section titled “Message”Not a question — a block of text shown to the visitor. Use it to set expectations before a long section, to explain why you are asking something personal, or to say what happens after they submit.
Message steps store no answer and cannot be used in pricing rules.