# Direct Contact Summary

#### Location

This panel appears on the following dashboards:

* [User Dashboard](/analyze/impact-dashboards/user-dashboard.md)

#### Modules Included

* Direct Contacts

#### Filters

**Applied Filters**

* **Viewable records** — Only Direct Contacts the current user has permission to view are included.

**Non-Applicable Filters**

* **Sites** — Direct Contacts do not have a site field.
* **Interventions** — Direct Contacts do not have an intervention field.
* **Projects** — Direct Contacts do not have a project field.
* **Action Plans** — Direct Contacts do not have an action plan field.
* **Settings** — Direct Contacts do not have a setting field.
* **Verified** — Direct Contacts do not have a verification status field.
* **Session Date Range** — Direct Contacts do not have session occurrences.
* **Primary Curriculum** — Direct Contacts do not have a curriculum field.
* **Collaborator** — The collaborator filter maps to the created-by user for Direct Contacts.

#### Calculations

1. PEARS retrieves all viewable Direct Contacts that match the current dashboard filters.
2. Contacts are grouped by their date range (time period).
3. Within each date range, contacts are further grouped by contact method (Phone, In-Person, Email, Video Conference, Social Media, Text, Other).
4. A stacked bar chart is displayed where:
   * The x-axis shows the date range categories.
   * Each stacked segment represents a contact method.
   * The segment height represents the count of contacts using that method in that date range.

#### Additional Notes

* Contact methods are color-coded in the chart legend for easy identification.


---

# Agent Instructions: 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:

```
GET https://support.pears.io/analyze/impact-dashboards/panels/direct-contact-summary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.