NIN-CaseExtract-v1
Prepare enterprise support cases for review.
Explore Models in NINXL for available workflows. Supported capabilities and model availability vary.
- reported issue
- Duplicate charge
- follow up
- Agent to investigate and call tomorrow
- resolution
- Not confirmed
From source to something useful.
Illustrative example, authored by NIN. This is not a live model prediction.
- 01 / SOURCE
Support transcript excerpt
Customer: I was charged twice for my order. Agent: I will investigate and call you tomorrow.
- 02 / FOCUSED MODEL
NIN-CaseExtract-v1
Extract service issues and follow-up commitments from enterprise support transcripts and tickets.
Planned capability - 03 / REVIEW
Case draft
Case drafts require analyst review. Missing identifiers and evidence must be collected through the support workflow.
Inspect the example input and output
Support transcript excerpt
Customer: I was charged twice for my order. Agent: I will investigate and call you tomorrow.
Case draft
{
"reported_issue": "Duplicate charge",
"follow_up": "Agent to investigate and call tomorrow",
"resolution": "Not confirmed"
}Prepare enterprise support cases for review.
Extract reported issues, customer requests, commitments and follow-ups from enterprise support transcripts and service tickets for case-management review.
Extract service issues and follow-up commitments from enterprise support transcripts and tickets.
Prepare a structured case draft for an analyst to review.
Separate reported issues from confirmed resolutions.
On-device / private-hosted
Built around your workflow.
On-device execution in NIN products and private hosting for organisational workflows are intended deployment options.
Details after evaluation.
Model size, hardware requirements, supported formats, licensing and measured performance will be documented when available. No release date is announced.
Where could NIN-CaseExtract-v1 help?
Tell us about your workflow, the data it uses and what a useful result would look like. Discuss an evaluation partnership with NIN.
Discuss this model ↗
