← Blog
Sales Playbook

How to Make a Sales Call: Structure, Scripts, and Examples

Kernous team · July 2, 2026
How to Make a Sales Call: Structure, Scripts, and Examples

A sales call is not a presentation. It is a structured conversation — and the rep who does most of the talking is usually the one who loses.

Most reps know this in theory. In practice, the call starts, the prospect says something unexpected, and the structure falls apart. What follows is either a frantic pitch or an awkward silence that neither side knows how to close.

This guide covers how to build a call structure that holds up under pressure, how to write a script that sounds human, and what to do when the conversation goes somewhere you did not plan for.

Key Takeaways

  • A sales call is a structured conversation, not a presentation — the rep should be listening more than talking.
  • The fifteen minutes before a call shape the first three minutes more than any script.
  • Every sales call has five phases: open, discover, present, handle objections, advance. Each has a distinct goal.
  • Real-time AI helps reps stay on track when unexpected moments pull the conversation off-structure.

Sales Call vs. Cold Call: What's the Difference?

A cold call is unsolicited. The prospect did not ask to speak with you, so the goal is to earn enough attention to create a next step. The first ten seconds are spent fighting the instinct to hang up. (For more on that, see our guide to cold calling tips.)

A sales call is expected. The prospect has agreed to a conversation, which means the first barrier is already cleared. The goal is not to prove you deserve their attention — it is to use that attention well. That usually means confirming the agenda, understanding the problem, connecting the right parts of your solution, and leaving with a clear next step.


Before the Call: 15 Minutes of Preparation

What a rep does in the fifteen minutes before a call determines how the first three minutes land. Not the fifteen hours — fifteen minutes.

Five things to confirm before dialing:

  1. Their role and tenure. A rep who started six months ago has different pain than a director who has been in seat for three years.
  2. One recent signal. A new hire, a product launch, a funding round — something that happened in the last 30 days that gives you a reason to reference their current moment.
  3. Your hypothesis. Based on what you know, what problem are you guessing they have? Write it in one sentence. You will test this in discovery.
  4. Your ask for the next step. Know before the call starts what a successful outcome looks like — a scheduled demo, a technical call, a proposal review. Do not figure this out at the end.
  5. Time confirmed. Check whether they accepted the calendar invite. If the meeting was booked more than a week ago, send a same-day confirmation so the call does not feel like a forgotten calendar hold.

How to Structure a Sales Call: Five Phases

Every effective sales call moves through five phases. Each one has a single goal. Skipping or rushing a phase is where most calls fall apart.

PhaseGoalWhat to avoid
OpenConfirm time, agenda, and conversation formatJumping straight into a pitch
DiscoveryUnderstand pain, impact, timing, and decision processAsking checklist questions without listening
PresentConnect the solution to what the prospect saidGiving a full product tour
Handle objectionsExplore concerns and missing informationDefending too quickly
AdvanceAgree on a specific next stepEnding with "I'll follow up"

Phase 1: Open (90 seconds)

Goal: Set the agenda, confirm time, and establish that this will be a two-way conversation.

Most reps skip this and go straight into their pitch. The prospect then spends the next ten minutes waiting for the call to feel relevant to them.

A clean open sounds like this:

"Thanks for making time. I have us down for thirty minutes — does that still work? Quick plan: I want to spend most of this understanding what you are working on, and if it makes sense, I will show you how we approach it. Sound good?"

Three things happen here: you confirm the time commitment, you signal that discovery comes before pitch, and you get a micro-yes that puts the prospect in an active mode rather than a passive one.

Phase 2: Discovery (8–12 minutes)

Goal: Understand the problem, the impact, the timeline, and how decisions get made.

Discovery is where most calls are won or lost. Reps who rush through it to get to the demo are solving for their own comfort, not the prospect's need.

The four things discovery should answer:

  • What is the actual problem? (Not the symptom — the underlying cause)
  • What happens if it does not get solved? (Impact quantifies urgency)
  • Why now? (What changed recently that made this a priority)
  • Who else is involved in the decision? (So the follow-up reaches the right people)

Questions that open up discovery:

  • "What made you want to take this call?"
  • "Walk me through how your team currently handles [process]."
  • "When this breaks down, what does that look like in practice?"
  • "If you solved this in the next quarter, what would be different?"

One question at a time. Let the answer breathe before the next one. The more the prospect talks, the more useful the rest of the call becomes.

Phase 3: Present (5–8 minutes)

Goal: Connect what they told you in discovery directly to what you offer.

This is not a product tour. It is a targeted bridge from their stated pain to your solution. Every feature you mention should trace back to something they said.

The structure:

"You mentioned [specific problem they named]. The way we approach that is [relevant capability]. What that usually means for teams like yours is [outcome they care about]."

If you caught three pain points in discovery, address those three. Do not add four more features because you think they are impressive. Relevance beats completeness every time.

Phase 4: Handle Objections

Goal: Explore concerns without defending against them.

An objection is not a rejection. It is information about what the prospect needs to feel confident moving forward. The reps who treat objections as attacks spend the call defending. The reps who treat them as questions spend the call solving.

Common objections and what they usually mean:

  • "We already have something for that." — They need to understand the difference, not hear why their current tool is wrong.
  • "The timing isn't right." — Either budget or priority. Find out which.
  • "I need to think about it." — They are missing something to make a decision. Ask what.
  • "It's too expensive." — They have not connected the cost to the value yet. Go back to impact.

The most effective response to almost any objection starts with a question, not an answer:

"That makes sense — can you say more about what you mean by [objection]?"

Phase 5: Advance (2–3 minutes)

Goal: Leave with a clear, specific next step that both sides have agreed to.

"I'll follow up" is not a next step. It is a way to end a call without commitment.

A real next step has three elements: who does what, by when, and what happens after that. Get it on the calendar before the call ends, not in a follow-up email that may or may not get a response.

"Let's get the technical call on the calendar now — does Thursday or Friday work? I'll send the invite with an agenda so your team knows what to expect."


How to Make a Sales Call Script

A fully scripted call sounds scripted. The moment the prospect says something unexpected — which they will — the rep is lost, searching for the next line in a document that no longer applies.

What works instead is a framework with flexible language: you know what each phase is trying to accomplish, and you have a handful of phrases ready for the transitions. The exact words adjust to the conversation.

Sample opening (adapt to your voice):

"[Name], good to connect. I have us for [time] — does that still hold? Here is what I was thinking: I want to spend the first part understanding what you are working on, and if it seems like a fit, I will show you exactly how we handle that. Does that work?"

Sample discovery opener:

"Before I get into anything on our end — what made you want to take this call?"

This question does two things: it resets the conversation away from pitch mode, and it tells you exactly what angle matters most to them.

Sample bridge into presenting:

"Based on what you just described, the part that seems most relevant is [X]. Can I show you how that works specifically for [their use case]?"

Sample next step close:

"This seems like it could be a fit — here is what I would suggest as a next step: [specific action]. Does [day/time] work to get that on the calendar now?"


Real-Time AI in Sales Calls: What Happens When Preparation Is Not Enough

Preparation covers what you know going in. It does not cover what the prospect says once the call starts.

A prospect who mentions a use case you have not mapped, raises a technical constraint you did not anticipate, or brings up a competitor you are not familiar with — these are the moments that separate reps who can adapt from reps who stall.

Most sales tools address this after the call: transcriptions, summaries, deal health scores. That context is useful for the next call, but it does not help in the moment when the conversation has already moved on.

kernous works during the call. It listens to the live conversation and surfaces relevant prompts, talk tracks, and context in under 200ms — while the exchange is still happening.

For a structured sales call, that means the rep does not have to abandon the framework the moment the conversation shifts. When a prospect raises an unexpected objection, mentions a competitor, or introduces a new use case, the context they need is already there.

The goal is not to replace the rep or replace the structure. It is to help the rep stay present when the conversation pressure-tests the plan.


FAQ

What is the difference between a cold call and a sales call?

A cold call is an unsolicited outreach to a prospect who has not agreed to speak with you. A sales call is a scheduled conversation with someone who has already shown interest or agreed to a meeting. The goals are different: a cold call aims to earn a next step; a sales call aims to move a qualified opportunity forward.

How long should a sales call be?

Most first sales calls run between 20 and 45 minutes. The right length depends on where the prospect is in the buying process. Early-stage discovery calls tend to be shorter; calls involving multiple stakeholders or technical evaluation typically run longer. The rule is not to fill the time — it is to accomplish the five phases. If you have done that in 20 minutes, end the call.

How do I keep a sales call from running over time?

Set the agenda and time commitment at the open, and track phases as you move through the call. If discovery is running long, it usually means you found something important — but signal the time to the prospect: "This is really useful. We have about ten minutes left — can I show you the part that's most relevant to what you just described?" Respecting the agreed time builds trust.

What should I do if the prospect goes off-topic?

Let them go briefly, then bridge back. Going off-topic often surfaces useful context — why they took the meeting, what else is on their mind, what the real pressure is. After a minute, you can redirect: "That's useful context — and it actually ties into what I wanted to ask you about. Can I pick up from [topic]?"

How is AI changing sales calls?

The primary shift is in real-time support. Historically, AI tools for sales have worked after calls — providing transcripts, summaries, and coaching feedback. Real-time AI changes the timing: it surfaces relevant guidance during the live conversation, helping reps respond to unexpected moments, objections, and use cases as they happen rather than analyzing them afterward.