> 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.md).

# Customer management

- [Manage loyalty customers](https://docs.roadmap.so/loyalty-and-rewards/customer-management/manage-loyalty-customers.md): 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.
- [Understanding a customer's loyalty timeline](https://docs.roadmap.so/loyalty-and-rewards/customer-management/understanding-a-customers-loyalty-timeline.md): Read a customer's loyalty timeline: earnings, spendings, admin actions, and the exact reasons an order or review didn't award points.
- [Import loyalty customers](https://docs.roadmap.so/loyalty-and-rewards/customer-management/import-loyalty-customers.md): Bring existing loyalty members into Roadmap from a CSV: points, tiers, membership dates and birthdays. What the file needs, how matching works, and how to read your import results.
- [Block customers from the loyalty program](https://docs.roadmap.so/loyalty-and-rewards/customer-management/block-customers-from-the-loyalty-program.md): Keep chosen customers out of your loyalty program with a Shopify customer tag: what changes for them, what they see, and how to bring them back.


---

# 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.roadmap.so/loyalty-and-rewards/customer-management.md?ask=<question>&goal=<user_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.
