> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/faqs/managing-emails-and-names/my-customer-has-two-accounts.-what-should-i-do.md).

# My customer has two accounts. What should I do?

If a customer has two (or more) accounts in your loyalty program, you can [transfer their information](https://docs.perkville.com/features/customers/transfer-account-data.md) to the account they should be using with their up to date email address. Here’s how:

1. Navigate to the customer profile of the account where you'd like to transfer data from.
2. Click on "Transfer data," enter the email address associated with the account you'd like to transfer data to.
3. Follow the prompts to transfer points, membership details, and referrals.

**Important note about Perkville Support's policies regarding inaccessible emails**

Please do not advise users to contact Perkville Support about this issue.

Perkville Support cannot take at face value requests from users writing from one email address to gain access to another email address. Users must contact the business directly for any information transfer requests. [Read this article for a complete description of this policy.](https://docs.perkville.com/faqs/managing-emails-and-names/perkville-support-cannot-help-with-purported-inaccessible-email-addresses.md)


---

# 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.perkville.com/faqs/managing-emails-and-names/my-customer-has-two-accounts.-what-should-i-do.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.
