How to write a sales call script with Claude

Salespeople often keep the call script in their head and rebuild it from scratch every time. Results vary: on a good day the call flows, on a bad day you forget to ask about budget and timing. Claude turns your working experience into one document that both a new hire and you at the end of a hard day can call from. Here is how to do it in one sitting, without vague talk about discovering needs.

Why bother with a script if you already sell well?

A script is not a text you read like a robot. It is a map of the conversation: where to start, what to ask, how to answer too expensive and let me think about it, how to close. An experienced seller keeps that map in their head, a new employee does not, and call quality across the team jumps around. One document levels the bar: everyone gets the same strong questions and the same answers to common objections.

Claude helps because in a couple of minutes it drafts a first version from your inputs, and then you edit it together. The blank page stops slowing you down.

What should you give Claude so the script is about your product, not a generic one?

A generic script from the internet does not sell, because it does not know your client. Give Claude context and the answer becomes yours:

• what you sell and for how much;
• who you call: role, business size, city;
• what customer problem the product solves;
• three common objections you actually hear;
• how you beat two competitors;
• the goal of the call: sell now, book a meeting, or send a proposal.

The prompt can be simple: You are an experienced head of sales, build a cold call script from these inputs, then the list above, write in plain spoken language, no corporate jargon. The more concrete the inputs, the less you will rewrite.

What does a call script structure look like?

Ask Claude to split the conversation into stages, so it is easy to use during a live call:

1. Greeting and reason for the call: one line on why you are calling.
2. A short interest question so the person does not hang up.
3. Two or three questions to clarify the task.
4. The offer in a single sentence, shaped by the client answers.
5. Answers to common objections: too expensive, no time, we already have a solution.
6. Agreement on the next step with a concrete date.

Ask Claude to write variants of each line, not one rigid text. A real conversation rarely runs straight, and a stock of phrasings helps.

How do you make Claude write human speech, not a robot?

The first draft often comes out smooth but lifeless. The fix is editing out loud. Tell Claude: the line in stage three sounds like a textbook, rewrite it the way a person would say it on the phone, shorter and simpler. Read the text aloud yourself: if you stumble, the client will too. A good trick is to give Claude one of your real winning phrases and ask it to hold that tone across the whole script.

How do you test the script before a real call?

Do not bring a raw script to a client. Ask Claude to play a role: you are a picky client, a small business, called for the first time, I sell by the script, object like in real life. Run a couple of dialogues, mark where the script sags, and fix it. Fifteen minutes of this rehearsal saves dozens of failed calls.

Once the script is ready, save it as a separate file and update it monthly: add objections you actually heard and lines that worked. A script is a living document, not a monument.

Want to practice on your own product right now, start with the free Academy materials: guides and the first lesson about UNIT. Claude itself opens at claude.ai.

AGINE Academy is an independent product, not affiliated with Anthropic. Claude belongs to Anthropic.