> 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/create-an-interaction.md).

# Create an Interaction

An interaction records a communication event with one or more contacts in the Community Relationships module. Use interactions to track meetings, phone calls, emails, and other engagements with the people in your contact database.

{% 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 CRM

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

{% step %}

#### Select a contact

Click the contact you want to add an interaction for.
{% endstep %}

{% step %}

#### Select an Interaction Type

In the **Notes** section of the contact record, select the **Interaction Type** from the dropdown. Standard interaction types are available, plus:

* **Other, please specify** — Reveals an additional field for entering a custom communication method description.
* **Roster Attendance** — Displays an extra field for uploading attendance files.
* **Internal use only** — Documents notes without counting them as interactions. Internal notes are not included in Direct Contact demographics when using the auto-calculate feature.
  {% endstep %}

{% step %}

#### Enter Notes

Enter the interaction notes in the text field. This field is required.
{% endstep %}

{% step %}

#### Select Program Areas (optional)

Select one or more **Program Areas** associated with this interaction.
{% endstep %}

{% step %}

#### Enter Time (optional)

Enter the duration of the interaction.
{% endstep %}

{% step %}

#### Set the Date and Time

Select the date and time when the interaction took place using the calendar popup.
{% endstep %}

{% step %}

#### Set Privacy (optional)

Click the **Shared with my org** toggle to make the interaction private.

When an interaction is made private:

* Only the creator can view the interaction details in both CRM and CRM exports.
* Other users see: "You do not have permission to view this private note."

{% hint style="info" %}
**TIP:** The toggle icon changes color when privacy is activated.
{% endhint %}
{% endstep %}

{% step %}

#### Add Uploads (optional)

Attach any relevant documents or files related to this interaction.
{% endstep %}

{% step %}

#### Save the Interaction

Click **Add Note** to save the interaction. The interaction will appear on the contact record.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**TIP:** CRM interactions can be used for auto-calculating data in the Direct Contacts module. See [Auto Calculate Direct Contact Demographics](/engage/direct-contacts/auto-calculate-demographics.md) for details.
{% 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/create-an-interaction.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.