Teammately Docs
Docs menu

task

Import Case Examples

Bring real product behavior examples into a Project and reconcile them against Project Input Schema before benchmark use.

Import Case Examples

Prerequisites

  • A target Project and permission to work with Cases.
  • The current Project Input Schema, including required input architecture and case-material fields.
  • Source examples with stable provenance or customer correlation IDs.
  • Any files referenced as Case materials.
  • An operator who can resolve ambiguous column mappings and rejected rows.

Before and after

beforeafter
Source rows mix input, prior messages, context, outputs, and notesEach admitted Case has canonical input, named Case materials, and customer-owned attributes
File references are local paths or source-system linksRequired files are Teammately artifacts with processing state
Source identifiers are known only outside TeammatelyCorrelation IDs remain attached without replacing backend-issued Case IDs
No benchmark membership is impliedImported Cases are reusable Project Assets and can be selected deliberately for benchmark work

Import workflow

Import Case examples

  1. Open Project Settings and inspect Project Input Schema. Confirm whether the Project expects plain text, chat, or structured input and which Case materials are required.
  2. Prepare a small representative sample. Separate the Case input from candidate output, human correction, and source-system bookkeeping.
  3. Open the Case import flow from the Project's Cases or Case Pool surface and upload the supported source file.
  4. Map source columns to input, named Case materials, and customer attributes. Do not map candidate output into Case input merely because it shares a row.
  5. Preview the normalized Cases. Inspect conversations, structured values, file associations, empty required fields, and duplicate source identifiers.
  6. Resolve validation and artifact-processing failures before admitting the full collection.
  7. Complete the import, then inspect the admitted Cases in Assets. Confirm Case identity, current version, source context, and material readiness.
  8. Add Cases to coverage or a Benchmark Dataset only after the team has reviewed whether they belong there.

Object and state changes

Import creates reusable Project Cases and can create artifact-processing work for referenced files. Reimporting a synchronized source example can create a new Case version when canonical content changes.

Import does not automatically approve a Case, assign coverage facets, add it to every Benchmark, create a Dataset Snapshot, attach candidate outputs, or declare the Case representative.

Success criteria

  • Every admitted Case matches the current Project Input Schema.
  • Input, conversation history, Case materials, attributes, and outputs remain distinct.
  • Required artifacts are ready or visibly pending; none are silently missing.
  • Source correlation survives without replacing Teammately Case identity.
  • Rejected rows have an understood field-level reason.
  • Benchmark membership remains a separate deliberate action.

Common failure modes

  • Treating every source column as arbitrary metadata instead of mapping the canonical input.
  • Flattening a multi-turn conversation into one unstructured string.
  • Attaching the model's answer as input rather than as external Run output.
  • Relying on filenames or input text as durable Case identity.
  • Importing the full corpus before validating a representative sample.
  • Assuming upload completion means artifact processing and Case admission completed.
  • Sending required context as a Reference Material when it must travel with each Case.

Worked example

Support transcript import

A source row contains a ticket ID, three messages, the assistant's answer, region, and the policy PDF used by the support specialist.

The importer keeps the ticket ID as customer correlation, represents the three-message history as chat input, attaches the PDF to the configured policy_document Case material, and keeps region as an attribute. The assistant answer is not stored in Case input; it can later enter as an external Run output or an accepted target through its owning workflow.

Related reference pages

Reference / Project SettingsProject Input SchemaDefine the canonical input architecture, case-material fields, and accepted artifact formats for project cases.Reference / AssetsCasesUnderstand canonical project cases, their input and materials, and how they become members of benchmark datasets.Concept / Data IntegrationsIntegrationsMove Cases, source materials, external outputs, and benchmark evidence across Teammately's supported product boundaries.Reference / Object ModelCasesUnderstand cases as the situations Teammately uses to represent important AI behavior.

Related troubleshooting pages

Troubleshooting / Recovery LibraryCase upload troubleshootingRepair uploads with rejected rows, missing inputs, incorrect column mapping, or Cases that arrive without usable context.Troubleshooting / Recovery LibraryUnclear CasesRepair Cases that informed reviewers cannot interpret consistently from the supplied input, context, and output identity.Troubleshooting / Recovery LibraryMissing OutputsSeparate a missing managed Run response from an unmatched row in an imported output-only Run.

Source confidence

Code-backed: the active Case, Case Pool upload, mapping, and Project Input Schema sources define the workflow and validation boundary. File limits and exact automated import serialization remain outside this stable UI task until the Public API contract is implemented.

Found something unclear?

Report outdated, unsupported, or confusing docs so we can fix the source page.

Report a docs issue

Continue learning

Related docs

Operating Manual Import and prepare cases Bring cases into the project, conform them to Project Input Schema, inspect materials, and prepare benchmark selection. Project Settings Project Input Schema Define the canonical input architecture, case-material fields, and accepted artifact formats for project cases. Assets Cases Understand canonical project cases, their input and materials, and how they become members of benchmark datasets. Recovery Library Case upload troubleshooting Repair uploads with rejected rows, missing inputs, incorrect column mapping, or Cases that arrive without usable context.
AI context