Skip to content
be-human.ai
← Back to the journal

AI by industry

Superintelligence Prep for Dental Labs: Case Tickets and Shipping

Which case-ticket, shade and shipping records a dental lab should standardize now so AI agents can track remakes and due dates reliably.

Be Human typographic cover with the title: Superintelligence Prep for Dental Labs: Case Tickets and Shipping
Conceptual illustration created with AI · Be Human

Superintelligence prep for dental labs means standardizing the records every case depends on before an AI agent works with them: the case ticket, the shade record and the shipping log. When these three record types use consistent fields and one case identifier, an agent can follow a case from prescription to delivery, flag a remake before a due date slips, and tell the production lead what is actually committed. Without that structure, an agent can only summarize free-text notes, and that is where remakes tend to hide.

Key takeaways

  • Standardize the case ticket first, since every shade, shipment and remake record should point back to it.
  • Record shade with the same guide, the same lighting condition and the same notation every time.
  • Log each shipment as its own event with a tracking reference, not as a sentence in the case notes.
  • Link every remake to its parent case with a reason code, so the original due date stays visible.
  • Start agents with read and draft access, and keep shade, material and due date changes with named staff.

Why the case ticket is the unit an agent needs

A dental lab usually receives a prescription through several channels at once: a portal message, an email with photos, a phone call, and a paper form that travels with the box. Each channel creates its own version of the truth. An agent asked when a crown is due will answer from whichever version it can find, and if two versions disagree, it will sound confident about the wrong one.

The fix is unglamorous. Create one case identifier at intake, never reuse it, and treat the case ticket as the record every other event attaches to. Staff can keep working in their current tools. What changes is that the case ticket holds the fields an agent needs, and the other channels feed into it rather than competing with it. The same ticket-first logic applies in other production settings, such as quality records for nonconformances.

Which case ticket fields to standardize first

Start with a short field list and resist adding more until the first list works. For most labs the core set is:

  • Case identifier, created at intake and never reused for another job
  • Submitting practice account and doctor of record, stored as a reference rather than retyped
  • Restoration type, such as single crown, bridge, implant component or removable appliance, chosen from a fixed list
  • Tooth or arch notation, using one system across the whole lab
  • Material and system used, recorded as structured values
  • Committed due date, plus a separate change log that records each change and its reason
  • Current production stage, with a timestamp for each stage change
  • Parent case reference and remake reason code, filled in only when the case is a remake

Patient data needs its own rule. In most cases the case identifier is enough for production tracking, so keep patient names and clinical history out of general fields and limit them to the systems that truly need them. Check the data protection rules that apply where you operate. For Brazilian labs, the guidance published by the national data protection authority, ANPD, is the place to start.

Shade and shipping records that keep due dates honest

Shade problems are a common reason a case returns to the bench, so the shade record should be as structured as the case ticket. Record the shade guide model and version, the shade reading in the lab's standard notation, and whether the reading came from the doctor, a technician or a photo taken under a defined lighting condition. A photo without its lighting condition is hard to compare months later.

Keep the shade record attached to the case, not in a personal folder or a message thread. A shade change requested after a try-in should be logged as an event, so an agent can show what was originally selected and what changed. A practical checklist for each shade record:

  • Shade guide identifier and version
  • Shade reading in the lab's standard notation
  • Photo reference, with the lighting condition noted
  • Name or role of the person who selected the shade, and the date
  • Staining or characterization instructions as fields, with free text kept for remarks only
  • Any later shade change request, logged as a linked event

Shipping is where due dates become real. Record every outbound and return shipment as its own event with the carrier, tracking reference, ship date, expected delivery and delivery confirmation. Note the cutoff time used for same-day departure, because a case that missed the cutoff has a different real due date than the one on the ticket. Returns need the same care: a case sent back for a try-in or a rejected restoration should show the return event, the reason, and the reshipment linked to the remake. Then an agent can answer the question staff ask most often, which is whether the doctor actually received the earlier version. Delivery timing follows the same pattern in other trades, as seen in delivery window records for party rentals.

Remakes and due dates: a step-by-step plan

This sequence can be run with the systems you already use, over about a month:

  • Step 1: Export open cases and remakes from the last three months into one list.
  • Step 2: Check each open case for one identifier and one committed due date. Resolve duplicates by hand and record who made the decision.
  • Step 3: Add a parent case reference and a reason code to every remake, starting with the open ones.
  • Step 4: Replace free-text tooth and material entries with short fixed lists.
  • Step 5: Begin logging shipment events for new cases, then backfill open cases where tracking is available.
  • Step 6: Write down what an agent may read, what it may draft and flag, and which changes need a named staff member.
  • Step 7: Review the agent's flags each week, and adjust the fields that produced false alarms.

Illustrative scenario: A clinic messages a lab to say a crown does not seat correctly. The technician agrees to remake it and notes the new work in the thread, but the original case ticket still shows the first due date. An agent reading only the ticket would report the case as on track. With a parent reference and a remake reason code, the agent sees a new case linked to the old one, the original ship date and a new committed date, so it flags the conflict for the production lead instead of guessing.

Permissions and how Be Human approaches the work

Give the agent read access to case tickets, shade records and shipment events first. Let it draft status messages for the practice and flag overdue or conflicting dates to the production lead. Keep shade changes, material substitutions and due date commitments with named staff, since those decisions carry clinical and production consequences. Use scoped, revocable connections to each system rather than shared logins, and record which record each agent action touched so a person can review it. The [NIST AI Risk Management Framework](https://www.nist.gov/itl/ai-risk-management-framework) is a useful reference for deciding who reviews what.

Be Human's managed approach starts with one role, such as a case-status agent, and defines the memory, tools and approval boundaries it needs before it connects to anything. Managed operations then cover monitoring of the flags, recurring evaluations that compare the agent's conflict reports with what staff found, permission reviews, and controlled changes when a field list or carrier connection changes. The work is remote, in English or Portuguese.

Where to start in your lab

Pick one record type to standardize this month, usually the case ticket, and keep the field list short enough that staff will complete it on a busy morning. The first agent task should be narrow, such as flagging remakes that have no parent link, rather than a broad request to manage the bench. If you want to find the first task worth handing to an agent in your lab, take the free Be Human AI diagnostic.

Frequently asked questions

Do we need new software before we standardize these records? No. Most labs can start with the production system they already use or a shared spreadsheet with locked fields and a change log. The field list matters more than the tool, and an agent can connect later to whatever holds the records, as long as the identifiers stay consistent.

Should patient names appear on the case ticket? Only where production or the clinical workflow requires them. For most tracking, a case identifier and a doctor account reference are enough, and that limits how much personal data an agent can read. Confirm the rules that apply in your country and to your clients before you connect any system.

Who should agree on shade notation? The production lead and the technicians who select shades should agree on one guide, one notation and one lighting condition, and write them down on a single page. Review that page when a new guide or material is introduced. Agreeing on notation is usually faster than repairing inconsistent records after a remake.

Can an agent change a due date after a remake is logged? It should not change a committed date on its own. The agent can propose a new date based on the remake event and the current queue, then route the proposal to a named staff member who confirms it. The original date stays in the change log, so the history of the case remains visible.

Your next step

See where an AI agent fits in your company first.

Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.

Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.

Less busywork. More room for you.

Bring us the work you wish you had time for.

Book a call to try a personalized AI agent free for 7 days ↗Or take the free AI diagnostic →