Recipe catalog / resolution-check
Check reported resolution
Does message establish that the customer reports issue as resolved?
You need to know whether the customer reports that an issue is resolved.
Explore this recipe interactively ยท Source and implementation guide
Use resolution-check in TypeScript
Install with npm install jev-recipes. Requires Node.js 22.9 or newer and ES modules. Set TYPESAFE_API_KEY in your server environment for live calls, which send input to TypeSafe and use API quota. See the installation guide.
import { resolutionCheck } from 'jev-recipes/resolution-check';
const result = await resolutionCheck({
"issue": "The customer cannot sign in.",
"message": "The reset worked. I can sign in now."
});
console.log(result);
Input contract
| Field | Type | Needed |
|---|---|---|
| issue | string | Required |
| message | string | Required |
| context | string | Optional |
| minConfidence | number | Optional |
Full input and result schemas
{
"input": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"issue": {
"type": "string"
},
"message": {
"type": "string"
},
"context": {
"type": "string"
},
"minConfidence": {
"type": "number",
"minimum": 0,
"maximum": 1
}
},
"required": [
"issue",
"message"
]
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"model": {
"type": "string"
},
"usage": {
"type": "object",
"properties": {
"input_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
},
"output_tokens": {
"type": "integer",
"minimum": 0,
"maximum": 9007199254740991
}
},
"required": [
"input_tokens",
"output_tokens"
],
"additionalProperties": false
},
"status": {
"type": "string",
"enum": [
"ready",
"review"
]
},
"verdict": {
"type": "string",
"enum": [
"resolved",
"unresolved",
"unclear"
]
},
"confidence": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"probabilities": {
"type": "object",
"propertyNames": {
"type": "string",
"enum": [
"resolved",
"unresolved",
"unclear"
]
},
"additionalProperties": {
"type": "number",
"minimum": 0,
"maximum": 1
},
"required": [
"resolved",
"unresolved",
"unclear"
]
}
},
"required": [
"model",
"usage",
"status",
"verdict",
"confidence",
"probabilities"
],
"additionalProperties": false
}
}Saved example result
This hand-authored response demonstrates the contract. It is not a model accuracy measurement. Run it without an API key: npx jev-recipes demo resolution-check.
{
"model": "demo-fixture",
"usage": {
"input_tokens": 0,
"output_tokens": 0
},
"status": "ready",
"verdict": "resolved",
"confidence": 0.96,
"probabilities": {
"resolved": 1,
"unresolved": 0,
"unclear": 0
}
}
Evaluation evidence
No verified live accuracy measurement is available. Evaluate representative cases before using this decision in your workflow.
Use the evaluation guide to measure this decision on your own labeled cases.
Limitations
- Interprets the customer report. It does not verify the system state, close a ticket, or treat courtesy alone as resolution.
Related recipes
- issue-recurrence: Use issue-recurrence to distinguish a first occurrence, an ongoing issue, and a return after reported recovery.
- step-complete: Use step-complete to assess evidence against a supplied completion condition.