> 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/perkville-support-cannot-help-with-purported-inaccessible-email-addresses.md).

# Perkville Support cannot help with purported inaccessible email addresses

This page describes a scenario in which a person has lost access to their email address, and would like to transfer points or access from the old email address to a new one.

Perkville Support can never take at face value requests from users writing from one email address asking for access to a second email address, even if certain details appear to be in alignment, such as date of birth or name.

## I'm a user. I've lost access to my email address, what can I do?

The only resolution is to contact the business directly and ask for help. This does not constitute a promise on the part of Perkville Support that the business will take any action to effectuate a resolution. Businesses are within their rights to deny any request to transfer points from the old account into a new one. The only resolution at that point would be to continue using an email address accessible to you.

## I'm a business staff member. How can I help users who have lost access to their email address?

Businesses are free to create any policy that makes sense to you for how to resolve these situations. We describe two approaches below.

**In all cases, please consider carefully the authenticity of the request, and confirm any identifying details as appropriate (for example, in your point of sale or membership management system) before effectuating a resolution.**

First, see [this article](https://docs.perkville.com/faqs/managing-emails-and-names/can-i-merge-two-emails-into-the-same-account.md) for how to use the merge tool to automatically merge details together and resolve the two disparate point balances. (Note that certain situations will cause this tool to reject the merge request, such as when the source email is a staff member at a business.)

Second, as an alternative to the above, consider using a [point adjustment](https://docs.perkville.com/features/customers.md) on both accounts to effectuate a manual "point transfer" from one account to the other. Here's how to do that.

1. First, create a negative point balance on the old account that would result in a point balance of 0. (For example, if the balance on the old account is 2,314 points, create a negative point adjustment of -2,314.)
2. Second, create a positive point adjustment on the new account equivalent to (or less than) the value remembered above. (For example, create a point adjustment of +2,314.) Consider carefully certain "one time" rewards that may reduce the value you want to transfer, such as a sign-up bonus.


---

# 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/perkville-support-cannot-help-with-purported-inaccessible-email-addresses.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.
