> For the complete documentation index, see [llms.txt](https://docs.clearout.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clearout.io/data-pulse/features-and-functionality.md).
# Features & Functionality
The core functionality of the **Data Pulsing Engine** is to act as a real-time data quality layer to validate and qualify your contacts in CRMs (e.g., HubSpot, Salesforce, Zoho) by eliminating any external automation platforms/tools.
### Data Verification & Validation
Currently, Data Pulse supports **email**, **phone**, and **name** fields in your contact record for validation.
* **Email Verification** - Classifies addresses as Valid, Deliverable, Risky, or Invalid. It also flags disposable email providers.
* **Name Validation** - Detects gibberish, random strings (e.g., `asdfgh`), and placeholder values (e.g., `N/A` or `Test`).
* **Phone Number Validation** - Verifies international formats and retrieves metadata, determining line type as Mobile, Fixed, or VoIP, along with carrier, location, and timezone details.
### Reports and Insights
#### Weekly Reporting
A data quality report is generated and delivered every **Monday**. The report summarizes key validation metrics, trends, and data health indicators based on processed contact data.
**Enable or Disable Weekly Reports**
Go to the **Data Pulse Settings** page to enable or disable weekly report delivery.
{% hint style="info" %}
You can opt in or opt out of receiving weekly reports at any time from the [**Settings page**](http://app.clearout.io/settings/data_pulse)**.**
{% endhint %}
#### Analytics Dashboard
A live view of validation trends, allowing teams to see which sources are providing the highest (or lowest) quality data.
The dashboard reveals:
* Patterns in valid, invalid, and risky data
* Common data issues (e.g., increased gibberish names, disposable emails, etc.)
* Trends affecting overall data health
These insights help **monitor and track data quality** over time.
---
# 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://docs.clearout.io/data-pulse/features-and-functionality.md?ask=&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.
