Outbound and sales calls

How to Write a Sales Call Script That Sounds Human

Build a sales call script that opens honestly, asks good questions, handles objections and ends with a clear next step, without sounding scripted.

Call editorial team · Published · 5 min read

Most people dislike being read to over the phone, and most salespeople dislike reading. Yet a call without any structure drifts, and the first thirty seconds are wasted on throat-clearing. The solution is a script that serves the agent: a clear purpose, a sequence of questions and prepared answers for the predictable moments.

A salesperson with a headset reading call notes at a desk while on a phone call
Illustrative image

This guide takes you through writing one, step by step. It assumes you already have a reason to be calling and permission to call; if not, start with Outbound Calling Basics and Japan's Telemarketing Sales Rules for Japan.

Define the single goal

Every script needs one goal for the call. A first call rarely closes a sale. More realistic goals are: book a meeting, qualify the need, send information and agree a follow-up, or take an order from a customer who is ready. Write the goal at the top of the page and judge every line by whether it moves toward it.

Different goals need different scripts. A call to book a meeting can be short and light on detail, while a call to a returning customer can skip the introduction and go straight to the reason. Keep a separate outline for each goal rather than one script that tries to do everything.

The structure of a call

A five-part call

  1. OpenSay who you are, who you represent and why you are calling, in two sentences.
  2. Ask permission"Is now a good moment for two minutes?" Respect the answer.
  3. DiscoverAsk a few open questions about their situation before presenting anything.
  4. OfferMatch one benefit to what they said, in plain words.
  5. CloseAgree the next step, repeat it and thank them.

The opening

The opening decides whether the call continues. Be honest and brief. Compare these:

Openings

WeakStronger
Introduction"Hi, how are you today?""Hello, I'm calling from Northside Supplies. I'll take two minutes."
Reason"I wanted to tell you about our services.""You asked us last week about delivery times, and I have an answer."
PermissionRushing straight to the pitch"Is this a good time to talk?"

The examples are hypothetical, but the pattern holds: name yourself, give a reason that matters to them and ask permission. If the call is placed by an automated assistant, say so at the start.

Discovery questions

Discovery is where most scripts are thin. Prepare three to five open questions that reveal the situation and the priority, and that you can ask in any order.

Listen more than you speak, and write down what you hear in their words. Those words become the offer.

Present the offer simply

State one benefit, tie it to what they said, and stop. A list of features invites objections; a single sentence invites a question. Use plain language. Mention a price, a term or a promise only if you are sure it is accurate and current, and never promise what you cannot deliver.

Keep claims true

A sales script is where inflated claims creep in. Avoid superlatives you cannot prove, invented urgency and vague promises. Say what you can do, show where the customer can read the details, and tell them how to cancel or change their mind. Honest scripts also reduce complaints.

Prepare for objections

Objections are information. Collect the ones you hear most and write a short, respectful answer for each, ideally in the form acknowledge, ask, answer.

Common objectionA respectful response outline
"I'm busy."Acknowledge, offer a callback time and keep the promise.
"Not interested."Ask one gentle question about what they use today; if still no, thank them and end.
"Send me information."Agree, ask what they most want to see, and set a follow-up time.
"It's too expensive."Ask what they are comparing with, and explain value only with facts you can support.
"We already have a supplier."Ask what they like and what they would change; do not criticise the other.
"Who gave you my number?"Answer truthfully and offer to remove them from the list.
"Don't call me again."Apologise, confirm and record it; never argue.

The last two matter most. A caller must always be able to leave the conversation, and a request to stop must be recorded and honoured at once. See Managing Opt-Outs and STOP Requests.

Close with a clear next step

End every call with a specific next action, a date and a person: "I'll send the summary this afternoon, and I'll ring you on Thursday at ten." If the person declines, thank them and note why, so the next contact does not repeat the same mistake. Record the outcome and the next step in the customer record at once; see Managing a Phone Sales Pipeline.

Make it sound like a person

Scripts fail when they sound like scripts. Techniques that help:

  1. Write the lines the way you speak, with contractions and short sentences.
  2. Mark pauses and places where you must stop and listen.
  3. Use the person's name once or twice, not constantly.
  4. Replace jargon with the words the customer uses.
  5. Practise out loud with a colleague, and record yourself.

Script review

  • The goal of the call is written at the top.
  • The opening takes under fifteen seconds.
  • There are at least three open discovery questions.
  • Every claim can be backed up.
  • There is a prepared answer for each common objection and a polite exit.
  • A request to stop is handled in one step.
  • The next step is always specific.

Test, listen and refine

Treat the script as a draft. After each week, listen to a sample of calls, mark where people hung up or where agents stumbled, and edit those lines. If you run two versions of an opening, compare results over enough calls to be meaningful, and keep the one that works. Keep a version history so you can return to an earlier wording.

Doing it in Call

Call keeps scripts in one place under Campaigns. You can write a script, ask for a draft based on your words, or draw it as a diagram of steps and branches, and attach it to lines, campaigns and batch calls. A script can include placeholders, such as the contact's name and your company name, which are filled in for each call. Saving updates every place that uses the script, while calls already in progress keep the version they started with.

For products, Call can read material you add, such as a link, file or text, and draft a sales script from it. You replace any gaps marked in the draft with real values, and the draft states prices only if your material does. An outbound script drafted this way opens with your business name, says who is calling, including that it is an AI assistant where relevant, and includes a path for a person who asks not to be called again. See Writing and Using Call Scripts in Call and Branching Call Scripts with the Script Diagram.

Frequently asked questions

How long should a sales call script be?

Short enough to use as a guide. A one-page outline with an opening, discovery questions, the offer, objection answers and a close is usually more useful than a long word-for-word text.

Should agents read the script word for word?

No. Reading aloud sounds unnatural. Agents should know the structure and the key phrases, and adapt the wording to the person.

How do I handle people who say no?

Accept it politely, thank them and note the reason. If they ask not to be called again, record it immediately and do not try to persuade them.

Can an AI write my sales script?

It can produce a useful first draft from your product material, but a person should review it, correct any gaps, check every claim and listen to test calls before it goes live.

How often should I change the script?

When calls show a pattern: the same objection unanswered, the same line causing hang-ups, or a change in your product. Review a sample every week and edit in small steps.

Write and attach a call script, or draw it as branching steps, in Call

In the demo console you can try incoming calls in a simulation.

Related guides