> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/implementation-guide/members-and-activity/members/member-list/single-member-view/general-info.md).
# General Info
The **General Info** tab provides an overview of the member’s profile, including their basic details, registration data, and program participation highlights. It is the starting point for understanding who the member is and how they engage with the loyalty program.
***
### Key Elements
* **Basic details**\
Displays the member’s name, email, phone number, date of birth, gender, referral token, and loyalty card number.
* **Registration data**\
Shows the date when the member joined the program.
* **Segments**\
Lists the segments this member belongs to (e.g. *High Spenders*, *Inactive 90 days*, *Birthday in 2 days*).
* **Custom attributes**\
Displays any attributes specifically assigned to the member.
* **Business performance**\
Provides insight into the member’s economic activity:
* Total spending
* Number of purchase and return transactions
* Average transaction and return values
* Days since last transaction
* **Wallets overview**\
A snapshot of balances in different wallets, including active, pending, expired, spent, and total earned units.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://help.openloyalty.io/implementation-guide/members-and-activity/members/member-list/single-member-view/general-info.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 `build a script that syncs our docs to a CMS` 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.
