> For the complete documentation index, see [llms.txt](https://docs.premsoft.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.premsoft.de/en/plugins/bonus-system/admin-dashboard/customers.md).
# Customers
The customer list shows all customers of your shop — including their point balance, if they have one.
Columns shown:
* Name
* Customer number
* E-mail
* Points balance
The **Customer group** filter in the sidebar narrows the list; the search field finds customers by name, customer number and e-mail address.
> The stacked icon at the top right of the table lets you show and hide columns and switch between compact and expanded view.
## Customer details
Open the detail view through the **…** menu of a row and **View**. It shows the contact data, account status, customer group, language and customer number, plus the customer's **points balance** and **booking history**.
## Crediting and deducting points manually
There are two ways to the booking dialog:
* in the customer list through the **…** menu and **Edit points**,
* in the detail view through the **Book points** link below the balance.
In the **Credit/Deduct points** dialog you enter a **Reason** and the **Points**. A minus sign deducts points, for example `-100`. **Apply** activates the booking immediately and updates the balance.
> Manual bookings fire the Flow Builder trigger **Bonus points changed**, so you can notify the customer by e-mail automatically — see [Flow Builder and rules](/en/plugins/bonus-system/flow-builder-and-rules.md).
## The points account in the storefront
Customers see the same state in their account under **Points account**, with the tabs **Booking history** and **Points status**. If the expiration e-mail is enabled and customers may unsubscribe, they manage their subscription there as well.
---
# 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.premsoft.de/en/plugins/bonus-system/admin-dashboard/customers.md?ask=&goal=
```
`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.