VA vs. Employee vs. Automation: A Per-Task Decision Framework

This framework answers which resource type is correct for a given task. It is applied per task, not per role. The most common error is applying it to a whole job and asking “should this person be a VA or an employee?” Most jobs in a dental practice should be split across resource types: part of the work belongs to automation, part to a VA, part to in-house staff, and part to an outsourced specialist. The question is not which category the job belongs to. The question is which category each component of the job belongs to.

The five decision inputs

For each candidate task, score or assess five inputs:

1. Physical presence required (yes/no)

Anything requiring in-person patient contact, clinical proximity, or physical access to a space or machine is disqualified from remote solutions. This input eliminates options before any other scoring occurs.

2. Clinical judgment required (yes/no)

Anything requiring licensed clinical assessment, diagnosis, treatment recommendation, or direct clinical communication belongs to licensed clinical staff regardless of volume or exception rate. Volume and cost arguments do not override this gate.

3. Exception rate (low/medium/high)

How often does the standard process not apply? A low exception rate means the workflow follows its rules the large majority of the time. A high exception rate means human judgment is frequently needed, and automation will be unreliable for the primary case, not just the edges.

4. Volume (low/medium/high)

How many instances per week or month? Volume combined with exception rate determines whether automation is viable. High volume with low exception rate is the automation sweet spot. Low volume with low exception rate may not justify the implementation cost.

5. Relationship dependency (low/high)

Does this task depend on an ongoing personal relationship with the patient, the team, or an external party that requires familiarity and trust built over time? Some patient communication is effectively relationship maintenance; collapsing it to automation can produce technically complete but clinically damaging outcomes.

The recommendation logic

If physical presence is required: in-person employee.

If clinical judgment is required: licensed clinical staff, regardless of other factors.

If exception rate is low and volume is high: automation is the primary resource.

If exception rate is low and volume is also low: automation if inexpensive to implement, otherwise deprioritize.

If exception rate is high and a mature external specialist market exists and the task is isolated: outsourced specialist.

If exception rate is medium or high (but not so high as to require a specialist): automation handles the base case, a VA handles exceptions.

Otherwise: VA.

The task-splitting method

A named Dentist Circle method worth publishing explicitly, because the failure mode is common enough to warrant a named alternative.

Appointment confirmation is the worked example. A practice that asks “should we automate confirmations or have the VA do it?” is asking the wrong question. Here is what the correct task map looks like:

• Touch 1 (text at 7 days out): automation.
• Touch 2 (text or email at 2 days out): automation.
• Touch 3 (live call for unconfirmed high-value appointments): VA.
• Slot backfill decision when a cancellation occurs: VA.
• Policy decision on chronic no-shows: owner.

One task, four resource types. The automation handles volume: it sends the same message to the same patient population at the same interval, every time, without variation. The VA handles exceptions and high-stakes situations: an unconfirmed patient with a two-crown appointment three days out is not a situation you want to resolve with a text message. The owner handles policy: what constitutes a chronic no-show, what the consequence is, and when to break pattern for a specific relationship.

Collapsing these into one resource produces two failure patterns. A person doing repetitive low-stakes confirmation texts is doing work a machine can do at a fraction of the cost and with no variability. A machine trying to decide whether to offer an appointment to the patient who has cancelled three times is making a judgment call it cannot make. Neither version is running well. Both are running at the wrong layer.

Apply the same logic to any task. The framework does not produce a single answer. It produces a task-level map. Each map looks different for each practice because the exception rates, volumes, and relationship dependencies are different.

Cost comparison rules

A defensible cost comparison uses fully loaded cost per unit of completed work, not hourly wage comparisons. For each resource type, the comparison must include the following:

For in-house employees: base wage plus all employer taxes and costs, plus benefits costs, plus recruiter or onboarding costs, plus the cost of turnover if the position churns. [EXPERT REVIEW: employer cost components vary by jurisdiction. This framework does not constitute employment or tax advice.]

For VAs: the engagement rate, plus the practice’s internal management overhead (typically 1 to 4 hours per week, depending on maturity of the engagement), plus onboarding and training costs, plus the cost of any technology required that the VA does not already have access to.

For automation: implementation cost amortized over the expected active period, plus maintenance and monitoring overhead, plus failure-mode cost (what happens when it stops working and nobody notices).

Comparing a VA hourly rate to an employee hourly wage is the standard industry dishonesty, and it should be named as such. The VA rate looks expensive per hour compared to a minimum-wage employee only when the comparison excludes employer taxes, benefits, paid time off, and the cost of the hours the in-house employee spends on tasks outside their primary function. The correct comparison is completed work units per dollar, not hours per dollar. A VA who handles 40 insurance verifications per week at a fixed weekly cost is not competing with the receptionist’s hourly wage. She is competing with the full loaded cost of the receptionist’s time on that specific function, which includes everything the receptionist could have been doing instead.

One additional factor the hourly comparison always omits: the cost of work currently not being done at all. If no one is working the lapsed patient list or the unscheduled treatment report, the opportunity cost of that undone work is not zero. It is the value of the work not completed. Any resource cost compared against zero produces the same answer: the resource looks expensive.

When to choose the outsourced specialist

The outsourced specialist is not the same as a VA. The model applies when the function is a single, specialized discipline, a mature external market exists with established pricing and accountability structures, and the practice wants function-level accountability rather than task-level management.

Revenue cycle outsourcing and dental bookkeeping are the most common dental examples. The outsourced specialist takes ownership of a defined outcome (AR collected, books closed) rather than a defined set of tasks. The trade-off: less day-to-day process visibility, and a more complex data relationship when patient records are involved.

The framework applies here as well. If a task within a broader job function requires an outsourced specialist, extract that task from the job and route it correctly. The rest of the job follows its own routing through the logic above.