> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/profiles/creating-a-customer-profile/customer-tags.md).
# Customer Tags
### Overview
Customer Tags are labels on Customers that let you find them again as a group.
* **Custom Tags** — applied by staff in a Customer's Profile, like **VIP**
* **System Tags** — the platform applies on its own from what the Customer does, like **Lesson** for anyone who has booked a court with a coach
### Related Updates
* [Read a Customer Note from the Has Notes Tag](/profiles/creating-a-customer-profile/read-a-customer-note-from-the-has-notes-tag.md)
### Where you will see Tags
* **A Customer's Profile** — the **Customer Tags** section, on the Overview tab above Account Status
* **The Customers list** — a **Tags** column, and a **Tags** filter for narrowing the list
* **Customer Tags page** — the full list of your Club's tags, with how many Customers hold each one (`https://[club_name].podplay.app/adminv2/companies/current/customer-tags`); this is visible from the Front Desk role up
### Who can do what
| Role | Tags and untags Customers | Creates, edits and deletes Tags |
| ----------------- | ------------------------- | ------------------------------- |
| Front Desk | Yes | No |
| Manager and above | Yes | Yes |
Viewer and lower roles do not reach the Customers or Customer Tags pages, so they do not work with Tags. No role can apply or edit a System Tag — see below.
### Tags in a Profile
* Search for the Customer and open their profile
* Find the **Customer Tags** section
* Click **Add tag** and pick a tag from the list
* To take a tag off, click the **×** on the tag
Tags applied by the platform have no **×** and they cannot be removed. More on those below.
### Tag several Customers at once
* Go to **Settings**, then **Customer Tags**
* Click the Tag you want to apply
* Use **Add a customer to this Tag** to search for each Customer and add them
The same page lists everyone who currently holds the Tag, and lets you remove them one at a time. **Export** downloads that list as a spreadsheet.
### Find Customers by Tag
* Go to the **Customers** page
* Open **More Filters**
* Choose one or more tags under **Tags**
The list narrows to Customers holding those Tags, and the **Tags** column shows what each one holds.
### System Tags
Some Tags are maintained by the platform from a Customer's activity — for example **Booked**, **Reservation**, **Lesson**, **Guest**, **Has Kids**, **On Chat**, the Replay Tags, and one Tag for each of your Event types. They are marked **System** on the Customer Tags page.
These tags:
* Go on and come off on their own as the Customer's activity changes
* Cannot be renamed, edited or applied by staff, by anyone
* Are useful for filtering and for restricting events when Customer Tag Restrictions are enabled, exactly like the tags you apply yourself
### Tags and Locations
A Tag is either available at **all locations** or limited to **selected locations**. The **Available at** column on the Customer Tags page shows which.
Staff whose role is limited to certain locations only see **Selected locations**, and can only create or edit Tags for the locations they cover.
A Tag limited to locations can only be held by Customers at those locations. Customers with a current Global or Angel membership count as being at every location, so they can always be tagged.
**If a Tag's locations are narrowed**, Customers who fall outside will lose it. Before the change is saved you will see a warning telling you how many Customers that is — for example, **12 customers outside these locations will lose this tag**.
{% hint style="warning" %}
Losing a Tag this way cannot be undone by widening the locations again. The Customers have to be added back and will not automatically have the Tag added again to their Profile.
{% endhint %}
### Why the same Tag name appears twice
Two Tags can share a name as long as they have no location in common — one club might have a **VIP** Tag at the Shibuya location and a separate **VIP** Tag at the Shinjuku location, each with its own list of Customers.
When that happens, the Tag shows its location beside the name, like **VIP · Shibuya**, so you can tell them apart. A Tag whose name is unique across the club just shows the name.
### What the numbers mean
On the Customer Tags page:
* **Customers** — how many Customers hold that Tag
* **Percentage of customers** — that Tag's share of your Customers
Both numbers follow the location filter at the top of the page. With no location chosen, they cover the whole club. Choose a location and both numbers describe that location only, so the same tag will show a smaller number.
The same applies on a tag's own page, where the count beside the tag name reads, for example, **48 customers in Shibuya**.
### See who changed a Tag
Each Tag has an [**Activity Log**](https://docs.podplay.app/support-and-troubleshooting/customer-activity-log) (Logs) tab showing when it was created, renamed, given a new description or colour, had its locations changed, or was deleted, and who did it.
Applying a tag to a Customer, or removing it, is recorded on **that Customer's** activity feed rather than on the Tag.
Tags that the platform applies on its own are not recorded in either place — only changes made by staff are.
### Tips
* Deleting a Tag removes it from every Customer who holds it, including Customers outside your current location filter. The Customers themselves are not affected.
* Customers are not notified about Tags, and Tags are not shown to them anywhere in the App.
* Tags can also be used to restrict who may sign up for an Event — see the Event setup documentation.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.podplay.app/profiles/creating-a-customer-profile/customer-tags.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
