Every "let me get back to you" on a sales call feels safe in the moment. It is often the most expensive sentence in the deal, because the buyer keeps moving while your answer sits in a drafts folder.
Reps say it to avoid being wrong, and being wrong is a real risk. But the phrase has a cost that never shows up on the call recording: the deal loses momentum at the exact moment it had the most. This essay walks through what actually happens after the words leave your mouth, when deferring is genuinely the right call, and why most deferred answers should never have been deferred at all.
What Actually Happens After You Say It?
Picture the moment. Your champion is leaning into the camera. She has pulled two colleagues into the call. She asks: "Can this pull renewal dates straight from our CRM, or do we have to export them?" You do not know. You say the sentence. The call moves on, and it feels fine.
Here is what you gave up. At that moment, your champion cared. The question was hot in her head, the tab was open, and she had the attention of the two people she needs to convince. If you had answered, she would have reacted, pushed back, or said "good, that removes our biggest objection" in front of witnesses. That reaction is the deal moving. It only happens live.
Three days later your answer arrives by email. The question is now cold. She reads your paragraph between meetings, cannot quite remember why the export detail mattered, and files it. Your email did not land in the meeting where it was needed. It landed in an inbox alongside forty other messages, most of them from people she works with every day, some of them from your competitors.
Meanwhile the meetings you were not in have carried on. Buying committees do not pause for vendor follow-ups. If the security review met on Tuesday and your data-residency answer arrived on Thursday, the committee discussed the gap without you. Someone in that room guessed at your answer, and people who guess about vendors tend to guess cautiously. A blank next to your name became a mark against it.
And somewhere in the same evaluation, a competitor's rep got the same question and answered it on the spot, with a product that may well be worse than yours. Buyers read fluency as competence: the vendor who answers now looks like the vendor who will answer quickly after the contract is signed. That inference is not always fair, but buyers make it every day, and it is not crazy. How a company sells is real evidence of how it operates.
None of this shows up in the CRM. The deal dies quietly two stages after the call where you deferred, gets logged as "went dark", and the deferral never gets the blame.
When Is Deferring the Right Call?
Sometimes "let me get back to you" is exactly right, and a rep who never says it is a liability. Defer when:
- The answer needs legal. Custom contract terms, liability caps, indemnities. Improvising these on a call creates commitments your company may not honour, and walking them back later costs more trust than any pause.
- You genuinely do not know and nobody could expect you to. An unannounced roadmap date. A question about an integration your company has never built. Guessing here is lying with extra steps.
- The commitment is above your authority. Discounts beyond your band, custom SLAs, security attestations. "Yes" from the wrong person is worse than "tomorrow" from the right one.
A confident wrong answer costs more than a deferral. It surfaces weeks later in security or legal review, and now you are the vendor who overpromised, which contaminates every other claim you made.
The trap is that deferring drifts from exception to habit. The rep who correctly defers on indemnity language starts deferring on SSO support, then on a pricing question the website answers. Each deferral feels safe individually. Collectively they teach the buyer that talking to you produces homework instead of answers.
How Do You Defer Well?
When you do have to defer, the difference between a weak deferral and a strong one is precision.
- Name the artefact. Not "some information on security", but "our SOC 2 report and the current subprocessor list".
- Name the time. "By tomorrow at 10:00 your time." A specific deadline turns a vague promise into a small contract, and beating it is your first chance to demonstrate reliability.
- Park it visibly, then keep moving. Write the question down where the buyer can see it and return to the agenda. A deferral that derails the call costs twice.
- Deliver exactly what you promised, early. One document, one direct answer to the question as asked. A ten-attachment follow-up buries the answer you owed.
| Weak deferral | Strong deferral |
|---|---|
| "Let me get back to you on that." | "I'll send our SOC 2 report and subprocessor list by 10:00 tomorrow." |
| Answer arrives whenever | Answer beats a stated deadline |
| Generic follow-up email | The exact artefact the buyer asked for |
| Question silently dropped | Question parked on screen, then closed out |
A well-made deferral can even build trust: you showed the buyer what your company does when it owes someone something. But it is damage control, done well. The live answer was still better.
Why Do Most Deferred Answers Already Exist?
Here is the uncomfortable part. Take the questions your team deferred last quarter and check how many were genuinely unanswerable. In most sales organisations, the honest count is low. The CRM question was answered by a solutions engineer on a call in March. The data-residency question is on page four of the security whitepaper. The pricing edge case sits in a Slack thread your top rep could quote from memory.
The organisation knows the answer. The rep on the call does not, and the gap between those two facts is where deals leak. The problem is distribution at the moment of need: the knowledge exists, but it lives in recordings, docs, and heads that the rep cannot reach in the four seconds between the buyer's question and their own reply.
That framing changes what to fix. Better onboarding and searchable call libraries help, but they front-load knowledge and hope the rep retrieves it under pressure. The newer approach is to close the gap during the call itself, which is what a real-time sales assistant actually does: it hears the question and surfaces the organisation's existing answer while the conversation is still live. If you are curious how that retrieval works mid-call, we have written about how real-time AI finds answers on live sales calls. It is the problem Caretta is built around: learning from your docs, past calls, and best reps so the answer that exists somewhere in the organisation shows up on the call where it is needed.
Be clear about what this does and does not remove. Legal terms still go to legal. Real unknowns are still unknown. What shrinks is the long tail of questions your organisation has already answered, so "let me get back to you" goes back to being what it should have been all along: a rare, precise promise instead of a reflex.
Curious how many of your deferred answers already exist inside your organisation? Book a demo.
Frequently asked questions
- Is it bad to say let me get back to you on a sales call?
- It depends on the question. For custom legal terms, unannounced roadmap items, or commitments outside your authority, deferring is the professional move. For questions your organisation has answered many times before, deferring hands momentum to a competitor who answers on the spot.
- What should you do when you don't know the answer on a sales call?
- Defer with precision. Name the exact artefact you will send and the exact time it will arrive, for example the security whitepaper by tomorrow at 10:00. Then park the question visibly and keep the call moving so the deferral does not stall the conversation.
- How quickly should you follow up after a sales call?
- As fast as you can while the buyer still remembers why they asked. Interest decays quickly after the call ends, and your follow-up email competes with everything else in the buyer's inbox. Same day is strong, and beating the deadline you promised builds trust on its own.
- How do you avoid saying let me get back to you?
- Most deferred answers already exist inside the organisation, in past calls, security docs, CRM notes, or a colleague's head. Reps defer because they cannot reach that knowledge mid-call. Better call prep, searchable call libraries, and real-time sales assistants each shrink the gap in different ways.