One call can erase years of trust.
A crown is already in the patient’s chair, then it doesn’t fit. Margins off. Contact open. The patient leaves without a restoration, and the doctor starts looking for another lab.
When you review the case, the cause is painfully obvious in hindsight: a scan void at the margin and an Rx that left key details unclear. Small problems… that made it all the way through design, production, and shipping.
That’s the story behind the remake that never should’ve shipped.
Most quality failures don’t start at the bench.
They start at intake and nobody catches them until it’s too late.
Examples are familiar:
The problem isn’t that these issues are invisible.
It’s that intake is busy, manual, and inconsistent, so the case moves forward anyway.
Yes, remakes have direct costs, materials, labor, shipping (often $50–$150 per case). Multiply that by volume, and it adds up fast.
But the real damage compounds in three ways:
Every remake jumps the queue and displaces planned work. It creates expedite pressure that ripples through the entire schedule.
Once production starts, you’ve already burned design time, materials, and technician hours—on a case that was doomed from the start.
Dentists can forgive an occasional error.
They can’t forgive feeling like quality is a gamble, especially when the failure happens chairside.
Most labs inspect quality at the end, right before shipping.
But by then, you’re choosing between two bad options:
%%ship a problem %% or %%eat the cost. %%
The smarter moment to check is earlier—before design begins—when issues are cheapest to fix and easiest to clarify. The challenge is scale: opening every scan, reading every Rx carefully, and comparing files across dozens of cases a day is tedious and unrealistic to do perfectly.
So problems slip through, not because people don’t care, but because they don’t have time.
Modern labs are moving toward intake QC that happens automatically:
The goal isn’t perfection.
It’s preventing the avoidable remakes. The ones you could’ve stopped on day one.
If you answer “yes” to any of these, intake QC is already costing you:
It breaks down the real cost of intake blind spots, what “AI QC at intake” actually checks, and the five questions to ask before investing in any portal/QC solution.
Designs you order from EviSmart arrive in your Oqcam already formatted. Named the way your nesting rules expect, with shade and material attached, and pointed at the machine that case belongs on.
The routing is decided per case. An implant case sends the crown to the mill and puck you cut implant crowns on, and the model to the printer you print models on. Different case types, different machines, chosen automatically rather than by a tech working through a dropdown for every file.
The trigger is QC approval. EviSmart designs your cases your way. The same team works on all your cases and learns what a good case looks like to you. Once your case passes our QC, it triggers a greenlight to send the design directly into your Oqcam account in under a minute.
Once the file arrives in your Oqcam, all your CAD/CAM technicians can review the nested design before starting the mill. That final QC step does not change and is not meant to.
Setup is one session. We connect your Oqcam account and agree where each of your products should go, using the routes and materials you have already built there. Nothing new to create, and you only revisit it if something changes.
Automatic sending only works if you trust what is being sent. Once a case is nested it gets cut, and a design that was not right is wasted material.
You choose what flows. During setup we map only the case types you want moving on their own. Anything unmapped never sends. It waits for you exactly as it does today.
Most labs start narrow. Bread and butter work first, night guards and posterior single units, then widen once they have watched it run for a few weeks. The lab that has been live longest started exactly there and has added case types since.
Your approval stays. This removes the file shuffling between design and CAM. It does not remove your eyes from the build.
For labs outsourcing design work the math gets compelling somewhere north of 30 cases a day into nesting, because that is where the handoff stops being an annoyance and starts being a role.
Not touchless design. Touchless handoff. Every step in that chain that requires judgment should keep requiring judgment, and every step that never did should stop requiring a person.
Nesting requires judgment. Confirming a build requires judgment. Renaming a file so software can read it does not, and never did. It was a workaround that quietly became somebody's job.
Nobody pays you to rename files.
