FindingcurrentGTM data

Re-logged call summaries crowd the calls out of an agent's evidence

When a call is re-logged as CRM tasks, those tasks can outweigh the call in the evidence.

SymptomMost facts behind an account answer cite CRM tasks that summarize a call, while the call's own transcript barely appears.

Revenue teams re-log the same content across systems. When a call summary lands in a CRM task, the agent sees the call once as itself and again as the task.

Re-logged summaries can easily outnumber the calls they restate, so copies win on volume.

An evidence limit is fixed, so copies push sources out. When re-logged tasks fill it, the transcripts they summarize, with the detail the summary dropped, miss the cut.

Having more facts does not mean having more evidence.

In a synthetic test set of calls re-logged as CRM tasks, filling a 40-fact limit by score kept 15 transcript facts from 14 calls; putting each call ahead of the tasks that restate it kept 40 transcript facts from 26 calls. The set shows the mechanism, not how common it is.

When you link tasks to calls, check that a re-logged summary and a rep's own notes on the same call are not both treated as copies.

Check your setup read-only

Take the 10 most recent agent answers about an account in your transcripts. Count the cited facts that come from logged CRM tasks. Count the cited facts that come from the calls those tasks summarize. If the tasks outnumber the calls they restate, copies are crowding out the primary source.

Passes ifIn all 10 sampled account answers, citations from logged tasks don't outnumber citations from the calls those tasks summarize.

Access needed:agent-transcriptscrm-readcall-data

If it fails: changes to make later (not part of the check)
  1. 01Find logged tasks whose text restates a call summary. Link each task to the call it came from.
  2. 02Put the call in the evidence first when a task and its call are both candidates.
  3. 03Count a task and the call it restates as one source when filling the evidence limit.
Applies ifYour jobs back-fill email or call activity into the CRM as tasks, and your agent's store also holds the call transcripts those tasks summarize.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.