Sales call guidance: How to end a call with a clear outcome
A customer says, “This looks good. Send me a proposal.”
You send it that afternoon. A week later, you’re still wondering whether they read it, who needs to approve it, and what they were hoping to see in the first place.
The call felt positive, but the proposal had no clear job to do.
A good sales call helps both sides make a decision. Sometimes that means moving forward. Sometimes it means finding out what’s missing or agreeing that now isn’t the right time. The test is whether you leave knowing what changed and what, if anything, should happen next.
1. Decide what the call should help you learn or decide
Before the call, finish this sentence: “By the end of this call, we should know whether…”
Make the answer specific to where the customer is in their buying process:
| Type of call | A useful outcome |
|---|---|
| Discovery | You understand the requirement well enough to decide whether it’s worth evaluating a solution. |
| Demo or walkthrough | The customer has seen how their most important workflow would work and knows what still needs testing. |
| Proposal review | Both sides know whether the scope is acceptable, what needs to change, and who can approve it. |
Suppose you provide maintenance services and a customer asks for a quote covering three locations. You could go into the call aiming to send a quote. A better outcome might be to find out whether all three locations need the same coverage and who will approve the scope. Without those answers, you can send a document, but you may be pricing the wrong work.
2. Check that the customer wants the same outcome
Open with a short agenda and give the customer a chance to change it.
“I thought we could use this call to understand what each location needs, then see whether I have enough information to put together a useful quote. Is there anything else you need to leave with today?”
They might say, “Actually, before we discuss price, I need to know whether you can take over without a gap in service.”
That answer changes what you should cover. Ask when the current agreement ends, what has to stay running during the handover, and what would make a transition feasible. You can come back to pricing once you know whether the timing works.
3. Find out what would hold up the decision
Once you understand the requirement, ask what the customer would need to see before moving forward. You’re trying to learn how the decision works, not push them to make it sooner.
Useful questions include:
- “What would you need to see in the proposal to make a decision?”
- “Who else will review it, and what will they want to check?”
- “Is there a date you’re working towards, or are you still comparing options?”
In the maintenance example, the operations manager might approve the coverage while procurement checks the commercial terms. That tells you what to put in the proposal: a clear breakdown of the work by location and a separate explanation of the terms. It also tells you why a verbal “looks good” from one person isn’t the same as approval.
If the customer doesn’t know the process yet, record that as an open question. Don’t fill the gap with a guessed close date.
4. Leave enough time to agree what happens next
Set aside the last few minutes to summarise what you learned, check it with the customer, and agree what to do next.
“We’ve established that two sites need weekday coverage and the third also needs weekend support. Before I price it, we need the opening hours for that third site. Can you send those by Tuesday? If so, I’ll send the quote by Thursday, with the coverage and price shown separately for each location.”
A useful next step has an action, an owner, a date, and a reason. Here, the customer sends the hours so you can price the right coverage. Your commitment to send the quote on Thursday depends on receiving that information first. Saying so makes it easier for both sides to keep the agreement.
If there’s nothing useful to do yet, don’t invent a follow-up. “Let’s pause until you know whether the current contract can end in June” is clearer than “I’ll check in next week.”
5. Send a recap the customer can correct
Keep the recap short enough to read at a glance. Capture the decision and any open question, not a transcript of the meeting.
Subject: Maintenance coverage — scope and next steps
Thanks for today. We agreed on weekday coverage for sites A and B, with weekend support also needed at site C.
Still open: The weekend opening hours for site C. You’ll confirm those by Tuesday.
My next step: Once I have the hours, I’ll send the location-by-location quote by Thursday for your operations and procurement teams to review.
Please let me know if I’ve missed anything.
Record the same commitment alongside the opportunity. When you or a teammate opens it later, you should be able to tell what was agreed, what you’re waiting for, and whether anything is overdue.
A quick test before your next call
Write down three things: what you want to learn, what you still don’t know, and what decision the call could realistically help the customer make. At the end, compare that plan with what actually happened.
If you learned that the timing won’t work, that’s useful. If you agreed exactly what needs to go into a proposal and who will review it, that’s useful too. A call can feel productive without moving the sale forward. What matters is whether it made the next decision clearer.
Qonvera is a conversational sales CRM built by Aether Solutions.