# Your front desk copilot. Less admin to juggle.

> Coming soon. Find appointment times, prepare booking changes and patient messages, and check what is outstanding for an arrival. Your team reviews and confirms each change.

- **Agent:** DappleAI Front Desk Agent
- **Canonical:** https://dappleos.com.au/dapple-ai/frontdesk-agent

## Agent scope

### Keep routine front-desk work moving without hiding what changes.

#### Connected DappleOS context

- Check the live diary, locations, rosters, timeblocks and room availability
- Use booking history and learned time preferences within clinic rules
- Surface waitlist entries, outstanding forms, patient flags and visit status
- Compare usable stock and expiring units with booked treatments and historical use
- Keep messages, invoices, memberships, permissions and audit context connected

#### What the agent handles

- Propose an eligible booking, reschedule or cancellation
- Run the arrival checklist and prepare visit-status updates
- Maintain rosters, timeblocks and waitlist entries without hard deletion
- Forecast tomorrow's stock needs and show the supporting working
- Prepare a draft purchase order for supplier review
- Read back every patient message, form link or payment link before it is sent

Every supported write follows propose, plain-English read-back, explicit confirmation and execution. Overlap warnings require another explicit confirmation to override. Money movement, refunds, point-of-sale transactions and clinical decisions stay outside the agent.

## Workflow

### Move the appointment without retyping the story.

Ask to move a patient’s appointment and let them know. Front Desk Agent uses the connected booking details to find an alternative, update the diary and prepare the patient message. Your team reviews the move and the exact message as separate decisions, then sees each completed result in DappleOS.

#### Step 1: Ask for the front-desk task

Describe a booking, waitlist, check-in, roster, stock, ordering or patient-administration task in natural language.

#### Step 2: Check the connected context

The agent resolves the relevant patient, clinic rules, diary, stock or membership context and surfaces conflicts before proposing a change.

#### Step 3: Review the exact action

A plain-English read-back shows what will change, including the exact patient message or draft-order details when relevant.

#### Step 4: Confirm, execute and verify

Only an explicit yes releases that exact action. The updated diary, message thread, waitlist entry or draft order then remains visible in DappleOS.

## Reporting and evaluation

### Keep the resulting clinic state and audit trail in view.

Front Desk actions finish in the connected DappleOS surface where the team already works: the appointment book, message thread, waitlist, patient record or draft purchase order. Stock forecasts show the booked treatments, historical usage and usable units behind the answer. Each interaction records the clinic, agent, tools used and outcome, while practice-manager reads can surface end-of-day cash-up and membership payment failures without moving money.

- Did the agent show the clinic rules, availability or stock evidence behind its proposal?
- Did the read-back state exactly what would change and wait for an authorised confirmation?
- Can the team verify the result in the appointment book, message thread, waitlist, patient record or draft order?

Review each operational result where it lands in DappleOS, together with the proposal, confirmation and audit context. This keeps evaluation grounded in completed clinic activity rather than unsupported efficiency claims.

## One connected platform

### Find the details once. Keep the work connected.

The Front Desk Agent can work across the appointment book, rosters, waitlist, patient administration, messages, forms, payment links, stock and draft ordering because those workflows already share DappleOS context. The team does not need to copy a request into a separate chatbot or re-enter the resulting action into the platform.

#### May reduce

- Keeping a patient waiting while staff search the diary, roster and booking rules for a suitable time
- Moving an appointment in one screen, then retyping the same details into a separate patient message
- Discovering an outstanding form or arrival task only after the patient reaches the front desk
- Finding a product shortage when tomorrow's treatment list is already under way

#### Does not replace

- Clinic rules, permissions and authorised human confirmation
- Clinical suitability or treatment decisions
- Point-of-sale transactions, refunds or membership charging
- Supplier review and sending of purchase orders
- Human handling of sensitive, exceptional or escalated conversations

## Safeguards

### Every write waits for a yes

The agent proposes the action, reads it back and executes only after explicit confirmation from an authorised user.

### Conflicts remain visible

Appointment overlaps and duplicate-patient warnings surface before the change, with an additional confirmation required to override.

### Money movement stays outside

The agent can prepare a payment link or read payment context, but it cannot run point of sale, issue refunds or charge memberships.

### Administrative boundaries hold

The agent coordinates front-of-house work, logs the tools and outcome, and does not diagnose, assess suitability or make treatment decisions.

## Related DappleOS workflows

- [Concierge Agent](https://dappleos.com.au/dapple-ai/concierge-agent): Coming soon. Preview the planned patient-conversation and staff-handover workflow.
- [Inbox and messaging](https://dappleos.com.au/features/inbox-messaging): Keep patient conversations and staff follow-up in one shared clinic inbox.
- [Digital drug book](https://dappleos.com.au/features/digital-drug-book): Connect medicine stock, batch and expiry records to the clinic workflow.

## FAQs

### What work can the Front Desk Agent handle?

Front Desk Agent is coming soon and is not currently available to customers. The planned workflow covers appointment-book, waitlist, roster, check-in, patient-administration, messaging, stock and draft-ordering work, subject to clinic rules, permissions and staff confirmation.

### Does it change appointments automatically?

No. It proposes the booking, reschedule or cancellation, reads back the exact details and waits for an authorised staff member to confirm. If a follow-up message is needed, that message is a separate proposal with its own confirmation.

### How does it avoid double-booking?

It uses the same DappleOS availability and clinic-rule context as the appointment book. An overlap warning appears before execution and requires a second explicit confirmation if an authorised user chooses to override it.

### Can it tell us whether we have enough stock for tomorrow?

It can compare tomorrow's booked treatments with the clinic's historical product use and usable stock after expiring units are considered. It shows the working and says when there is not enough usage history to make a forecast.

### Can the Front Desk Agent order or charge anything?

It can propose a purchase order, but the confirmed order is created as a draft and is not sent to the supplier. It cannot run point of sale, issue refunds or charge memberships; money movement stays in the main DappleOS workflow.

### What can it send to a patient?

It can propose an SMS, email, portal message or form link. The exact content is reviewed before a confirmed send. It can also create an invoice payment link; sending that link to the patient is a separate message proposal.

### How is the Front Desk Agent different from the Concierge Agent?

The Front Desk Agent works with authorised clinic staff inside DappleOS to operate administrative workflows. Concierge Agent helps patients with enquiries and bookings, with its own identity, handover and patient-confirmation safeguards.

### What will we see in a demo?

Front Desk Agent is coming soon. Bring the appointment, waitlist or stock tasks you want to discuss. We can explain what is available today and discuss the planned Front Desk Agent workflow and its availability.

## Bring the front-desk tasks your team handles every day.

Discuss your clinic’s workflow, the features available today and the planned Front Desk Agent. Front Desk Agent is coming soon.

[Book a demo](https://dappleos.com.au/sales-call)
