> 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/what-the-contact-page-shows.md).

# What the contact page shows

A contact is a person on a customer account, the people you reach out to for approvals, billing, or site access. The contact page shows their name, email addresses (the primary email first, then any additional emails), and phone numbers (with each number's type), their title or company, and the customer account they belong to.

When the customer portal feature is on for your business, a Portal pill appears next to their name - enabled when this contact has portal access, the customer's portal is on, and the customer is active, and disabled (greyed) otherwise. See [Give a contact access to the customer portal](/customers-and-work/contacts/give-a-contact-access-to-the-customer-portal.md) for what the greyed state can mean.

The Roles tab lists the properties and roles they're assigned to, and the Automations tab shows outreach involving them. Its date columns separate when the outreach started, its next pending action, and, for Job Approval outreach, the service due date behind the schedule. Use Edit to change their details, or Delete Contact to remove them.

You can ask Essential about the contact you're viewing, such as their email, phone, or which account they belong to.

Each custom field has its own card at the top of the right column, above Notes, matching Customer and Property pages. Click **Edit** on a card to change that field, then **Save**. On mobile, these cards appear below Roles and Automations. These fields are managed in [Settings → Custom Fields](/administration/settings/create-and-manage-custom-fields.md).

**Timeline** is always at the bottom of the page, below the main content and side cards on every screen size.

![Contact detail page](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-11b86c525a9b447384eba653ae474fe4a6a43631%2Fcontact-detail.png?alt=media)

> **Where to find it:** Main navigation → Customers, then **Contacts** in the submenu (it appears only while you're in the Customers area); open a contact

## Related guides

* [Creating a contact](/customers-and-work/contacts/creating-a-contact.md)
* [Contact roles explained](/customers-and-work/contacts/contact-roles-explained.md)
* [Edit a contact's details, or where their roles live](/customers-and-work/contacts/edit-a-contacts-details-or-where-their-roles-live.md)
* [Give a contact access to the customer portal](/customers-and-work/contacts/give-a-contact-access-to-the-customer-portal.md)
* [See and browse all your contacts](/customers-and-work/contacts/see-and-browse-all-your-contacts.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/what-the-contact-page-shows.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.