> ## Documentation Index
> Fetch the complete documentation index at: https://q.odontox.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Appointment Queue

> Approve pending bookings, track today's schedule, and resolve overdue appointments from a single list view designed for front-desk and reception staff.

While the calendar shows you *when* things happen, the appointment queue shows you *what needs attention*. It is a list-based view organized by urgency and action type, designed for reception staff managing the daily flow of patient visits.

## Queue tabs

The queue is divided into five tabs, each filtering appointments by a different priority.

### All

Every appointment in the system within the default time window — 30 days in the past through 90 days in the future. Use this tab for searching across the full scope when other tabs are too narrow.

### Requested

Appointments created by patients through the self-booking portal. These are waiting for staff approval before they appear on the schedule.

<Note>
  The **Requested** tab is the first place your reception team should check each morning. Patient-submitted requests need a doctor assignment and approval before they are confirmed.
</Note>

### Today

All appointments scheduled for the current day, regardless of status. This is your operational view — use it to track which patients have arrived, who is with a doctor, and who still needs to be seen.

### Upcoming

Future appointments beyond today. This tab helps your team prepare for the days ahead — confirming details, checking for missing information, and ensuring everything is ready.

### Action Required

Past appointments that are still in an unresolved status. This includes appointments stuck in:

* **Requested** — Never approved
* **Scheduled** — Never confirmed or completed
* **Confirmed** — Patient checked in but visit never started
* **In Progress** — Doctor started but never completed the visit

<Warning>
  Action Required items represent data hygiene problems. An appointment from last week still showing as "In Progress" means someone forgot to complete it. Resolve these regularly to keep your records accurate.
</Warning>

## Reception approval workflow

When a patient books through the portal, the appointment arrives in **Requested** status. Here is how to process it:

<Steps>
  <Step title="Open the Requested tab">
    Navigate to the Appointment Queue and select the **Requested** tab to see all pending requests.
  </Step>

  <Step title="Review the request">
    Check the patient's preferred date, time, and any notes they included. Verify the time slot is available.
  </Step>

  <Step title="Assign a doctor and procedure type">
    Select the appropriate doctor for the visit and confirm or adjust the appointment type.
  </Step>

  <Step title="Approve the request">
    Click **Approve** to move the appointment to **Scheduled** status. The patient will see the confirmed appointment in their portal.
  </Step>
</Steps>

<Tip>
  If the requested time does not work, you can adjust the date and time before approving. You can also decline the request by cancelling it, then contact the patient to reschedule.
</Tip>

## One-click status transitions

The queue supports quick status changes directly from the list, without opening the appointment detail page. Available actions depend on the current status:

<CardGroup cols={2}>
  <Card title="Confirm">
    Move a Scheduled appointment to Confirmed when the patient checks in. You will be prompted to assign an operatory if one is not already set.
  </Card>

  <Card title="Complete">
    Mark a visit as finished. Typically used after the doctor indicates they are done with the patient.
  </Card>

  <Card title="No Show">
    Flag a patient who did not attend their appointment. Only available once the appointment time has passed.
  </Card>

  <Card title="Cancel">
    Cancel an appointment. Frees the time slot for other patients.
  </Card>
</CardGroup>

These one-click actions follow the same permission rules and time restrictions described in the [Appointment Statuses & Workflow](/clinical/appointment-lifecycle) article.

## Dashboard widget

The main dashboard includes a **Pending Appointments** widget that shows only **Requested** items. This gives admins and receptionists immediate visibility into patient self-bookings without navigating to the queue.

<Note>
  The dashboard widget is a shortcut to the queue's Requested tab. Clicking any item in the widget opens the full appointment detail where you can complete the approval workflow.
</Note>

## Default time window

The queue loads with a sensible default range:

* **Past**: 30 days back, so you can review recent history and catch Action Required items
* **Future**: 90 days ahead, covering typical advance booking ranges

This window keeps the list manageable while ensuring nothing important falls through the cracks. You can adjust the date range using the filter controls at the top of the queue.

## Queue vs. calendar

Both views show appointments, but they serve different purposes:

<AccordionGroup>
  <Accordion title="When to use the queue">
    Use the queue when you need to **process** appointments — approve requests, update statuses, and resolve overdue items. The list format makes it easy to work through items sequentially.
  </Accordion>

  <Accordion title="When to use the calendar">
    Use the calendar when you need to **visualize** the schedule — check for gaps, balance doctor workloads, and plan future days. The time-based layout shows relationships between appointments that a list cannot.
  </Accordion>

  <Accordion title="Can I use both together?">
    Absolutely. Many clinics keep the queue open on the reception workstation for processing and the calendar on a wall display for visibility. They complement each other.
  </Accordion>
</AccordionGroup>

## Who uses the queue

Different roles interact with the queue in different ways:

* **Receptionists** use the Requested and Today tabs most heavily, processing approvals and managing patient check-ins throughout the day.
* **Admins** monitor the Action Required tab to ensure data hygiene and review the overall scheduling health of the practice.
* **Doctors** may check the Today tab to preview their own schedule, though they more commonly use the calendar's Doctor Day view for this purpose.

## Best practices

<AccordionGroup>
  <Accordion title="Process the Requested tab first thing each morning">
    Patient requests that sit too long without approval create a poor experience. Make it a morning routine for reception to clear the Requested queue before the clinic opens.
  </Accordion>

  <Accordion title="Review Action Required weekly">
    Set a recurring time — Friday afternoons work well — to clean up stale appointments. This keeps your reporting accurate and prevents confusion when patients rebook.
  </Accordion>

  <Accordion title="Use the Today tab as your operational cockpit">
    During clinic hours, keep the Today tab visible. It shows you exactly where every patient is in the workflow, making it easy to answer questions like "Who is next?" and "Has the 2 PM patient arrived?"
  </Accordion>
</AccordionGroup>

## Related articles

* [Creating Appointments](/clinical/appointments) — How appointments enter the queue
* [Appointment Statuses & Workflow](/clinical/appointment-lifecycle) — Status transitions available from the queue
* [Scheduling Calendar](/clinical/calendar) — Visual complement to the queue
* [Appointment Detail Page](/clinical/appointment-detail) — Full detail view accessible from queue items