> For the complete documentation index, see [llms.txt](https://support.pears.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pears.io/engage/community-relationships/add-a-contact.md).

# Add a Contact

This article walks through the steps to create a new person record in the Community Relationships (CRM) module.

![Screenshot: The CRM Add Person form showing the Title dropdown, Name field, Unit selector, Organization field, phone number fields, email section, and mailing address fields](/files/js4NTMVspWIqOm9bxKvj)

{% hint style="info" %}
**TIP:** The red asterisk **\*** next to the heading of a field indicates that the field is required.
{% endhint %}

{% stepper %}
{% step %}

#### Navigate to Community Relationships

From the PEARS homepage, hover over the **Engage** menu and click **Community Relationships**.
{% endstep %}

{% step %}

#### Click Add Person

On the Community Relationships list page, click the **Add Person** button.

![Screenshot: The Community Relationships list page with the Add Person button highlighted in the top-right area](/files/ic55oIxjeEjYow4pg1rf)
{% endstep %}

{% step %}

#### Select a Title (optional)

In the **Title** dropdown, select the contact's title if applicable (e.g., Mr., Ms., Mrs., Dr.).
{% endstep %}

{% step %}

#### Enter the Contact's Name

In the **Name** field, enter the contact's full name. This field is required.
{% endstep %}

{% step %}

#### Select a Unit

In the **Unit** field, select the extension unit associated with this contact. This field defaults to your primary unit.
{% endstep %}

{% step %}

#### Select an Organization (optional)

In the **Organization** field, select the site or organization associated with this contact.
{% endstep %}

{% step %}

#### Enter Phone Numbers (optional)

Enter the contact's phone numbers in the available fields:

* **Mobile Phone**
* **Home Phone**
* **Work Phone**
  {% endstep %}

{% step %}

#### Add Email Addresses (optional)

In the **Email** section, enter one or more email addresses for this contact. If you add multiple email addresses, select one as the **Primary** email. Click the **Add Email** button to add additional email addresses.
{% endstep %}

{% step %}

#### Enter Mailing Address (optional)

Fill in the contact's mailing address using the following fields:

* **Address**
* **Address Line 2**
* **City**
* **State**
* **Zip Code**
  {% endstep %}

{% step %}

#### Select Categories (optional)

In the **Categories** field, select one or more categories to organize this contact. Categories are specific to your organization.
{% endstep %}

{% step %}

#### Upload a Picture (optional)

In the **Picture** section, click the upload area to attach a photo of the contact.
{% endstep %}

{% step %}

#### Add Notes (optional)

In the **Notes** field, enter any additional information about this contact.
{% endstep %}

{% step %}

#### Save the Contact

Click **Save** to create the contact record. After saving, you can continue to add [demographics](/engage/community-relationships/contact-demographics.md) and [communication preferences](/engage/community-relationships/communication-preferences.md).
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**NOTE:** A contact must have at least a name and unit before it can be saved. All other fields are optional and can be filled in at any time by editing the contact record.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.pears.io/engage/community-relationships/add-a-contact.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.