> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/customers-and-work/contacts/give-a-contact-more-than-one-email-address.md).

# Give a contact more than one email address

A contact can have more than one email address, for example a work address plus a shared accounts-payable inbox. The **Email** field holds the contact's primary address. Any extra addresses go under **Additional emails**, as many as you need.

## Add, change, or remove additional emails

1. Open the contact and click **Edit**. The same field is on the **New contact** page, each contact on the **New customer** page, and the **Edit** link on a property's **Contacts** card.
2. Under **Email**, click **+ Add email** and type the address. Click **+ Add email** again for each address you want to add.
3. To remove an address, click the **×** next to it.
4. Click **Save**.

Extra addresses must be valid email addresses. If you enter the primary address again, or the same address twice, the form says so and the repeat is dropped when you save. Capitalization doesn't make two addresses different.

To make an additional address the primary one, type it into **Email** and save. It moves out of the additional list automatically. If you clear **Email** and save, the first additional address becomes the primary.

## Where additional emails show up

* **Contact page and a property's Contacts card:** every address is listed, primary first.
* **Contacts list and a customer's Contacts tab:** the **Email** column shows the primary address with a count of the others, such as **+2**. Table search finds a contact by any of their addresses.
* **Global search:** searching any of a contact's addresses finds them.
* **Technician app:** wherever a visit's contact list shows the primary email, it also shows the additional ones, and each opens the phone's email app.
* **CSV export:** the Contacts export includes an **Additional Emails** column.

## Sending to an additional email

When you send a quote, an invoice, a payment receipt, an inspection report, or a work acknowledgment, the recipient picker lists each of a contact's additional emails below their primary address, under the contact's name. Pick the address you want, in **To** or **Cc**. Typing or pasting an additional address also matches it to the contact. The email goes to exactly the address you picked.

Emails Essential starts on its own, such as visit reminders and job approval requests, go only to the contact's primary email. Follow-ups for a quote or invoice you sent go to the addresses you chose when you sent it.

> **Where to find it:** Main navigation → Customers, then **Contacts** in the submenu → open a contact → **Edit** → **Additional emails** (below **Email**)

## Related guides

* [Edit a contact's details, or where their roles live](/customers-and-work/contacts/edit-a-contacts-details-or-where-their-roles-live.md)
* [Creating a contact](/customers-and-work/contacts/creating-a-contact.md)
* [What the contact page shows](/customers-and-work/contacts/what-the-contact-page-shows.md)
* [Send an invoice to a customer](/revenue/invoices/send-an-invoice-to-a-customer.md)
* [Send a quote to a customer](/revenue/quotes/send-a-quote-to-a-customer.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://learn.withessential.com/customers-and-work/contacts/give-a-contact-more-than-one-email-address.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.
