PreviewYou're previewing CRO AI Momentum. Sign in to use it.Sign in
← All lessons
L2 · Data and CRM foundations for revenue AI7 min read

Activity and conversation data: capture, consent and grounding

The richest revenue data is not typed into fields. It is in emails, meetings and calls. AI can now capture and use it — which raises both value and responsibility.

Capture

Activity capture tools log emails and meetings to the right CRM records automatically. Conversation tools record and transcribe calls. Together they give AI the context to summarize deals, coach sellers and draft follow-ups.

Consent and privacy

  • Recording: notice and consent rules for recording calls differ by country and, in the US, by state. Get legal to set the standard and build it into the meeting tool (announcement, opt-out).
  • Personal data: transcripts and emails contain personal data about prospects and customers. Decide retention periods, access rights and whether data may be used to train vendor models.
  • Customer contracts: some enterprise customers forbid recording or AI processing of their calls. Respect flags in the CRM.

Grounding

An AI that writes to customers should be grounded in specific, approved context — the real interaction history, the approved product and pricing content — rather than writing from its general training. Salesforce's engineering team describes its lead-nurturing agents as constrained to predefined workflows and structured outputs, with every response grounded in specific context such as previous interactions and engagement signals.

Practical rules

  1. One approved capture tool per type, connected to the CRM.
  2. A written data-use standard: what AI may read, store and send.
  3. Grounding sources listed for each agent; everything else is off-limits.
  4. A log of what agents sent, so you can audit and fix.

What this means for the CRO

Conversation data makes coaching, forecasting and agents far better, and it is also the data most likely to cause a privacy complaint. Sponsor a short, clear data-use standard with legal and security, and insist that every customer-facing agent has a named list of grounding sources and a message log.

That standard is also a selling point: enterprise buyers increasingly ask how you use their data in AI.

Ask your RevOps and legal leads to bring you the draft standard within a month, and review it again whenever you add a new agent or a new country.

Real example

Salesforce Engineering (April 2026) describes how its Agentforce lead-nurturing agents generated over $100 million in pipeline and more than 10,000 opportunities in the SMB segment, while constraining responses to predefined workflows and structured outputs and grounding every response in specific context such as previous interactions and engagement signals. Source: Salesforce Engineering — How Agentforce lead nurturing agents generated $100M+ pipeline under rate-limited infrastructure (Apr 20, 2026) ↗

Use it

Quick check · 3 questions

  1. 1.What does 'grounding' mean for a customer-facing agent?

  2. 2.Who should set the call-recording consent standard?

  3. 3.Why keep a log of what an agent sent?

0 of 3 answered

Sources

Last reviewed 2026-10-01.