How to Reflect on a Sales Call: The Recap Isn't the Reflection
Most 'call reflection' is a recap for the CRM. The version that actually changes how you sell asks a different set of questions entirely.
2026-08-09 · SARA — KEEL'S AI DEAL ASSISTANT · GETKEEL.IO
The call ends. You have two options, and they look almost the same from the outside.
Option one: open the CRM, fill in what was discussed, move to the next thing.
Option two: sit with it for ninety seconds and ask what actually happened.
Most reps only ever do the first one — and call it reflection.
The recap everyone calls reflection
A recap is a record of the call. What was on the agenda, what questions came up, what the next step is supposed to be.
It's useful. It's also not reflection — it's transcription with extra steps, just done from memory instead of a tape.
A recap answers "what happened." It never gets around to asking what you noticed while it was happening.
Recap vs. reflection
| | Recap | Reflection | |---|---|---| | Answers | What was discussed | What changed | | Written for | The CRM, your manager | Yourself, next time | | Source | Memory of the agenda | The read you had in the room | | Decays | Slowly — facts hold | Fast — the felt sense fades first | | Question it asks | "What happened?" | "What do I do differently?" |
The left column is a log. The right column is the only one that changes how you sell the next call.
Why the recap wins by default
Logging a call is a habit most sales orgs already train hard. Stage, next step, done — the muscle memory is real.
Nothing trains the second habit. Nobody hands you a form for "what felt off" the way they hand you one for "deal stage."
So the recap happens because it's asked for, and the reflection doesn't, because nobody asked.
What an actual reflection sounds like
Three questions, in order, before you open anything else.
What changed. Not what was discussed — what's different now than before the call started.
What's still sitting with you. One line, one pause, one thing they said that you keep coming back to.
What you'd do differently next time. Even one sentence. Especially if it stings a little.
That's the whole method. Answering it out loud takes less time than logging the call did.
Timing is the whole trick
We've written before about how sharp the read on a meeting is in the first few minutes after it ends, and how fast that sharpness fades.
The same window applies to a phone call, a video call, any call.
Do the reflection at your desk an hour later, and you're not reflecting on the call anymore. You're reflecting on a summary of a summary.
Say it before you log it
Most reps don't skip reflection because they don't believe in it. They skip it because the recap is the only one with a field waiting for it.
Sara's built for the other one: talk through what you noticed the moment the call ends, before the recap swallows it. Founders Club is invite-reviewed. Apply at getkeel.io/founders.
The meeting is the performance
The call is the performance. The reflection right after is the work — the part that actually changes how the next one goes.
Log the recap if your CRM needs it. Just don't mistake it for the thing that makes you better at this.
That happens in the ninety seconds most reps skip.
By the team at Keel. We're building Sara, an AI deal assistant for the moments that don't get recorded.