> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# CRM data quality automation: validation and safe writes

> Ask your agent to propose CRM repairs with field-level evidence.

[Agent guide: CLI and SDK instructions →](/docs/guides/crm-data-quality-automation)

## 1. Have your context ready

Identify the CRM, target fields, trusted sources, ownership rules, and which changes require human review.

## 2. Ask your agent

Paste this into your agent, then provide your task and example inputs when it asks:

```deepline-prompt theme={null}
/deepline-gtm Audit this CRM sample with Deepline. Preserve record identity and current values. Propose field-level repairs with evidence, freshness, reason, and the authorized writer. Hold identity merges, conflicting values, owner changes, deal-stage changes, and commercial terms for review. Do not overwrite trusted values or execute repairs yet. Show the sample, expected usage, and the read-back plan before any approved writes.
```

Complete any requested sign-in yourself. Give the agent the missing information before approving execution. Provider-backed work can incur usage.

## 3. Review the result

Each approved write has an attributable proposal and a verified destination result. A write timeout is an uncertain outcome to reconcile before repeating the mutation.

Ask your agent:

```deepline-prompt theme={null}
/deepline-gtm Compare the result with the acceptance rule we agreed. Show the evidence for accepted and rejected outcomes, unresolved questions, and recorded Deepline usage where work ran. If work is still running or a response is uncertain, inspect the original saved execution before proposing another request. Explain the next decision I need to make.
```

Approve a larger job, recurring work, or external changes only after reviewing that decision.

## Check your understanding

Does a successful provider response authorize overwriting a protected CRM field?

> **Show the answer**
>
> No. Evidence and write authority are separate. Preserve protected values
> unless the stated policy authorizes the change.

## Related guides

* [Validate Incoming CSV Files Before CRM Enrichment](/docs/human/guides/validate-incoming-csv-files)
* [Your first Deepline workflow](/docs/quickstart)
* [Query Database](/docs/human/database-access)
* [Why CRM provenance matters](/docs/guides/data-provenance-in-crm)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.