> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/profiles/creating-a-customer-profile/how-to-add-a-phone-number.md).
# Edit Phone Number or Email
### Overview
A Customer can add or change their phone number in the App. Club staff can change a phone number or an email from the Dashboard. Customers cannot change their own email.
Each email address and phone number can belong to only one Profile. If you try to add one that another Profile already uses, PodPlay rejects the change. The usual cause is a duplicate Profile created during a Profile import. PodPlay has no merge option, so the fix is to move the details onto the Profile the Customer wants to keep.
### Edit a phone number
#### From the App
The Customer:
1. Taps the `More` tab (bottom right)
2. Taps `Account`
3. Taps `Account Info`
4. Taps `Phone`
5. Enters the phone number
6. Taps `Send Code`
1. The system sends a verification code by text message
7. Enters the code in the App
{% hint style="info" %}
**For international phone numbers,** check the flag shown next to the `Phone` field. If it matches the Customer's country, enter the number without the +CODE. If it doesn't, either pick the correct country from the flag dropdown and enter the number without the +CODE, or enter `+CODE [number]` and the App selects the flag automatically.
{% endhint %}
#### From the Dashboard
A staff member:
1. Opens the Customer Page
2. Searches for the Customer
3. Clicks the Customer's Profile. A side panel opens
4. Clicks the pencil icon next to `Phone Number` at the top of the `Overview` tab
5. Enters the phone number
6. Clicks `Save`
### Edit an email
Only Club staff can change a Customer's email, and only from the Dashboard.
1. Open the Customer Page
2. Search for the Customer
3. Click the Customer's Profile. A side panel opens
4. Click the pencil icon next to `Email` at the top of the `Overview` tab
5. Enter the new email
6. Click `Save`
### Email or phone number already in use
Emails and phone numbers are unique, so normal sign-up cannot create two Profiles with the same details. When one Customer ends up with two Profiles, it almost always comes from a Profile import that loaded both an existing set of details and a second set.
To fix it, choose the Profile the Customer wants to keep (usually the one with the email they sign in with), then move the correct details onto it.
{% hint style="warning" %}
**Remove the value from the duplicate Profile first.** PodPlay rejects an email or phone number that another Profile still holds. Clear it from the duplicate Profile before you add it to the Profile you're keeping.
{% endhint %}
1. Open the Profile the Customer wants to keep and remove any incorrect email or phone number.
2. Open the duplicate Profile and remove the correct email or phone number from it. Note the value.
3. Return to the Profile the Customer wants to keep, add the value, and click `Save`.
{% hint style="info" %}
**History does not combine.** Reservations, Memberships, and other activity stay on the Profile where they were created. Moving an email or phone number does not move that history.
{% endhint %}
#### Example
A Customer has these two Profiles:
| Profile | Email | Phone number |
| --------- | -------------------- | -------------- |
| Profile 1 | `kyle@podplay.app` | `201-575-1234` |
| Profile 2 | `kyle10@podplay.app` | `201-575-4321` |
The Customer signs in with `kyle@podplay.app`, so Profile 1 is the one to keep. Their correct phone number is `201-575-4321`, which sits on Profile 2.
1. Delete `201-575-1234` from Profile 1
2. Remove `201-575-4321` from Profile 2
3. Add `201-575-4321` to Profile 1
4. Leave Profile 2 alone
Any variation of these steps is fine. The goal is one Profile that holds all of the Customer's correct information.
### Delete or leave the duplicate Profile
Once the Profile the Customer wants to keep is correct, decide what to do with the duplicate Profile.
* **Leave it as is:** The Customer stops using it. Choose this when the duplicate Profile has history worth keeping, such as past Reservations or purchases.
* **Delete it:** Choose this when the duplicate Profile is entirely a duplicate and holds nothing worth keeping.
### FAQs
Can a Customer change their own email in the App?
No. Only Club staff can change an email, from the Dashboard.
Can PodPlay merge two Profiles into one?
No. There is no merge option today. Move the correct details onto one Profile and either delete or leave the other.
Should I deactivate or delete the duplicate Profile?
Delete it if it is entirely a duplicate. If it holds history you want to keep, leave it in place and have the Customer use the other Profile.
---
# 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.podplay.app/profiles/creating-a-customer-profile/how-to-add-a-phone-number.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 `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.