The ten minutes after a visit
A rep walks out of a client's office. The next visit is in twenty-five minutes, across town. Right now, every detail is sharp: who was in the room, the objection about price, the competitor's offer they mentioned twice, the order they hinted at for next month.
This is exactly when the CRM wants its form filled in — company, contact, stage, next step, notes — on a phone, in a car park. So the rep thinks "I'll do it tonight". Tonight becomes Friday afternoon.
What a Friday-afternoon CRM looks like
By Friday, notes are written from memory and compressed to "good meeting, follow up". Stages are updated in bulk. The price objection is gone, and so is the competitor's name.
The manager opens a tidy CRM that describes last week's mood rather than this week's reality. Every forecast built on it inherits the lag. And when the rep leaves the company, what they knew about each account leaves with them.
It's not discipline, it's friction
It's tempting to call this a discipline problem and add mandatory fields. That makes it worse. Every field is a small decision; typing on a phone is slow; switching apps between visits breaks focus. And for the rep, the effort mostly pays off for someone else — the manager, the forecast, the next person to own the account.
More friction doesn't produce more data. It produces less data, or worse data entered to make a warning go away.
Move the capture to the moment — and to the voice
Teams that keep a living CRM tend to follow the same five rules:
- Capture within minutes, not days. The best recap is the one made before the next visit.
- Use the channel reps already have open. For most field teams in Portugal and Spain, that's WhatsApp.
- Speak, don't type. Thirty seconds of speech carries more than a form — including the tone, the doubts and the exact words the client used.
- Let software do the filing. Which company, which deal, which field: that's the system's job, not the rep's.
- Confirm instead of guessing. When "Silva" could be two clients, the right move is a quick question, not a duplicate record.
What that looks like with emily
With emily, the recap is a WhatsApp voice note or a quick call from the car. An illustrative exchange:
The note lands on the right deal or company, dated, in the rep's own words rather than a transcript. If the name is ambiguous, emily asks which client was meant before writing anything. A photo of a business card becomes a new contact; a photo of an order sheet becomes a note on the deal. See voice CRM, visit reports and business cards to CRM.
What managers should change
- Ask for a 30-second recap after every visit, not a completed form.
- Measure "visits with a note the same day", not the number of fields filled in.
- Read the notes and react to them. Reps notice quickly whether anyone does.
- Give reps something back: a briefing before the next visit built from what they logged last time.
- Use a checklist, not a form. Our sales visit report template lists what a good recap covers — who was there, what they need, objections, next steps.
The bottom line
The CRM doesn't fail because reps refuse to use it. It fails because it asks at the wrong time, on the wrong screen. Put capture where the rep already is — the car, the phone, their own voice — and the CRM fills itself.
For the bigger picture, read our guide to WhatsApp for sales teams, or compare a traditional CRM with a voice CRM.