A real script, annotated line by line
A script is not something to read. It is a record of what worked, written down so you do not have to rediscover it every call.
The technique
Every line in a good script does one job, and you should be able to name it: earn attention, earn permission, learn something, present, close, or handle. Lines that do no job are padding and get cut. Once you can name each line’s job you can improvise inside the structure, which is the whole point, because customers do not follow scripts.
How it sounds on the line
1. “I’m calling about the broadband at 14 Marlow Road.” → earns attention, checkable 2. “Your street went full fibre last month.” → earns permission, gives a reason to keep listening 3. “Do you know roughly what you pay?” → discovery, answerable from memory 4. “Most people on that street are on £41 and could be on £28.” → offer, one sentence, one number
Four lines, four jobs. Anything you would add here should replace a line, not extend the script.
The five jobs, and the padding test
Earn attention, earn permission, learn something, present, close, with handling woven through. Every line in the script should be doing exactly one of these, and you should be able to say which. The test for padding is brutal and takes a second: cover the line and ask whether the call changes without it. Marketing copy fails this test almost every time, because its job was done by the page it was written for, the headline, the layout, the photograph, none of which survive being read down a phone line.
Changing a script without losing it
A script is a lab notebook: it records what worked so you do not rediscover it nightly. Change one line at a time and give the change twenty calls before judging it, because any line works twice and any line fails twice. Keep the tally from the objections lesson running while you test, most script problems announce themselves as one objection becoming suddenly common. When a change wins, it is the script now. The offer sentence is versioned per campaign. The structure around it travels.

What goes wrong here
Label every line in your own script with its job
Questions this lesson owns
Should telesales calls use a script?
Yes, but as structure rather than as lines to read. A good script is a record of what worked, every line doing one nameable job: earn attention, earn permission, learn something, present, close. Sellers who can name each line’s job can improvise inside the structure when the customer leaves it, which customers always do. Sellers who memorised a page cannot.
How do you write a telesales script?
Start from the campaign brief: the targeting is your opening’s reason, the offer becomes one sentence with one number, and discovery is two questions the customer can answer from memory. Label every line with its job and cut anything you cannot label. Then treat it as a running experiment, one change at a time, twenty calls per change, keeping what wins.
How long should a telesales script be?
Short enough that every line has a job you can name. Write out what you say, label each line with what it does, reason, permission, question, offer or close, then cut anything you cannot label. Most sellers lose about a third of their script this way and improve, because the cut lines were filling silence rather than moving the call.
Should you read a script word for word?
No, and the customer can hear it when you do. A script fixes the structure and the few lines that have to be exact, usually the offer and anything the campaign requires you to say. Everything between those is yours. Read verbatim and you produce the recited sound that ends calls inside ten seconds.
How often should you change your sales script?
Change one thing at a time and give it a fair run, twenty calls at least, before you judge it. Change several lines at once and you learn nothing about which one mattered. The exception is a line failing on every single call, which you cut immediately rather than test.