Grant with Caution: Seven Due Diligence Questions Before an AI Agent Writes to Your CRM

The first generation of AI in the CRM read; the current generation writes. Agents now draft outreach, qualify inbound leads, update opportunity stages, and in some deployments, trigger downstream actions in billing and fulfillment. Every one of those writes is a compliance event, whether or not the vendor's demo acknowledges it.

For IT and revenue leaders, the vetting questions that mattered for a chatbot are insufficient for an autonomous agent. Before granting write access to your system of record, seven questions deserve firm answers.

1. Where does the data actually live—and where does it train?

Ask specifically about data residency for US customers, processing locations, and whether your CRM data contributes to model training. A vendor's blanket "enterprise-grade security" statement is not an answer. If customer PII transits regions without adequate safeguards, your privacy obligations under state laws like the California Consumer Privacy Act travel with it.

2. Is every agent action logged at the same fidelity as a human user?

Your audit trail is only as strong as its weakest writer. If the agent updates a record outside standard API logging, or if its changes are attributed to a generic service account, you lose the ability to reconstruct who—or what—altered a customer record and why. Demand per-action attribution and immutable logs.

3. What requires human approval, and who can change that setting?

Human-in-the-loop controls should be configurable, enforced, and owned by someone inside your organization—not buried in vendor defaults. Which actions are autonomous today? What is the approval path for expanding that scope? Get it in writing.

4. What happens when the agent is wrong?

An agent that misroutes a lead is an annoyance; one that updates consent flags, deletes records, or sends representations to customers is a regulatory exposure. Ask for the error taxonomy, the rollback capability, and evidence of how the vendor handles hallucinated or unauthorized actions in production.

5. Who bears liability under the contract?

Most AI vendor agreements still allocate risk as if the software were a spell-checker. Probe indemnification for agent-caused errors, caps on liability relative to the blast radius of autonomous actions, and whether the vendor will name you in breach notification obligations when its systems malfunction.

6. How does the agent respect your existing governance?

Your CRM likely enforces field-level permissions, consent management, and retention rules. Does the agent inherit those controls natively, or does it operate on an elevated service account that bypasses them? An agent that sidesteps your permission model is a shadow administrator with a friendly interface.

7. What is the exit plan?

Finally, ask what happens when the relationship ends. Can you export agent-generated records, logs, and decision rationale? Will the agent's contributions be distinguishable from human activity in your historical data? Lockdown on egress is a red flag for any system touching regulated customer data.

The Standard to Set

None of these questions argues against AI agents—the efficiency gains in revenue operations are real. The argument is for symmetry: an autonomous actor in your system of record should meet the same standards of accountability, logging, and control that you would demand of a new employee with administrator rights.

Vendors that welcome these questions are partners. Vendors that deflect them have told you everything you need to know.