> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/connectors/crm-and-fidelity.md).

# CRM & loyalty

Connect CRM and loyalty systems to The Wallet Crew to keep Apple Wallet and Google Wallet passes aligned with customer profiles, points, tiers and rewards.

CRM and loyalty systems usually hold the source of truth for customer identity, points, tiers, rewards, and eligibility. The Wallet Crew connects those systems to Apple Wallet and Google Wallet, so each pass stays aligned with the latest customer state.

In most deployments the CRM or loyalty platform stays authoritative for customer data and business rules. The Wallet Crew handles wallet issuance, updates and delivery. A pass only works as a trusted credential when its data stays current, and a stable identifier links each source record to its pass. The responsibilities of each side are in [Wallet pass connectors](https://docs.thewalletcrew.io/connectors/wallet-pass-connectors.md#responsibilities).

<details>

<summary><strong>Real-world examples</strong></summary>

* **Retail loyalty:** points and tier change after checkout, then the pass updates without reissue.
* **Clienteling and recognition:** store staff scan the pass to identify the customer profile and available benefits.
* **Promotion and rewards:** a CRM or loyalty engine unlocks an offer, then the pass reflects the new entitlement.

</details>

## Common data synchronized to wallet passes

Typical integrations synchronize:

* customer identifiers used for recognition and scanning
* points, balances, tiers, and reward status
* lifecycle signals such as enrolment, renewal, expiry, or benefit changes

## Available connectors

| Connector          | Status                                                               | Page                                                                                                  |
| ------------------ | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| Comarch            | Documented: setup, data mapping, real-time updates and extensibility | [Comarch](https://docs.thewalletcrew.io/connectors/crm-and-fidelity/comarch.md)                       |
| Insider            | Not documented                                                       | [Insider](https://docs.thewalletcrew.io/connectors/crm-and-fidelity/insider.md)                       |
| Meteors            | Not documented                                                       | [Meteors](https://docs.thewalletcrew.io/connectors/crm-and-fidelity/meteors.md)                       |
| Microsoft Dynamics | Not documented                                                       | [Microsoft Dynamics](https://docs.thewalletcrew.io/connectors/crm-and-fidelity/microsoft-dynamics.md) |
| Snowflake          | Not documented                                                       | [Snowflake](https://docs.thewalletcrew.io/connectors/crm-and-fidelity/snowflake.md)                   |
| Talon.One          | Not documented                                                       | [Talon.One](https://docs.thewalletcrew.io/connectors/crm-and-fidelity/talonone.md)                    |

[Contact The Wallet Crew](https://www.thewalletcrew.io/contact) to discuss the platforms marked Not documented.

## CRM and loyalty platforms not listed

For an unlisted CRM or loyalty platform, see [Choose an integration path](https://docs.thewalletcrew.io/connectors/wallet-pass-connectors.md#choose-an-integration-path). Tenant-specific requirements use a [custom connector](https://docs.thewalletcrew.io/connectors/custom-connector.md). Define stable identifiers that link source records to wallet passes.


---

# 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.thewalletcrew.io/connectors/crm-and-fidelity.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.
