> For the complete documentation index, see [llms.txt](https://docs.simplespa.net/simplespa-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplespa.net/simplespa-documentation/fundamentals/appointments/park-appointment.md).

# Park Appointment

arking an appointment lets you hold a client's request on a waiting list when no suitable slot is currently available — without blocking time on the calendar. Parked appointments sit in the waitlist until a slot opens up and staff are ready to convert them into confirmed bookings.

***

### Overview

| Feature                | Details                                                              |
| ---------------------- | -------------------------------------------------------------------- |
| **Access**             | Dashboard and Appointments page — **Park** button in the top toolbar |
| **Requires**           | A client, a service. Staff and date are optional.                    |
| **Visible in**         | The Waitlist panel (bell/tasks icon in the top navigation bar)       |
| **Effect on calendar** | None — parked appointments do not occupy any time slot               |

***

### When to Use It

Use Park Appointment when:

* A client calls and wants a specific service but nothing is available on their preferred date
* You want to note a future client request without creating a placeholder booking
* A client wants to be first in line if a cancellation comes up
* Staff capacity is full and you want a queue to fill gaps automatically

***

### How to Park an Appointment

1. Click the **Park** button in the top toolbar on the Dashboard or Appointments page.
2. The Park Appointment panel opens.

#### Required fields

**Client** Search by name using the client search field. Results appear as you type. Select the client — their name and details appear as a chip. Click the × on the chip to change the selection.

**Service** Select the service the client is requesting from the dropdown. Services are grouped by category.

#### Optional fields

**Staff preference** If the client has a preferred staff member, select them here. Defaults to "No preference."

**Preferred date** If the client has a target date in mind, enter it here. This is for reference only and does not reserve the slot.

**Notes** Internal notes visible only to staff — use this for context such as scheduling constraints, client preferences, or follow-up reminders.

#### Urgent flag

Toggle **Mark as urgent** to flag this parked appointment as high priority. Urgent requests are visually highlighted in the waitlist so staff know to prioritise them when a slot opens.

3. Click **Park Appointment** to save.

The appointment is added to the waitlist immediately. No calendar slot is created.

***

### Viewing Parked Appointments

Click the **Waitlist** icon (checklist icon) in the top navigation bar to open the Waitlist panel. The table shows:

| Column        | Description                              |
| ------------- | ---------------------------------------- |
| **Added**     | Date and time the request was parked     |
| **Req. Date** | The client's preferred date, if provided |
| **Client**    | Client name                              |
| **Service**   | Requested service                        |
| **Staff**     | Staff preference, or "No preference"     |
| **Type**      | Standard or Urgent                       |

***

### Converting a Parked Appointment

When a slot becomes available:

1. Open the Waitlist panel.
2. Find the parked request — urgent items are highlighted.
3. Use the action controls on the row to book the appointment. This opens the standard appointment booking flow pre-filled with the client, service, and staff preference from the parked request.
4. Once booked, remove the entry from the waitlist.

***

### Frequently Asked Questions

**Does parking an appointment notify the client?** No. Parking is an internal staff action. The client is not sent any notification when their request is parked or when a slot becomes available. Staff should follow up with the client directly.

**Can I park the same client for multiple services?** Yes. Each parked entry is independent. A client can have multiple parked requests for different services or dates.

**Is a parked appointment the same as a waitlist entry?** Yes — "Park" and "Waitlist" refer to the same feature. The Park button creates a waitlist entry; the Waitlist panel is where all parked appointments are managed.

**Can I edit a parked appointment after saving?** Open the Waitlist panel and use the edit action on the row to update the request.

**What happens if I close the Park panel without saving?** The request is discarded. No entry is created in the waitlist.

**Who can park appointments?** Any staff member with access to the Dashboard or Appointments page. Viewer-only roles do not have access to the Park button.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.simplespa.net/simplespa-documentation/fundamentals/appointments/park-appointment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
