Using Call

Writing and Using Call Scripts in Call: A Practical Guide

How to write a call script that helps rather than constrains, attach it to a phone line, campaign or batch in Call, and learn which wording works.

Call editorial team · Published · 6 min read

"Script" has a bad reputation, and for good reason. Everyone has heard a call where the voice on the other end was clearly reading. But the opposite problem is worse: a team with no shared structure, where every call opens, handles and closes differently, and customers get a different service depending on who answers. A good script solves both. It gives the call a shape and leaves room for the person.

A person at a desk writing a phone script on a notepad beside a headset
Illustrative image

This guide covers how to write a script that helps, how to manage scripts in Call, and how to improve them with real calls. For sales-specific advice, read How to Write a Sales Call Script, and for the branching version see Branching Call Scripts with the Script Diagram.

What a script is for

Think of a script as a map, not a recording. It tells the agent where the call is going, what must be said, what must not be said and how to leave gracefully. The words in between are the agent's own. In Call, an AI agent says each step in its own words, so the script is guidance, not a tape.

What a good script provides

  • An openingWho is calling, from which business, and why, in a few seconds.
  • A purposeWhat the call is trying to achieve, so every step points at it.
  • Required statementsAnything that must be said, such as a disclosure.
  • An exitA clean way to end the call, including when the person asks not to be called again.

Writing a script that helps

Write what the call should achieve at each stage, rather than every word. Short stages are easier to remember and easier to change. A useful pattern has five parts.

A simple script structure

  1. OpenName the business, say who is calling and give the reason in one sentence.
  2. CheckAsk whether it is a good moment. If not, offer another time.
  3. Do the jobAsk the key questions or give the key information, one idea at a time.
  4. Handle repliesPrepare short answers for the usual objections and questions.
  5. CloseConfirm what happens next, thank the person and end the call.

Write the way people speak. Read the script aloud; if you stumble, rewrite it. Cut jargon. Use short sentences. Avoid promises you cannot keep, invented amounts and anything the agent should not say. More on tone in Showing Empathy on Calls Without Scripts Sounding Fake.

Placeholders

Scripts can use placeholders such as the contact's name and your company name, which are filled in for each call. The top of the Scripts page lists the ones available. Use them for facts that change from call to call, and write fixed text for everything else.

Managing scripts in Call

Open Campaigns, then Scripts. Each script card shows its title, its campaign, its text and a pill saying how many places use it. Press New script to write one as text, Built with AI to draft one from your description and knowledge, or New diagram to draw one. Members can read scripts; managers and administrators create, edit and delete them.

  1. Press New script and enter a title.
  2. Choose the campaign it is for, or leave All campaigns.
  3. Write the script, using placeholders where needed.
  4. Press Save script.

Saving a script updates every line, agent and campaign that uses it, and calls already in progress keep the version they started with. That is convenient, but it also means a careless edit spreads fast. If one place needs its own wording, open the pill, press Duplicate for this one only, and edit the copy; later saves of the original no longer change that place.

Attaching a script

A script does nothing until something uses it. After saving a script made with Built with AI, the Use this script section lets you choose a phone line (incoming and agent calls on it) and press Attach to line, or choose a call campaign or batch call and press Use as calling instructions. Attaching does not switch anything on or place any call, so you can set it up in advance and test.

Before it reaches real callers, test it. Place practice calls to yourself and a colleague, ideally with someone who has not seen the script. See Practice Calls: Training Agents Before They Go Live and How to Test a Voice AI Agent Before Launch.

Improving a script with real calls

Once calls happen, Call shows which wording is winning: variants compared by calls, connections, sales and conversion over the last thirty days, and which parts of the script actually get said. A checkpoint reached on few calls shows a part agents skip. Both sections appear once there are calls to compare.

You seePossible meaningTry
A checkpoint rarely reachedAgents skip it, or calls end earlierShorten or move it; ask why calls end
One variant converts betterIts wording or order works betterAdopt it and test a new challenger
Many calls end at the same stepThe step confuses or annoys peopleRewrite it plainly and listen to examples

Change one thing at a time. If you rewrite the whole script, you will not know what made the difference. And remember that conversion is only one measure; a script that wins sales by confusing people will cost you later. Compare against complaints and repeat calls as well.

A hypothetical example

Picture a small dental clinic that wants to remind patients about overdue check-ups. The script opens with the clinic's name and the caller's role, asks whether it is a good moment, mentions that the patient is due a check-up, and offers to take a request for an appointment, which a receptionist then confirms. If the patient says no, the agent thanks them and ends the call. If they ask not to be called again, the agent confirms, records it and ends politely.

Notice what the script leaves out. It does not quote prices, does not promise a particular time slot, and does not try to persuade someone who has said no. Each of those omissions is a choice that protects both the patient and the clinic. A good script is as much about what it avoids as what it says.

Keeping a script alive

Scripts decay. Offers change, staff move on, products are renamed. Put a review date on each script and give it an owner. A quarterly look is usually enough; after any change to your service, check the script the same week. Keep a short log of why each change was made, so the next person understands the reasons.

Scripts and the rules

Scripts for outbound calls should identify the business and the purpose, say clearly when the caller is an AI assistant where that applies, and offer a path for someone who asks not to be called again. Scripts for payment reminders and billing should not invent amounts, and Call does not take payments on the call. Bookings taken by an AI are requests that a person confirms.

Script review checklist

  • The opening names the business, the caller and the reason.
  • Required statements are present and in plain words.
  • There is a clean exit, including for someone who asks not to be called.
  • Nothing promises what the business cannot deliver.
  • It has been read aloud and tested on a practice call.
  • Someone owns it and knows when it was last reviewed.

Frequently asked questions

Who can edit scripts in Call?

Members can read scripts; managers and administrators create, edit and delete them.

What happens when I save a script that many places use?

Saving updates every line, agent and campaign that uses it from their next call. Calls already in progress keep the version they started with.

Can one campaign have its own copy of a script?

Yes. Open the pill on the script card, press Duplicate for this one only next to that place, and edit the copy. Later saves of the original no longer change it.

Does attaching a script start calls?

No. Attaching only tells a line, campaign or batch which script to follow. It does not switch anything on or place any call.

How do I know which wording works?

Under Which wording is winning, Call compares variants by calls, connections, sales and conversion over the last thirty days, once there are calls to compare.

Should the agent read the script word for word?

No. The script is guidance. An AI agent says each step in its own words, and people do best when they keep the structure but speak naturally.

Write and attach a call script in Call

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

Related guides