AI Agents for Orthodontic Offices: Treatment Updates and Aligner Reorders
How an orthodontic office can hand treatment updates, reminders and aligner reorders to an AI agent, and which clinical messages must stay with the team.

An AI agent for an orthodontic office can handle the repetitive messages around treatment: visit reminders, tray change timing, progress check-in forms, delivery questions and aligner reorder requests. It works only when it has an approved copy of the treatment plan, a defined memory of each patient's current stage, and written rules for what it may never say. Every answer about pain, fit, damage or tooth movement stays with the clinician.
Key takeaways
- Give the agent reminders, reorder intake and logistics questions. Keep clinical judgment with the clinician.
- Tie every message to an approved treatment plan version and the patient's current stage.
- Write a hard list of messages the agent never sends, then test the agent against that list before launch.
- Route any report of pain, poor fit, a cracked tray or missed wear to a human queue with a named owner.
- Start with one workflow, one observable success criterion and a fixed review schedule.
What the front office and clinical team repeat
Orthodontic treatment is long, and most of the friction sits between visits. A patient wearing clear aligners moves through a sequence of trays, each worn for a period the clinician has set, with check-ins at intervals the plan defines. Between those points the office fields the same questions again and again: when is my next visit, when do I switch trays, my tray cracked, can you send a new set, where do I pick up my records, is it normal that my teeth feel sore?
Some of these questions are administrative and follow written rules. Others depend on clinical judgment that no agent should make. The administrative share is repetitive, and it is where an agent can take real work off the team. Front desk staff reconcile calendars, chase confirmations, collect the same reorder details twice and copy tray numbers between systems. When the information arrives complete at first contact, the clinical team reviews a reorder in one pass instead of several.
Which tasks can go to the agent
Use one test for each task: could a trained front desk employee do it using only the approved plan and the office's written policy? If the answer is yes, the task is a candidate. If the answer depends on what a tooth is doing, it is not. In practice, the candidates usually look like this:
- Reminders for booked visits, sent from the calendar the office already uses, with approved wording.
- Reorder intake: collecting the patient's name, date of birth, current tray number, the reason for the request and the shipping address, then creating a request for clinician approval.
- Logistics: office hours, how to reschedule through the approved booking route, where to pick up records or retainers, and what to bring to a visit.
- Structured progress check-ins: asking fixed questions about wear hours and remaining trays, with answers recorded for the clinician.
- Contact and address changes, routed to the front desk for verification before they are saved.
- Handoff summaries: a short, factual note for the clinician listing what the patient asked and what the agent did.
A similar split between routine messages and clinical judgment appears in recall work, which is covered in dental office recalls and insurance admin.
Messages the agent must never send
Some messages stay off-limits however the question is phrased. Write them down as a never-send list, and reference that list directly in the agent's instructions and in its test cases.
- Any diagnosis, any interpretation of a photo, scan or intraoral image, and any statement that a tooth is or is not moving as planned.
- Advice to skip, shorten, extend or change wear time, or to move to a different tray than the one the plan lists.
- Reassurance that a symptom such as pain, pressure, gum irritation or a loose attachment is normal.
- Approval of a reorder, a plan change or any exception the clinician has not signed off.
- Promises about results, completion dates or outcomes beyond what the approved plan states.
- Answers about medications, medical conditions or whether treatment is safe during pregnancy or another health event.
- Any content from another patient's record, or details about a family member's treatment without verified authorization.
Patients sometimes paste text that tells an assistant to ignore its rules. The agent must treat such text as untrusted input. The OWASP guidance on prompt injection prevention describes layered defenses, including limiting what the agent can access and what actions it can take, so that a clever message cannot grant permissions the office never gave.
A reorder workflow the office can review step by step
The reorder workflow is the most common first task, so it is worth writing out in full. Each step should be visible to the clinical team, and each should have a clear stop condition.
- Confirm identity with the details the office already uses, and stop if they do not match the record.
- Read the current stage and tray number from the approved plan version, not from the patient's description.
- Ask what happened: a lost tray, a cracked tray, a change in fit, or a replacement that the plan already schedules.
- If the patient reports pain, bleeding, a cracked or damaged tray, a loose attachment or any change in bite, stop the workflow and send a review alert with the conversation attached.
- If the request matches the plan, create a reorder request with tray number, reason and shipping details for clinician approval.
- Tell the patient what happens next in the office's approved wording, including who reviews the request and how they will hear back.
- Log the request, the reviewer and the final decision so the sequence can be audited later.
Illustrative scenario: a patient writes in the evening that a tray cracked while eating and asks for the next set to be sent. The agent confirms identity and reads the current stage from the plan. Because the patient reports a crack, it does not create a standard reorder. It alerts the clinical queue, tells the patient that a team member will review the damage and confirm next steps, and avoids saying whether the tray still fits. The clinician then decides whether to send a replacement, adjust the plan or see the patient sooner.
What the agent needs in memory and permissions
An agent is only as accurate as the information it can reach. For an orthodontic office, the useful memory is narrow and current: the approved treatment plan version, the active stage and tray count, the next scheduled visit, exceptions the clinician has noted, communication preferences and consent on file, and the patient's preferred language, English or Portuguese. Answering from approved documents, rather than from general knowledge, keeps the agent quoting the office's own policy. When the clinician revises a plan, the new version must replace the old one everywhere the agent reads from.
Permissions should be narrower than a staff member's. The agent can read the plan and the calendar, write to the review queue and the message log, and nothing more. It should not edit clinical notes, approve orders, change a plan or open billing records. The OWASP authorization guidance is a useful checklist here, because each action should be checked against the role the agent holds and not against whatever the system happens to allow. The NIST AI Risk Management Framework gives a shared vocabulary for mapping these risks and deciding who owns each control. The same discipline applies to other intake-heavy practices, such as chiropractic intake and visit recalls.
How Be Human approaches this in practice
Be Human starts with one role rather than the whole front office. In a first engagement, the team defines the workflow, the memory and tools the agent needs, the approval boundaries including the never-send list, and one observable success criterion. Managed operations then cover monitoring of conversations against those boundaries, recurring evaluations of the agent's answers, integration maintenance when the scheduling or messaging system changes, permission review, and incident response when a message falls outside the rules. The practice keeps every clinical decision. The agent keeps a narrow, documented job.
How to measure the workflow and keep it safe
A success criterion has to be observable, or the team will argue about it at every review. Useful measures for a reorder workflow include how often requests arrive with complete information, how many are sent back to the patient for missing details, whether every review alert fired when it should, and how many never-send violations appear in sampled conversations, with zero as the target. Keep a trace of each conversation, tool call and handoff, so a manager or clinician can reconstruct what happened. The OpenTelemetry observability primer describes the basic ideas of traces, metrics and logs that make this possible. Rerun the evaluation set after every change to plan templates, messaging rules or sending software, and retire test cases that no longer reflect how patients actually write. If you want to find the first task in your office worth handing to an agent, take the free Be Human AI diagnostic.
Frequently asked questions
Can an AI agent send aligner reorder requests on its own? It can collect the details, check them against the approved plan and create a request in the clinical review queue, but a clinician should approve any order that raises a clinical question. For routine, plan-matched replacements, the clinician can pre-approve a written rule, and that rule should be tested and reviewed like any other control. Anything involving damage, fit or symptoms goes to a person.
Does the agent need access to the full patient chart? No, and it should not have it. It needs the current plan version, the active stage and tray count, the calendar and the consent preferences. Narrow access limits how much sensitive information a misdirected message or a prompt injection attempt could expose.
What should happen when a patient reports pain or a broken tray? The agent should stop the standard workflow, tell the patient in approved wording that a team member will review the message, and send an alert to the clinical queue with the full conversation attached. It should not offer a home remedy, a reassurance or an estimate of when a replacement will arrive. The practice should set the response expectations for that queue, not leave them to the agent.
Can the agent work in Portuguese as well as English? Yes, Be Human services run in English and Portuguese, but the never-send list and workflow rules must be written and tested in each language. Translating the words is not enough, because patients describe symptoms and damage in different ways across languages. Evaluate the agent with real examples in both languages before it handles live messages.
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.


