LunaLuna

Ask once. Follow the whole job.

Luna coordinates Omnira Dental’s five agents. Ask about the book, billing or tomorrow’s work, and follow each action through the permissions your practice sets.

Invite-only · Built around your practice’s permissions

See the workflow
ILLUSTRATIVE WORKSPACE
LunaStellaRelay
CARLA · OFFICE MANAGER

Who hasn’t confirmed for tomorrow?

LUNA · COORDINATED REQUEST

Coordinated request

Permissions checked
Prepared by agents. Controlled by your team.

The work behind the work

A request such as “cancel the appointment and let the patient know” sounds like one task. In practice it touches the schedule, patient communication, billing preparation and the production forecast.

When those tasks live in different systems, staff have to complete each one and check that the others agree. A reminder sent after a cancellation creates another call to fix the confusion. A report pulled before the change may already be out of date.

Luna coordinates the agents that own each part of the work. Staff ask in plain language. The request becomes ordered steps, with permission checks and a clear account of what happened. A question can remain read-only; an action still needs authorization.

An assistant across your dental practice

01

Ask the operational question

Ask who has not confirmed tomorrow, who is booked at 2 PM, or how production is tracking this week. Luna routes to the agents that hold the information and returns an answer within your role’s access.

02

Break a request into steps

A cancellation request reaches Stella before the related patient message is sent. Billing preparation stops and the forecast updates in the right order. Staff do not have to translate the same request into separate instructions for every agent.

03

Check the current status

Luna checks the appointment state when each step runs. The sequence should use the current record, so an earlier assumption does not cause a reminder to go out for a visit that has been cancelled.

04

Keep the agents in scope

Stella works on scheduling, Vera works on billing, and Aria works on clinical paperwork. Luna coordinates their tools and context. Coordination does not give every agent access to every part of a patient’s record.

05

Escalate a conflict

A coverage gap on a booked procedure is flagged for staff; the appointment is not automatically cancelled. A clinical concern is routed to the provider for review. Conflicts become decisions for the appropriate person.

06

Respect the person asking

The dashboard and specified mobile experience provide ways to ask. A front desk user cannot obtain clinical notes by phrasing the request differently. The same role and action permissions apply through Luna as through the underlying workflow.

A cancellation across four agents

Carla asks to cancel Mrs. Johnson’s appointment and let her know. This fictional sequence pauses at a human review before the action continues.

ILLUSTRATIVE WALKTHROUGH05 / 05
ILLUSTRATIVE WORKSPACE
Relay
CARLA · OFFICE MANAGER

Who hasn’t confirmed for tomorrow?

LUNA · COORDINATED REQUEST

Patient notified

Then
Prepared by agents. Controlled by your team.
  1. Carla identifies the appointment and asks for cancellation and notification. Luna determines the dependent work.

  2. If cancellation is supervised, the authorized person reviews it. The remaining work waits for the decision.

  3. Stella cancels the visit under the approved action. The opening can be offered to suitable waitlist patients.

  4. Vera stops billing preparation connected to the cancelled appointment. Financial history is not erased.

  5. Relay sends the appropriate message. Otto’s forecast updates, and Luna reports the completed work and any remaining decision.

An answer is different from permission

An owner can ask how production is tracking. A provider can ask about their next patient. A billing coordinator can ask about claims waiting on a payer. Each request should return the information that role is allowed to see.

An action adds another check. Permission to view an appointment does not necessarily include permission to cancel it. Luna must respect the action setting even when the person asks in a single sentence. Supervised work still pauses for a reviewer.

If information is missing, the useful answer is to identify the gap. Staff can resolve the underlying record or ask the responsible person. Luna should not turn an absent value into a confident answer, especially when a patient, payment or clinical decision depends on it.

Prepared first. Permission before action.

Your practice chooses Autonomous, Supervised or Off for each action type. New practices and newly enabled capabilities begin in Supervised mode for about two weeks. Your team approves or rejects recommendations.

A readiness report shows accuracy by action. The owner decides which actions to promote. Some work can remain supervised while other routine actions run autonomously.

The AI interprets and drafts. Tested software performs record changes after permission checks. Every agent action is logged, and supervised work shows what was prepared and why. Clinical decisions and provider signatures stay with clinicians.

The agent prepares the action. An authorized person reviews, edits, approves or rejects it before the record changes.

Interactive explanation · does not change product settings

Read-only questions

Your role and location access determine the information Luna can return.

Compound requests

Each underlying action keeps its own permission and approval requirement.

Conflicts

Coverage issues go to staff and clinical concerns go to the provider; the schedule is not changed automatically.

What we are designing toward

Targets, stated plainly.

These are product design targets, not measured practice results or promised outcomes.

  • 15+ admin hours back each week is the design target.

Where your team takes over.

  • Luna does not bypass a role restriction or promote a supervised action because it was requested in chat.
  • Luna does not diagnose, give clinical advice or decide how a provider should treat a patient.
  • When data is missing, the answer should say so. A plausible invented answer is not practice information.

Set it up around your practice.

01

Start with recurring questions

Choose the questions your team asks most often about the schedule, confirmations and production.

02

Check roles

Verify each person’s location access and action permissions before trying compound requests.

03

Inspect the sequence

During training, review the planned work, approvals and completed actions. Confirm mobile voice input and assistant naming separately.

Practices own their data and can export it. Review migration scope, enabled features and the BAA with the onboarding team. See security and data access, integrations and current pricing for the wider platform.

The connected team

Follow the handoff.

Before you ask for an invite

The practical questions.

Scope and availability should be confirmed for your practice during onboarding.

Is Luna a chatbot?

Chat is one way to ask. Luna’s product role is coordinating the five agents, including ordering work and respecting the permission checks on each action. A conversation can lead to an answer or authorized work.

Can Luna see every clinical note?

Only when the requesting role has access to that clinical information. Front desk users cannot use Luna to get clinical notes outside their permissions.

What if an action needs approval?

It remains supervised. The authorized reviewer must approve the prepared action before execution. Combining several steps in one request does not remove a review requirement.

What happens when insurance conflicts with a booking?

The appointment is flagged and the desk is informed. Staff decide what to do. Luna does not treat an insurance issue as permission to automatically cancel the visit.

Can we rename the assistant?

The specification allows a practice-specific assistant name, but presentation and launch availability need confirmation. Luna is the coordinator name used on these pages.

Is our practice data used for model training?

Omnira Dental’s specified privacy commitments require vendors touching patient data not to train models on practice data. Practices own their data. Review the BAA and data arrangements during onboarding.

Industry references.

These references inform the industry context. They do not verify Omnira Dental’s product capabilities or design targets.

  1. Dental practice research ADA Health Policy Institute · Undated / maintained resource

    Research on staffing, ownership and practice structure. Research index; accessed October 29, 2026.

Omnira Dental · Invite-only

Bring your workflow to the conversation.

Tell us where the work gets stuck. We’ll review your practice’s setup, the enabled features and the approvals your team needs.