Google PlayApp Store
LumaKol
Отраслевые методики

Call scripts that do not sound scripted (and the templates that follow them)

A script your team hides from is a script nobody reads. How to write one per pipeline stage, keep it to a screen, and pair it with message templates that fill in the lead’s own details.

Автор: Команда LumaKolОпубликовано 8 мин чтения
Handwritten sticky notes pinned to a noticeboard, the nearest reading “Impact Full”

Say the word “script” to a salesperson and watch their face. They picture a page of someone else’s sentences, read aloud badly, while the customer waits for the reading to stop. They are not wrong — that is what most call scripts are, and it is why most of them end up in a folder nobody opens.

But the alternative is not freedom. It is your newest agent inventing your company’s first impression, live, forty times a day. Somewhere between a teleprompter and improvisation there is a thing worth building: a short, stage-specific prompt that carries the handful of sentences that actually matter and leaves the rest to the person.

One script per stage, not one script per company

The most common mistake is writing “the script” — a single document covering everything from first contact to closing.

A first call and a fourth call have almost nothing in common. On the first you are establishing who you are and whether there is anything here at all; on the fourth you are removing a specific obstacle you already know about. A single document that covers both is long, and length is what kills a script: if it does not fit on a phone screen, it will not be read while a phone is ringing.

So write one per pipeline stage. In LumaKol the agent opens the script for the lead’s stage while they call, on the calling screen, so the right one is already in front of them — nothing to search for, nothing to choose. Managers keep them current; agents just read what is there.

This is also why the stage list itself deserves care. Each stage carries a one-line description — “what this stage means” — that agents see when they move a lead into it. When the stage meaning and the stage script are both one screen and both written by the same person, a new agent can understand your whole sales process in about ten minutes.

What belongs in a script — and what does not

A useful script is mostly not sentences to say. It is structure. Four things earn their place:

  • The opening, word for word. This is the one part that should be exact. The first fifteen seconds decide whether the call continues, they are said identically hundreds of times a week, and they are where nervous new agents flounder. Write them out.
  • The two or three questions that must be asked. Not a questionnaire — the specific answers without which the next step cannot be booked. For a property team that might be budget, possession timeline and whether they have seen the location.
  • The objections you already know are coming, with a first sentence for each. Not a rebuttal script; just a way to not be caught silent by the thing you hear nine times a day.
  • The ask. The explicit next step this call is meant to produce — a site visit, a demo, permission to send a brochure. Most calls fail here, not at the opening.

What does not belong: company history, the full feature list, anything the customer can read later, and — above all — paragraphs. Paragraphs get read aloud. Bullets get used as prompts. The difference in how the call sounds is enormous.

Name scripts the way agents look for them

Scripts are found by name, so name them the way someone under time pressure would search: “First call – residential”, “Follow-up – price objection”, “Site visit reminder”. Not “Script v3 final” and not “Standard Outbound Process”.

If you sell more than one thing, put the product in the name before the stage. Agents scan the first two words.

The message template is the other half of the call

Almost every good call ends with “I’ll send you the details.” What happens next is where teams quietly lose leads: the agent means to send it, gets another call, and sends it two days later — or types it from scratch, misspells the project name, and forgets the price.

Message templates fix the mechanical part. An agent picks one on the lead and sends it from their own phone, with the lead’s details already filled in. Because it goes from their number, the customer gets the message from the person they just spoke to, which is the whole point.

Templates take variables, and the list is broader than name-and-company:

GroupWhat you can drop into a message
The personFull name, first name, mobile number, email, designation
Their contextCompany, city, state, country, postal code, address
Where they came fromSource, campaign, external ID
Where they are nowStage, owner, next follow-up
Your sideYour name, organisation name, today’s date
Yours specificallyEvery custom field you have created — budget, project, course, policy number

That last row is the one that makes templates feel personal rather than mass-produced. A message that says “the 3BHK at Riverside you asked about, within your ₹85L budget” is not a template to the person reading it, even though it is one to you.

Email templates additionally carry a subject line, and variables work there too — which matters, because a subject with the person’s first name and your organisation’s name in it is the difference between opened and ignored.

A small thing that decides whether templates get used

Use first name, not full name, in greetings.

Imported sheets are full of entries like “MR RAJESH KUMAR SHARMA” and “kavita p.”. A template that opens “Dear MR RAJESH KUMAR SHARMA” announces itself as machinery in the first four words, and agents stop using it — not because they disagree with templates, but because they are embarrassed to send that.

Every abandoned template is a message typed from scratch, and every message typed from scratch is the one that never gets sent on a busy day.

Scripts rot. Plan for it.

Prices change, a project sells out, a competitor launches something and a new objection appears. A script written in January and never touched is actively harmful by June, because the team learns it is unreliable and stops opening it.

Two habits keep them alive, and both are cheap:

  1. Review the scripts for your two busiest stages once a month, for fifteen minutes, with one agent in the room. Not the best agent — a middling one, who will tell you which lines they skip.
  2. When an objection appears three times in a week, add a line for it the same week. Objections arrive in waves; the value of the answer decays fast.

If you are starting from nothing, the industry pipeline templates are a reasonable first draft: applying one adds stages, call outcomes, custom fields and scripts that do not already exist, without deleting anything of yours. Treat what arrives as a skeleton, not as your voice. The opening line in particular should be rewritten in the words your best agent actually uses.

How to know whether any of this worked

Scripts are usually justified with a feeling. You can do better with two numbers you already have.

The first is the outcome mix on first calls. If a new script is working, the share of first calls ending in a booked next step should rise, and it should rise for the weakest agents first — good agents were already doing this in their own words. If only the top performer improves, the script did nothing; the coaching did.

The second is the gap between your best and worst agent on the same stage. The honest purpose of a script is not to make the best agent better. It is to stop the newest one from being much worse. Narrowing that gap by a third is a real result, and it shows up in the by-agent table long before it shows up in revenue.

Вопросы по теме

Should agents read the script word for word?+

Only the opening. The first fifteen seconds are repeated hundreds of times a week and are where new agents struggle most, so exact wording helps. Everything after that works better as prompts — the questions to ask and the next step to book — said in the agent’s own words.

How long should a call script be?+

Short enough to fit on one phone screen. Agents open the script for the lead’s stage while the call connects; if it needs scrolling, it will not be read. Background and product detail belong in onboarding material, not in the script.

What is the difference between a call script and a message template?+

A script is what an agent says on the call, chosen automatically by the lead’s pipeline stage. A template is what they send afterwards — a WhatsApp, SMS or email sent from their own phone with the lead’s details filled in from the lead record.

Can templates use our own custom fields?+

Yes. Any custom field you create — budget, project, course, policy number — is available as a variable alongside the standard lead fields, so a template can reference the specific thing the customer asked about.

We sell several products. One script or many?+

Many. Write one per stage per product and put the product first in the name, because agents scan the first two words when they are looking for something mid-call.

Начать бесплатный период
#call scripts#sales scripts#message templates#onboarding#pipeline
Команда LumaKol — Написано создателями LumaKol на основе того, что рассказывают клиенты и что мы видим в данных.

Дайте команде CRM, которая фиксирует каждый звонок

Настройте рабочее пространство за минуты и начните фиксировать звонки уже сегодня.

Создать бесплатный аккаунт