> For the complete documentation index, see [llms.txt](https://docs.roadmap.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roadmap.so/loyalty-and-rewards/customer-management/manage-loyalty-customers.md).
# Manage loyalty customers
The Manage Customers area — filter and save member views, open a customer's loyalty profile, adjust their points, redeem on their behalf, and read their history.
**Manage Customers** is the admin home for loyalty members. Open it from the **Loyalty Program** dashboard.
#### The customer list
The list includes name, email, **Tier**, **Expiry Date**, **Member since**, **Last active**, **Total spent**, and **Points**.
**Tier** can show **None** for members without a tier. It shows **B2B** when company membership pauses personal loyalty.
Search by name or email. Use the D2C / B2B toggle to open the B2B Companies dashboard. Use the **Members**, **Non-members**, and **All** tabs to filter customers.
#### Save your own views
{% stepper %}
{% step %}
**Create the view**
Click **+** next to the tabs. Name and create the view.
{% endstep %}
{% step %}
**Add filters**
Click the search/filter icon, then add filters. For example, use **Status: Members** and **Membership Tier**.
{% endstep %}
{% step %}
**Save the filtered view**
Click **Save as** and enter a name. Save after filtering so the view retains its filters.
{% endstep %}
{% endstepper %}
#### The customer detail page
Select a customer to open their loyalty profile. Click **View Customer** to open their Shopify profile.
**Point History** contains:
* **Transactions** for every earning, spending, and adjustment, including award and expiry dates.
* **Discounts** for redeemed codes, reward value, `Active`, `Used`, `Refunded`, or `Deleted` status, creation date, and code copy.
**Membership History** records membership start-date and tier changes. **Orders** lists order history and totals.
You can also use **Update Birthday**. Under **Membership → Update**, change tier, start date, or expiry date.
#### Adjust their point balance
Use **Adjust point balance** to add or remove points. Enter a negative value to subtract.
* **Reason for adjustment** is internal.
* **Customer facing note** appears in the customer’s points history. It defaults to `Manual adjustment`.
The modal shows **New Balance** before you confirm.
#### Redeem points on a customer's behalf
Use **Redeem points** to generate an available reward for a customer. Copy the generated code to share it.
The code also appears on the customer’s redeemer surfaces: cart drawer, loyalty page, and Shopify Plus checkout redeemer.
#### The Timeline
The Timeline records earnings, spendings, admin actions, and non-awarded reasons. See [Understanding a customer's loyalty timeline](/loyalty-and-rewards/customer-management/understanding-a-customers-loyalty-timeline.md).
#### Related guides
* Understanding a customer's loyalty timeline
* Refund an unused loyalty coupon
* Loyalty Tiers
---
# 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.roadmap.so/loyalty-and-rewards/customer-management/manage-loyalty-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.
