# Customer Management

The **Customers** section in the backoffice gives you access to your full customer database — including booking history, contact details, and management options such as editing or blacklisting.

<figure><img src="/files/0aToUaaXHf4LuZaoHsIY" alt=""><figcaption></figcaption></figure>

***

### 📂 Viewing **Customers** Profiles

Clicking on a client in the list opens their **detailed profile page**, where you’ll find:

* Contact information (name, email, phone)
* All past booking requests, grouped by type
* Total number of requests
* Total amount spent on **privatisation fees**

This gives you a clear overview of the client’s engagement with your venue.

<figure><img src="/files/ozjuMnx7vVJoVtsvhGKm" alt=""><figcaption></figcaption></figure>

***

### ✏️ Editing **Customers** Information

Click the **“Edit”** button on a client’s profile to update their details:

* Name
* Email
* Phone number
* Any internal notes

This is useful to correct typos or update contact data.

<figure><img src="/files/mTwvZV6L3FqF3ctSHKJN" alt=""><figcaption></figcaption></figure>

***

### 🚫 Blacklisting **Customers**

You can **blacklist a client** from their profile using the toggle button.

Once blacklisted:

* The client will be automatically highlighted in **blue** across the interface
* This acts as a visual warning for your team
* You can also leave internal notes (e.g. "no-show", "rude behavior") that only your team can see

***

### ⚠️ Manual Booking Rules

If you're creating a **manual booking** from the backoffice:

* The client **must already exist** in the database\
  → Always create the client *before* creating the booking

This ensures that the request is linked to the correct user and their history remains accurate.

***

### 🗑️ Deleting a **Customers**

You can delete a client entirely from the database if needed.\
Be cautious — this action is **permanent** and will remove all associated records from the client’s profile.

***


---

# Agent Instructions: 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:

```
GET https://bookit-2.gitbook.io/bookit-template-bubble/basics/markdown/customer-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
