crm-operations

Safely perform bulk CRM updates by orchestrating writes with explicit confirmation gates. The system enforces read-before-write validation and per-record confirmation for destructive actions to prevent accidental data loss.

Manage sequence enrollments and DNC actions by triggering gated CRM operations through plain language requests. The workflow applies safeguards to large operations, ensuring compliance and data integrity across one or many prospects.

The audit trail works by appending every executed CRM status change and deletion to an append-only log file named crm-actions.md. This maintains strict traceability and compliance for all destructive and non-destructive operations.

Yes, you must review prospect data before running a bulk CRM update because the system enforces a strict read-before-write requirement. You will be prompted to review the current state and explicitly confirm actions before execution.

Yes, you can type initial requests in plain language to trigger destructive CRM operations like deletions and DNC actions. The system automatically applies explicit approval gates, requiring your confirmation before executing any irreversible changes.

When managing large prospect operations across sequences, limitations include mandatory per-record confirmations for destructive actions and enforced safeguards for large operations. These constraints prevent unapproved bulk changes and ensure data integrity.