Jev Choice versus Noul: choose the question type

Start with the decision you need

Use Choice when the next step needs one category from a defined set. Use Noul when you need to judge one yes/no statement. In the official interface, Choice supplies an option distribution; Noul supplies the probability of yes. Neither type executes your next step.

“Which queue should review this message first?” and “Does this message mention a payment problem?” ask different things. A payment issue and an app failure can both be present even when a workflow ultimately needs one owner.

Adapt the example

The attached feedback template starts with one Choice question. Write a routing policy and compare clear, mixed, and out-of-scope messages. To explore Noul, switch the editor to yes/no, ask only about one property, and replace the rules so they explain that property. Changing the type alone is not enough.

If several labels may all apply, separate checks can preserve that information. This website’s custom editor runs one question at a time; a multi-question integration belongs in your own application or the official Playground.

Interpret the answer in context

A Choice answer is relative to the choices offered. A Noul probability refers to its yes statement. Do not compare values from different questions as though they were interchangeable quality scores. Missing context can undermine either form.

A common design failure

“Is this urgent or a billing issue?” combines independent properties. A yes answer cannot say which property holds. Split the question, then decide in code how urgency and destination interact. Conversely, separate yes/no checks do not themselves resolve which queue owns a mixed message.

Try the feedback classification recipe, then document how a person should handle disagreements. The examples are editorial guidance, not performance findings.