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.
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
- 01Find logged tasks whose text restates a call summary. Link each task to the call it came from.
- 02Put the call in the evidence first when a task and its call are both candidates.
- 03Count a task and the call it restates as one source when filling the evidence limit.