Somebody has sent you a proposal. It is well made. It says the words dental and multi-location, it has a diagram of arrows going into a circle, and it promises your front office will stop drowning. You have read it twice and still cannot say which of the jobs in your own building it would do. Not because it is dishonest. Because it never names one.
You own or run somewhere between five and forty practices. There is a central office that bills, a regional manager who moves people between sites, an office manager at each location, and a hygiene column at every one leaking appointments nobody had time to chase. You know which of those jobs eats a person’s week. What you have never been handed is a list with your jobs on the left and something specific on the right.
That is this page. Twenty-five pieces of recurring work inside a dental group, each named in the words your own team uses and assigned to a specialist in a room. Two of the ten specialists come out empty, and that is reported rather than filled in.
Your work is specific, and that is the argument for asking who owns it
A recall interval is not a sales pipeline. A benefit year, a broken bracket, an unseated crown and a spore test have no counterpart in general business either. Anyone who has run a practice knows this in their hands, and it is why a demonstration of an agent writing emails settles nothing. So the objection is right on the facts and wrong about what follows from them. What follows is not that a system must be built for dentistry from the ground up, but that the question has to be put one job at a time, because the unit that can be owned is a job and never a category.
Here is the mechanism, in nouns. The Cabinet is ArkOne’s reference design for an executive agent: one voice a company talks to, and behind it a room of ten specialists, each a name, a model and a set of instructions. A Chair runs the room. A Door decides what may leave it and to whom. A Clock acts when nobody has asked. A Record holds every action with the reason it was taken, and a Mandate on each specialist says whether it may act alone, propose and wait, or escalate. None of those parts knows anything about teeth. What they decide is ownership: which specialist takes a piece of work, what it may do unasked, what it hands to a person, and what it writes down. Dentistry supplies the jobs; the design supplies who owns each and where it stops.
So the test for whether a piece of work can be handed over is not how specialised it is. It is whether a named person does it repeatedly, on a rhythm, from information the practice already holds. Chasing the patients whose recall came and went passes in any dental group in the world. Reading photographs to decide whether an aligner case is still tracking fails, in every group, forever, and that failure is not a limitation waiting on a better model. Which means a vendor who cannot name the specialist owning your recall list will not work it out during a pilot.
Twenty-five jobs, and the ten seats they land in
Suppose you laid out every piece of recurring back-office work a group of your size carries, leaving out the clinical work and the one-off projects, and asked which of the ten specialists would own each. This is what that produces.
| Seat | Jobs it owns | What that looks like here | The part carrying the weight |
|---|---|---|---|
| Operations | Seven | The schedule: chair fill, columns, the huddle sheet, paperwork, lab cases, referrals, supplies | Clock, Table, Watch, Morning Box |
| Finance | Six | The money: breakdowns, pre-authorisations, balances, lapsing members, denials, contracts | Brief, Signature, Mandate, Record |
| Marketing | Five | Patients not currently seen: recall, unbooked treatment, complaints, lapsed patients, benefit room | Door, Order Paper, Brief |
| Counsel | Two | Sterilisation logs complete at every site, no lapsed credential on the schedule | Library, Directory |
| Triage | Two | Callers in pain, and the patient a day after surgery | Switchboard |
| People | One | An associate’s production, traced to the visit | Record |
| Product | One | Aligner patients on their tray schedule | Clock |
| Board | One | One front office across every location | Chair |
| Strategy | None | None of the twenty-five is strategy. Where to open next is not weekly work | Not engaged |
| Talent | None | None is recruitment. Hiring an associate is an episode, not a rhythm | Not engaged |
Exhibit 1. Illustrative. The ten seats of the room against the recurring work a dental group actually carries.
Read the two empty rows first, because they are the finding. Point a room of ten specialists at a real trade and two of them have nothing to do. Putting a job beside Strategy and one beside Talent would have been the thing this page argues against: fitting a business to a diagram.
Operations, Finance and Marketing carry eighteen of the twenty-five, which says less about dentistry than about what a back office is: the schedule, the money, and the patients you are not currently seeing. In Counsel and Triage the work is to notice and route rather than answer. Sorting the people who ring in pain may order the queue and may never tell a caller how long it is safe to wait, a rule in the design rather than a caution in a manual.
The right-hand column carries more than the counts. The Clock owns four, meaning four of these jobs go undone because nobody had time rather than because anybody decided. Filling the chair that opened at eight this morning is the plainest: empty by nine, found in the evening report, lost on the question of who was free to make calls at half past eight. The Door owns three, all patient contact, and it is what stops one patient getting two messages about the same appointment.
One week, invented
Suppose a group of fourteen locations, invented for this exercise, with a central billing office and a regional manager. Nothing here was measured. It is one plausible week, arranged to show which work runs when, what waits for a person, and what the owner reads in the morning.
| Day | What runs unasked | What waits for a person | What lands in the morning brief |
|---|---|---|---|
| Monday | Huddle sheets overnight; recall list worked; short-notice slots offered | Two offers to patients with failed-appointment histories | Three thin columns on Thursday; one site short of a hygienist |
| Tuesday | Breakdowns pulled for midweek arrivals; paperwork sent ahead | One breakdown incomplete, flagged rather than quoted | A denial pattern on one procedure code |
| Wednesday | Payments posted; denials separated; a lab case chased | A denial worth appealing: file assembled, argument left to the billing lead | Two lapsed contracts on active orthodontic cases |
| Thursday | Unbooked treatment worked oldest first; supplies reordered | A supplier change and the spend release, for the regional manager | A credential renewing; a referral with no report back |
| Friday | Post-surgery checks sent; complaint replies drafted; production statements assembled | Every reply to an unhappy patient; every production statement | What was refused this week, and why, per location |
Exhibit 2.
The middle column is the one to spend time on. Every row has something in it, and none of it is there because the software fell short. A short-notice offer to a patient with failed appointments behind them is a judgement about a relationship, so it goes to the office manager. An incomplete benefit breakdown is never turned into a confident number at the desk, because the honest version of that sentence is that the payor did not answer in full. A denial worth appealing has its file assembled by the room and its argument written by the billing lead, because an appeal is a claim about a patient’s care. That column shrinks nowhere over the week. It is the permanent shape of the arrangement rather than a queue being worked down towards autonomy, and a week that showed it emptying would be one to be suspicious of.
What arrives on Friday is not a productivity figure either. It is what the room refused and why, per location, the only evidence that will exist about whether the thing is behaving. Research gathered from the dental office managers’ own community says why the left column matters commercially: tens of thousands of live postings for insurance coordinators and treatment plan coordinators name ringing payors and chasing unscheduled treatment as the duties. That is the left column, currently staffed.
What to ask, once you have the map
Take one job off the list above, from your own week, and put it to the vendor. Not the category, the job.
Which specialist owns chasing lapsed recall, and what may it do without asking anybody? A good answer names a component, says what authority it carries, and says where that authority is written and who may change it. A real vendor answers that the platform handles recall automation and the rules are configurable. Both sentences describe an outcome rather than an owner. The follow-up that separates them: show me where that setting lives, and the last time somebody changed it.
What does it hand to a person, and by what rule rather than by what judgement? You want a named line, not a promise of good behaviour. Whether a patient who asked not to be contacted is ever messaged again sits with the office manager permanently. A vendor who says the system knows when to escalate is telling you the model decides, which is the same as saying nobody has. Ask which decisions are structurally out of reach, then what happens when it is confident and wrong.
What does it write down, and can I read it in front of you? Ask for a week’s record: what was done, what was refused, and the reason attached to each. A dashboard of counts is a report rather than a record, and the difference matters the first time a patient says they were messaged twice, or the first time you have to show that every site’s sterilisation logs are current.
And ask the two empty rows. Ask what in your business it would not touch. A vendor who says it can be pointed at anything has told you nobody has drawn a line, and a design with no line is one where the line gets drawn by whatever happens first. The right answer names things: where to open the fifteenth practice is not on the list, nor is hiring the associate to staff it.
Then say the words central billing office, hygiene column, recall interval, open unit and spore test in an ordinary sentence, and watch whether anybody asks what you mean. A system built for this trade carries those words because the jobs it owns are made of them.
Start from the list rather than the software, because the list is yours and already written. You do not need a vendor to tell you which work in your group eats a person’s week. What the map adds is a name for who would own it, a rule for where it stops, and a language for asking. Take one job. Ask who owns it. If the answer is a component and a setting, you are talking to somebody who has built this. If it is the outcome again in different words, you have learned that in the first ten minutes rather than the sixth week of a pilot.
Asked plainly
What back-office work in a dental group can an AI agent actually own?
The recurring work a named person does every week and would hand over if they could: chasing lapsed recall, verifying benefits before a patient sits down, offering a chair that opened this morning, following up treatment that was agreed and never booked, posting payments and spotting denials, chasing a case that has not come back from the lab, writing the huddle sheet overnight. What it does not own is any clinical judgement, and any decision about money that a person has to be able to defend afterwards.
Is dental work too specialised for an AI agent to be useful?
The work is genuinely specialised, and that is the reason the question has to be asked job by job rather than about the software as a whole. A recall interval, a benefit year, a broken bracket and a spore test are not general business objects, so a system that cannot say which specialist in it owns a recall list is not going to acquire that answer during a pilot. Ask which job it takes and what it hands back.
What should the owner of a dental group ask an AI vendor?
Name a job from your own week and ask who inside the system owns it, what it may do without asking anybody, what it hands to a person and by what rule, and what it writes down about having done so. A vendor whose system has a real answer will name a component and a setting. A vendor whose system does not will describe the outcome again in different words.