Choice
Select one of the alternatives your application can handle.
Use short, distinct IDs for routing and descriptions to explain their meaning. IDs must be unique and nonblank. Supply 2–255 options.
{
"model": "ren-zero-2026-11-12",
"type": "choice",
"situation": "A customer reports being charged twice for one order.",
"question": "Which support queue should handle this ticket?",
"options": [
{"id": "billing", "description": "Charges, invoices, and payment disputes"},
{"id": "delivery", "description": "Shipping and missing parcels"},
{"id": "other", "description": "The ticket does not clearly fit the named queues"}
],
"threshold": 0.9
}choice is the selected option ID; probabilities contains one entry for each offered ID and sums to one within numeric tolerance. p is the selected option’s probability. The current gateway also exposes that same value as confidence.
High probability only compares the offered options. It cannot prove that an omitted category would fit worse. Review ambiguous boundaries and option-order sensitivity on your own development examples.