> For the complete documentation index, see [llms.txt](https://docs.mews.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mews.com/loyalty-partner/workflows/search-members.md).

# Search members

**Mews Operations** uses the [Search members](https://docs.mews.com/loyalty-partner/api-operations/members.md#post-members-search) operation to find members in the partner loyalty system matching a specific Mews customer, based on personal information such as name, email, and address.

## New customer creation

Front desk staff are creating a new customer profile. The customer already exists in the partner loyalty system with a membership. During the creation process, Mews queries the partner system for potential matching members and returns a list of matches.

{% stepper %}
{% step %}

#### Create customer

<figure><img src="https://3946584615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXX5WlJYsdpRtizxNDPz%2Fuploads%2Fgit-blob-c18401b10d7d35025d2879e1b957a842731d1c30%2Fcreate-customer-screen.png?alt=media" alt="New customer creation form with fields for email, name, phone, membership number, and address" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Lookup results

<figure><img src="https://3946584615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXX5WlJYsdpRtizxNDPz%2Fuploads%2Fgit-blob-a917cafab3ac3655b7d424168fae87a187c7b8b1%2Flookup-results.png?alt=media" alt="List of matching members returned from the partner loyalty system, with customer details and a Confirm button" width="330"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Link membership to existing customer

A customer already exists in Mews without a linked loyalty membership. Mews queries the partner loyalty system to retrieve a list of possible matches.

{% stepper %}
{% step %}

#### Customer profile screen

<figure><img src="https://3946584615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXX5WlJYsdpRtizxNDPz%2Fuploads%2Fgit-blob-9d8d1f41d93d55b4f9c4eef42f60f554fd57d72c%2Fcustomer-profile-screen.png?alt=media" alt="Customer profile screen with a Loyalty panel warning that the customer is not enrolled in a loyalty program" width="563"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Customer lookup result

<figure><img src="https://3946584615-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXX5WlJYsdpRtizxNDPz%2Fuploads%2Fgit-blob-e9d82f473a96b09cada3bd47c99c452bd3f4e47c%2Fcustomer-profile-lookup-result.png?alt=media" alt="Customer profile screen with a membership lookup panel showing a list of matching members from the partner loyalty system" width="563"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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.mews.com/loyalty-partner/workflows/search-members.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.
