The personal agent knows the request
It keeps the conversation, understands the person’s preferences and asks about choices that still need a decision.
People tell their personal AI agent what they need. Opalforce’s ten built dental agents handle the practice side. Setup connects their capabilities to your team’s tools, rules and practice management system.
The first priority: an appointment that is confirmed in the actual practice schedule.
All ten agents are built. PMS compatibility, personal-agent access and each connected workflow are assessed and tested for your practice.
“Book a cleaning next week after 3 pm at my usual dental office.”
Opalforce dental capabilities
The right access. Your booking rules. A supported action.
Your PMS & back office
The appointment must exist in the practice system.
A clear division of work
It keeps the conversation, understands the person’s preferences and asks about choices that still need a decision.
Its agents apply your practice rules, carry out permitted work through configured connections and bring exceptions to your team.
An appointment, update or other completed action must be checked against the system your team relies on.
The connection plan
Reliable access to your practice system comes first. The rollout begins with a supported booking workflow, then enables the other built agents as their connections are tested.
Review your PMS, locations and available integration access. Identify exactly which actions a connection can support.
Define appointment types, providers, opening hours and who can approve each action. Your team stays in control.
Check patient identity, find a suitable time, make the booking and confirm that the appointment is recorded correctly.
Add changes, cancellations and back-office work as each capability is tested for your practice.
Deploy the built agents in stages: verify rescheduling and cancellation, then enable intake, insurance, treatment coordination, recall, claims, collections and practice reporting. Clinical Notes AI prepares drafts for clinician review. Each workflow has its own access requirements and readiness checks.
The connection is designed around permissions. Asking an agent to help should never give it unrestricted access to the practice.
Verify who they are, show only their permitted information and act within their instructions. A family member’s access needs its own permission.
Match access to each person’s role and location. Keep clinical, financial and administrative responsibilities clear, with a person handling exceptions.
Personal-agent access and practice-system access are both checked before enabling a workflow.
Before you connect
Compatibility needs to be assessed for your particular system, version, location and integration access. All ten agents are built; compatibility and deployment are assessed separately for each practice.
The direction is to let people use their own approved personal agent. Opalforce provides the dental capabilities and the practice connection. Website chat, phone and a staff workspace can also provide access where those channels are configured.
Agent support must be checked alongside the practice connection. A personal agent needs an approved way to request actions and receive only the information it is permitted to see. Naming a personal agent does not establish compatibility.
The intended experience is to show a request as pending or explain what needs attention. A booking should only be described as confirmed after the practice system has been checked. Your team handles unsupported requests and unresolved exceptions.
Explore all ten built dental AI agents and their capabilities. A demonstration is separate from a live PMS connection. We can discuss your practice systems and the right starting workflow before agreeing on a deployment.
Let’s start with your systems
Tell us which PMS you use and where your team needs help. We’ll scope the connection and the first useful workflow.