Structured Output

Preview in your theme

status='ready' — the answer the schema asked for. Rows follow SCHEMA order (not the model's key order), booleans are check chips, the enum is a badge next to how many values were allowed, the 11-tag array caps at 8 with an explicit 'Show 3 more', the 4-field customer object and the 3 orders are collapsible groups, and the 551-character reply is clamped at 240 with its exact character count on screen.

Structured output

16 of 16 fields

SummarysummarystringrequiredOne sentence an agent can read in three seconds.

Customer was charged twice for the annual renewal and wants the duplicate refunded.

Categorycategoryenumrequired

billing1 of 5 allowed values

Prioritypriorityenumrequired

high1 of 4 allowed values

Sentimentsentimentenumoptional

negative1 of 3 allowed values

ConfidenceconfidencenumberrequiredHow sure the model is about the category and priority.

0.820–1

Needs a humanneedsHumanbooleanrequired

true

Refund eligiblerefundEligiblebooleanoptional

true

Tagstagsstring[]optionalFree-form labels from the routing vocabulary.

"duplicate-charge"
"billing"
"stripe"
"vip-escalation"
"eu-region"
"invoice"
"refund-requested"
"second-contact"

Showing 8 of 11 entries

Namenamestringrequired: Chloe Wisoky
Emailemailstringrequired: [email protected]
Planplanenumrequired: enterprise1 of 3 allowed values
Account ageaccountAgeDaysintegeroptional: 412days

#1
OrderorderIdstringrequired
ORD-GYVNTX
Amountamountnumberrequired
131.63USD
Statusstatusenumrequired
paid1 of 4 allowed values
Refundedrefundedbooleanoptional
false
#2
OrderorderIdstringrequired
ORD-GJ1OAC
Amountamountnumberrequired
144.05USD
Statusstatusenumrequired
disputed1 of 4 allowed values
Refundedrefundedbooleanoptional
false
#3
OrderorderIdstringrequired
ORD-QVKV9Q
Amountamountnumberrequired
82.03USD
Statusstatusenumrequired
refunded1 of 4 allowed values
Refundedrefundedbooleanoptional
true

3 entries

Suggested replysuggestedReplystringoptionalDraft answer for the agent to edit — never sent automatically.

Hi Chloe — thanks for flagging this, and sorry for the double charge. I can see two identical authorisations against your card from the 3rd of March: one for the annual renewal and one that our payment provider retried after a timeout on t…

Follow up atfollowUpAtstring | nulloptionalISO-8601 instant, or null when no follow-up is needed.

2026-03-06T09:00:00.000Z

status='ready', same schema, a sloppy answer. Every defect here is valid JSON: priority='P1' is invented, confidence='0.82' is a number as text, accountAgeDays=412.5 is a float in an integer field, affectedOrders[1].amount arrived as a string, order #3 has an invented status — and needsHuman never arrived at all. Two warnings come from the app's validator (a policy rule no type checker can see), and two keys the schema never declared are shown instead of dropped. Hit 'Only issues (11)' to collapse the card down to just those rows and their parents.

Structured output

15 of 16 fields · 7 to review · 2 flagged · 2 off-schema

SummarysummarystringrequiredOne sentence an agent can read in three seconds.

Customer was charged twice for the annual renewal, is threatening to churn, and wants the duplicate charge refunded today.

Longer than the 120-character budget the ticket list can show.expected at most 120 charactersgot 122 characters

Categorycategoryenumrequired

billing1 of 5 allowed values

Prioritypriorityenumrequired

"P1"

Not one of the values the schema allows — the model invented this one.expected low · medium · high · urgentgot string "P1"

Sentimentsentimentenumoptional

negative1 of 3 allowed values

ConfidenceconfidencenumberrequiredHow sure the model is about the category and priority.

"0.82"

A number arrived as text — it has to be coerced before anything can sum or compare it.expected numbergot string "0.82"

Needs a humanneedsHumanbooleanrequired

Missing — the schema requires this field.

Refund eligiblerefundEligiblebooleanoptional

true

Marked refund-eligible, but this account is on the free plan — policy needs a manager.expected false while plan = freegot true

Tagstagsstring[]optionalFree-form labels from the routing vocabulary.

"duplicate-charge"
"billing"
"stripe"
"vip-escalation"
"urgent!!!"

5 entries

#5: Not in the routing vocabulary, so nothing will match this tag.expected one of 42 known tagsgot "urgent!!!"

Namenamestringrequired: Chloe Wisoky
Emailemailstringrequired: [email protected]
Planplanenumrequired: free1 of 3 allowed values
Account ageaccountAgeDaysintegeroptional: 412.5
A whole number was asked for; this one has a fractional part.expected integergot number 412.5

#1
OrderorderIdstringrequired
ORD-GYVNTX
Amountamountnumberrequired
131.63USD
Statusstatusenumrequired
paid1 of 4 allowed values
Refundedrefundedbooleanoptional
false
#21 to review
OrderorderIdstringrequired
ORD-GJ1OAC
Amountamountnumberrequired
"144.05"
A number arrived as text — it has to be coerced before anything can sum or compare it.expected numbergot string "144.05"
Statusstatusenumrequired
disputed1 of 4 allowed values
Refundedrefundedbooleanoptional
false
#31 to review
OrderorderIdstringrequired
ORD-QVKV9Q
Amountamountnumberrequired
82.03USD
Statusstatusenumrequired
"chargeback"
Not one of the values the schema allows — the model invented this one.expected paid · refunded · disputed · pendinggot string "chargeback"
Refundedrefundedbooleanoptional
true

3 entries

Suggested replysuggestedReplystringoptionalDraft answer for the agent to edit — never sent automatically.

Follow up atfollowUpAtstring | nulloptionalISO-8601 instant, or null when no follow-up is needed.

null

reasoningstringnot in the schema

"The customer mentions two identical charges, so this is a duplicate-billing case rather than a refund policy question."

_internalScorenumbernot in the schema

0.4412

status='ready' with streaming=true — a snapshot from the middle of the stream. Fields that haven't arrived read as 'waiting for tokens', never as missing, and the progress line counts 12 of 16. customer.plan is half-written ('enterp'), and because it is the streamingPath it is NOT flagged: half of an enum member is not a wrong answer. Remove that one prop and the row turns red for a value that is about to be correct.

Structured outputstreaming

12 of 16 fields

SummarysummarystringrequiredOne sentence an agent can read in three seconds.

Customer was charged twice for the annual renewal and wants the duplicate refunded.

Categorycategoryenumrequired

billing1 of 5 allowed values

Prioritypriorityenumrequired

high1 of 4 allowed values

Sentimentsentimentenumoptional

negative1 of 3 allowed values

ConfidenceconfidencenumberrequiredHow sure the model is about the category and priority.

0.820–1

Needs a humanneedsHumanbooleanrequired

true

Refund eligiblerefundEligiblebooleanoptional

true

Tagstagsstring[]optionalFree-form labels from the routing vocabulary.

"duplicate-charge"
"billing"
"stripe"
"vip-escalation"
"eu-region"

5 entries

Namenamestringrequired: Chloe Wisoky
Emailemailstringrequired: [email protected]
Planplanenumrequired: enterp1 of 3 allowed values
Account ageaccountAgeDaysintegeroptional: waiting for tokens

Affected ordersaffectedOrdersobject[]optional

waiting for tokens

Suggested replysuggestedReplystringoptionalDraft answer for the agent to edit — never sent automatically.

waiting for tokens

Follow up atfollowUpAtstring | nulloptionalISO-8601 instant, or null when no follow-up is needed.

waiting for tokens

status='ready', but the model answered in prose: the payload parsed as JSON and is a string, so not one field could be matched. That is stated once at the top instead of drawing twelve identical 'missing' rows.

Structured output

0 of 12 fields · 6 to review

The response is string "Sure! Here is the triage: this looks li…, not an object — no field could be matched.

SummarysummarystringrequiredOne sentence an agent can read in three seconds.: Missing — the schema requires this field.
Categorycategoryenumrequired: Missing — the schema requires this field.
Prioritypriorityenumrequired: Missing — the schema requires this field.
Sentimentsentimentenumoptional: Not provided
ConfidenceconfidencenumberrequiredHow sure the model is about the category and priority.: Missing — the schema requires this field.
Needs a humanneedsHumanbooleanrequired: Missing — the schema requires this field.
Refund eligiblerefundEligiblebooleanoptional: Not provided
Tagstagsstring[]optionalFree-form labels from the routing vocabulary.: Not provided
Customercustomerobjectrequired: Missing — the schema requires this field.
Affected ordersaffectedOrdersobject[]optional: Not provided
Suggested replysuggestedReplystringoptionalDraft answer for the agent to edit — never sent automatically.: Not provided
Follow up atfollowUpAtstring | nulloptionalISO-8601 instant, or null when no follow-up is needed.: Not provided

The same ready payload opened on the Raw JSON tab (defaultView='json'). The two views are a real tablist — arrows and Home/End move between them — and Copy always writes the whole payload, never the visible preview.

Structured output

16 of 16 fields

{
  "summary": "Customer was charged twice for the annual renewal and wants the duplicate refunded.",
  "category": "billing",
  "priority": "high",
  "sentiment": "negative",
  "confidence": 0.82,
  "needsHuman": true,
  "refundEligible": true,
  "tags": [
    "duplicate-charge",
    "billing",
    "stripe",
    "vip-escalation",
    "eu-region",
    "invoice",
    "refund-requested",
    "second-contact",
    "sla-24h",
    "payment-failed",
    "high-value"
  ],
  "customer": {
    "name": "Chloe Wisoky",
    "email": "[email protected]",
    "plan": "enterprise",
    "accountAgeDays": 412
  },
  "affectedOrders": [
    {
      "orderId": "ORD-GYVNTX",
      "amount": 131.63,
      "status": "paid",
      "refunded": false
    },
    {
      "orderId": "ORD-GJ1OAC",
      "amount": 144.05,
      "status": "disputed",
      "refunded": false
    },
    {
      "orderId": "ORD-QVKV9Q",
      "amount": 82.03,
      "status": "refunded",
      "refunded": true
    }
  ],
  "suggestedReply": "Hi Chloe — thanks for flagging this, and sorry for the double charge.\n\nI can see two identical authorisations against your card from the 3rd of March: one for the annual renewal and one that our payment provider retried after a timeout on their side. Only the first one is a real order, so the second has already been voided and the funds should be back with your bank within 3–5 working days.\n\nI've added a note to your account so the retry can't happen again on the next renewal, and I'm keeping this ticket open until you confirm the refund landed.",
  "followUpAt": "2026-03-06T09:00:00.000Z"
}

1,623 characters

status='loading' — the request is out, no bytes yet.

status='empty' — the model answered without filling this schema in.

The model answered without filling in this schema.

status='error' — the stream died mid-object, so there is no payload at all. A different failure from a field being wrong, so it reads differently and offers a retry.

No structured answer

The response stopped mid-object: 1,142 characters arrived and JSON.parse failed at position 1,142. request-id: 7f2c-9ad1

Loading preview…

This component is part of Pro

The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.

Unlock with Pro

{ "summary": "Customer was charged twice for the annual renewal and wants the duplicate refunded.", "category": "billing", "priority": "high", "sentiment": "negative", "confidence": 0.82, "needsHuman": true, "refundEligible": true, "tags": [ "duplicate-charge", "billing", "stripe", "vip-escalation", "eu-region", "invoice", "refund-requested", "second-contact", "sla-24h", "payment-failed", "high-value" ], "customer": { "name": "Chloe Wisoky", "email": "[email protected]", "plan": "enterprise", "accountAgeDays": 412 }, "affectedOrders": [ { "orderId": "ORD-GYVNTX", "amount": 131.63, "status": "paid", "refunded": false }, { "orderId": "ORD-GJ1OAC", "amount": 144.05, "status": "disputed", "refunded": false }, { "orderId": "ORD-QVKV9Q", "amount": 82.03, "status": "refunded", "refunded": true } ], "suggestedReply": "Hi Chloe — thanks for flagging this, and sorry for the double charge.\n\nI can see two identical authorisations against your card from the 3rd of March: one for the annual renewal and one that our payment provider retried after a timeout on their side. Only the first one is a real order, so the second has already been voided and the funds should be back with your bank within 3–5 working days.\n\nI've added a note to your account so the retry can't happen again on the next renewal, and I'm keeping this ticket open until you confirm the refund landed.", "followUpAt": "2026-03-06T09:00:00.000Z" }