Sales in the age of AI

Before you let an AI agent touch your CRM: what should you check? A checklist

Disclosure: ThePipelineBots is published by Uassist.ME (uassistme.com), which sells outsourced CRM cleanup and sales-support teams. CRM data work is one of its services, so weigh our take with that in mind. Every figure below links to its source.

Short answer: Check what the agent is allowed to change, who owns it, and how you'd undo its work, before you connect it. SaaStr says a vendor's agent deleted almost every opportunity in its Salesforce, and a snapshot SaaStr's own agent had taken that morning got the data back. G2's 2026 survey suggests this kind of oversight work is now a normal cost of running agents.

What happened at SaaStr? (The ugly)

SaaStr's Jason Lemkin writes that "an agent from a well-known vendor deleted almost every opportunity in our Salesforce." SaaStr had connected it "as a favor". It happened on a Friday, right after the team's weekly pipeline cleanup, and "the vendor had no rollback" (SaaStr, Oct 16, 2026).

What saved them: SaaStr's own agent, 10K, "had kept its own snapshot of the pipeline from about 11am that morning and restored it once Amelia confirmed." SaaStr doesn't name the vendor. This is one company's account, not a study.

In the same piece, SaaStr says the three tools it tested on its Salesforce all had read and write access. Claudeforce restricts itself to read-only during its beta, while Replit and Lovable "default to read-only and confirm with you in writing before they write anything back to Salesforce" (same source). Those are SaaStr's observations, not vendor documentation we've checked.

What does survey data say about overseeing agents? (The bad)

G2's 2026 AI Agents report surveyed 1,019 B2B decision-makers in July 2026 (G2, last updated Oct 14, 2026). G2 runs a software-review marketplace and sells marketing and buyer-insight services to software vendors (this report is published on its vendor site, sell.g2.com), so it has a stake in this topic. G2 says its review data covers over 2,500 reviews in its AI Agent Builder category from March to August 2026, and that generative AI models were used to "define the study's focus areas, optimize survey design, and analyze results."

Finding (G2 survey, July 2026) Share
Companies reporting agent-related security incidents in the past year 36%
Spend 6 or more hours a week overseeing agents (share of organizations) 31%
Oversight and rework consume more than a quarter of expected productivity gains 45%
Higher-than-expected agent operating costs 46%
Require human quality review before production 52%
Keep a central AI agent registry 27%
Have real-time observability into unusual agent behavior, costs or risks 14%

G2 also reports that the most time-consuming oversight tasks are reviewing agent outputs (26%), fixing agent errors (24%) and approving agent actions (22%). G2's review data (not the survey) shows 48% of B2B software buyers prefer agents with guardrails, and only 7% would hand over total autonomy (same source).

The survey doesn't break these figures out for CRM or sales agents. In G2's separate review data from its AI Agent Builder category, sales development use cases "have more than halved" year over year (same source). That's review data from one category, not market share.

Do the CRM vendors' own agents limit what they can change? (The good, with caveats)

A separate identity and a named manager make an agent's actions easier to trace. Neither vendor publishes a rollback guarantee on these pages.

What should you check before connecting an agent to your CRM?

All of these are our suggestions, drawn from the sources above. They aren't a vendor standard or legal advice.

  1. Start read-only. Give the agent read access first and add write access one object at a time. (Our suggestion.)
  2. Scope the permissions. Use a dedicated integration user or agent identity, not an admin's login, and block delete and mass-update rights unless you need them. (Our suggestion.)
  3. Keep a backup you control. Take a snapshot or export of opportunities, accounts and contacts before go-live and on a schedule, and test a restore once. Don't rely on the vendor's rollback. (Our suggestion.)
  4. Test in a sandbox first, with a copy of real data, before you touch production. (Our suggestion.)
  5. Name a human owner who approves the agent's setup, reviews its changes and can switch it off. (Our suggestion.)
  6. Require approval for bulk or destructive actions, such as deleting records, merging, or changing stages or owners. (Our suggestion.)
  7. Log and review what it changed, using field history or an audit trail, daily at first. (Our suggestion.)
  8. Keep a fresh backup before any agent runs, especially right after a cleanup. SaaStr's wipe happened right after its weekly pipeline cleanup. (Our suggestion.)
  9. Budget for oversight time. G2's survey suggests supervising agents takes real hours each week. (Our suggestion.)

Related: Do you need to clean your CRM before using an AI sales agent? and Can AI SDR agents replace your SDRs yet?

FAQ

Can an AI agent delete records in Salesforce? Yes, if it has write and delete access. SaaStr says a vendor's agent deleted almost every opportunity in its Salesforce, and the vendor had no rollback (SaaStr, Oct 16, 2026).

How did SaaStr get its data back? Its own agent, 10K, had kept a snapshot of the pipeline from that morning and restored it once a team member confirmed (same source).

How much time do companies spend overseeing AI agents? In G2's July 2026 survey of 1,019 B2B decision-makers, 31% of organizations said they spend 6 or more hours a week overseeing agents. 45% said oversight and rework consume more than a quarter of expected productivity gains (G2).

Should an AI agent get write access to my CRM on day one? Our suggestion is no. Start read-only, back up your data, and add narrow write permissions with a named human owner and approval for bulk changes.

Are Salesforce Hunter and Microsoft's Sales Development agent generally available? Not yet. Salesforce lists Hunter as a pilot with general availability planned for November 2026, and Microsoft's Sales Development agent is in preview.

Sources (opened 2026-10-19)

  1. SaaStr (Jason Lemkin), "Going Headless: Claudeforce vs. Replit vs. Lovable … The Agents #016," Oct 16, 2026 (page metadata). First-hand account; vendor unnamed. https://www.saastr.com/going-headless-claudeforce-vs-replit-vs-lovable-agents-picking-our-vendors-and-two-of-our-agents-built-their-own-inbox-to-talk-behind-our-back-the-agents-016/
  2. G2, "Agentic Chasm: 2026 AI Agents Report," last updated Oct 14, 2026. Survey of 1,019 B2B decision-makers, July 2026, plus G2 review data. Interested party (software-review marketplace that sells services to software vendors; report published on sell.g2.com). Methodology: survey plus 2,500+ AI Agent Builder reviews (Mar–Aug 2026); G2 says generative AI was used in survey design and analysis. https://sell.g2.com/g2-2026-ai-agents-insight-report
  3. Salesforce, "Salesforce Expands Agentforce With a New Portfolio of AI Agents Built for High-Value Work," Sept 11, 2026. Vendor-reported. https://www.salesforce.com/news/stories/agentforce-job-ready-ai-agents/
  4. Microsoft Learn, "Activate Sales Development agent (preview)," updated Aug 21, 2026. Vendor documentation, prerelease. https://learn.microsoft.com/en-us/dynamics365/sales/sales-dev-agent/activate-agent