Why reps don't update the CRM, and how to capture context anyway
Most of a rep's week already goes to non-selling work, so CRM updates slip. Here's what gets lost when logging waits, and how to capture context while the conversation is still fresh.
Key takeaways
- Reps say 70% of their time goes to non-selling work, according to Salesforce's 2024 State of Sales report 1. CRM updates compete for that same time, and they usually lose.
- Deal values and stages make it into the CRM. Context, like who really signs off and what was promised, mostly stays in people's heads, and memory fades fast 2.
- The fix is to capture in the moment, in the channel reps already use, and add structure afterwards with a human check.
Why the CRM stays half empty
When the CRM is half empty, leaders tend to call it a discipline problem and add another required field. That rarely helps, because the real cost is the interruption. Logging a call means stopping, opening the CRM, finding the right account and turning a conversation into form fields, usually at the end of the day, when the details are already fading.
Salesforce's sixth State of Sales report, based on 5,500 sales professionals in 27 countries, found that reps spend 70% of their time on non-selling tasks such as admin work and meeting prep 1. Every extra field adds to that number.
What gets lost first
The fields someone checks in the pipeline review get filled in. Much of what actually decides an account stays in people's heads:
- Who signs off, and who influences the decision.
- What was promised, by whom and by when.
- Sensitivities, like a topic that puts the customer on the defensive.
- People changes, like a champion moving to another team.
This kind of detail fades fast. The forgetting curve, first described by Ebbinghaus and replicated by Murre and Dros in 2015, shows that most forgetting happens soon after we learn something 2. A note written the next morning is already a summary.
Capture first, structure later
The practical rule: make logging as quick as sending a text. If a rep already sends their manager a voice note after a site visit, that voice note can be the record.
- Accept the formats your team already uses: voice notes, screenshots, quick texts and meeting recordings.
- Meet reps where they are. For many teams that's WhatsApp or Telegram, already open on their phone.
- Separate capture from structure. Save what was said first, then sort it into people, commitments and risks.
- Flag anything uncertain for a person to resolve, like whether a note refers to one site or the whole account.
- Keep the source and date of every fact, so anyone can see where it came from.
Where the CRM fits
None of this replaces your CRM. It stays the system of record for accounts, contacts, stages and amounts. The change is in the context layer, which no longer depends on one person's memory and is there for whoever owns the account next.
How ARC approaches it
ARC takes voice notes, screenshots, messages and recorded meetings over WhatsApp, Telegram or its own app, pulls out the facts that matter and links each one to the right account. Nothing is saved until someone confirms it, and every fact keeps its source and date. The Experience page has a guided demo of this flow, with fictional data.
FAQ
Why don't sales reps update the CRM?
Because logging competes with selling. Salesforce reports that reps already spend 70% of their time on non-selling tasks 1. When an update means opening a screen and filling in fields, it gets pushed to later and loses detail.
What information is usually missing from the CRM?
Relationship context: who decides, who influences, commitments, sensitivities and people changes. Amounts and stages are usually there, because they get reviewed in pipeline meetings.
Can a WhatsApp voice note become a CRM record?
Yes, as long as it's turned into structured facts and someone confirms anything uncertain. That's the workflow capture tools like ARC automate.
Sources
See ARC with your own team.
The guided demo shows, in about a minute, how one conversation becomes memory and a next step.