When an objection comes up on a live call, the first useful response is often a question. The buyer may see a real constraint, misunderstand the proposal, or not see enough value to continue. Find out which situation you are facing before answering. The examples below are conversation prompts, not scripts or guarantees.
Acknowledge, clarify, respond, check
Acknowledge the concern without pretending to agree with an assumption you have not tested. Ask one question that narrows it. Respond with the relevant evidence you actually have, then check whether you addressed the concern. If you still do not understand it, stay with the question rather than adding a longer pitch.
Listen for the difference between a question and a refusal. A buyer who says the project is not a priority may be giving you a clear answer. You can ask what drives that priority, but should respect the decision rather than treating every response as something to overcome.
'It is too expensive'
Clarify the comparison. The concern might be total budget, expected value, payment timing, or another proposal. Each needs a different discussion. Do not jump to a discount before you understand the constraint, and do not offer commercial terms you are not authorized to provide.
If the issue is value, return to the buyer's confirmed problem and the outcome they care about. Use their evidence when discussing impact. If you cannot substantiate a savings figure, explain what information would be needed instead of presenting a precise but invented estimate.
'We already use another solution'
An existing solution may be doing its job well. Ask what works and whether any part of the process still creates difficulty. A useful comparison starts with the buyer's requirements, not unsupported claims about a competitor.
If a real gap exists, check whether it matters enough to investigate. Consider the effort of changing the process alongside any proposed benefit. When your product does not meet the requirement, say so and avoid presenting a planned feature as an available capability.
'We need approval' or 'The timing is wrong'
Approval is a decision process to understand, not a reason to pressure your contact. Ask who needs to review the proposal, what evidence they need, and whether your contact wants help preparing it. Do not assume that the person on the call controls another team's decision.
For timing, identify the dependency: a renewal, budget cycle, competing project, or missing owner. Agree on a follow-up only if there is a useful trigger. Sending a generic reminder every week does not resolve a genuine dependency.
Bring evidence into the live exchange
Sales Copilot can suggest responses on screen during a live session, using the conversation and the context you provide. Before the call, attach approved product details, limitations, and relevant material to the Prospect and select a Playbook. You can request help or steer the copilot toward a short clarifying question. Review each suggestion against the buyer's concern and your actual authority to make commitments.
Afterward, use the transcript and Debrief to examine the exchange. What did the buyer mean? Which question helped clarify it? Did your response rely on confirmed facts? Record the unresolved issue and agreed next step in the Prospect context, and review the Account Action Plan before the next conversation. Rehearse the difficult question with a text counterpart to work on your response before it comes up again.