> For the complete documentation index, see [llms.txt](https://docs.diro.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diro.app/en/operations/branches-and-customers.md).

# Branches & Customers

## Branches

**Settings → Branches.** Each physical location is one branch, with its own address, map point, contact, photo, and operating hours.

Services, staff, and resources are all attached to a branch. Customers choose a branch when booking, and then only see the services and slots available there.

If you have more than one branch, use the **branch switcher in the portal header** to change context. The data shown on the portal pages follows the currently active branch.

{% hint style="info" %}
A branch's operating hours are shown to customers as information, but they do not limit booking slots. What determines slots is the service schedule and resource availability. See Setting the Service Schedule.
{% endhint %}

## Customers

**Customer → Customer List.** Anyone who has ever made a booking is automatically added here, complete with booking history, total spend, active memberships, and vouchers they hold.

Use this data to:

* Reach out to customers who haven't visited in a while.
* See which customers have the highest spend.
* Check history before serving a returning customer.

Existing customer data from a previous system can be uploaded all at once through the import feature.

## Reviews

Incoming reviews are linked to the customer and their booking. See Customer Reviews.


---

# 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.diro.app/en/operations/branches-and-customers.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.