How to Write and Use an Appointment Setting Script

What an appointment setting script does and why you need one

An appointment setting script is a written outline of what you or your team will say when calling a prospect to book a meeting. It is not a word-for-word speech to read robotically — it is a framework that keeps the conversation on track, handles the most common objections, and moves toward a yes or no without wasting either person's time.

The script serves three purposes. First, it gives you something to fall back on when you are nervous or when a prospect throws you an unexpected question. Second, it ensures consistency: if five people on your team are making calls, they are all hitting the same key points and may have access to leads the same way. Third, it trains new callers faster because they have a template to follow and adapt rather than starting from nothing.

A working script is short enough to fit on one page, specific enough to your business that it mentions real problems and real solutions, and flexible enough that it sounds like a conversation, not a recording.

Key Takeaways

• A script should open with a specific reason for the call — the prospect's industry, a recent company change, or a problem your service solves — not a generic greeting.
• The core of the script is a two-sentence statement of what you do and why it matters to them, followed immediately by a question that invites them to respond.
• Build in space for the three objections you hear most often: "I'm not interested," "We don't have budget," and "Call me back later."
• The script should end with a specific next step — a date, time, and what the meeting will cover — not a vague "let's stay in touch."
• Test your script with five calls, note which lines get pushback and which ones move people toward yes, then revise before rolling it out to your team.

The opening: why you are calling this person right now

The first 15 seconds determine whether the prospect listens or hangs up. Do not open with your name and company alone. Instead, open with a reason specific to them.

A strong opening names something you know about their situation: "Hi Sarah, I noticed you just hired a VP of Sales at Acme Corp, and we work with companies in that transition to cut their ramp-up time in half." Or it names a problem they likely face: "Hi Marcus, most logistics managers we talk to are drowning in manual data entry between their warehouse system and their accounting software — does that sound like your world?"

The opening should be two sentences maximum. The first sentence is the hook — the reason they should keep listening. The second sentence is permission to continue: "Do you have 30 seconds?" or "Is now an okay time for a quick question?" If they say no, ask when you can call back. If they say yes, move to the next part.

The core pitch: what you do and why it matters

After they give you permission, state what you do in terms of the outcome they get, not the features of your service. Do not say, "We provide cloud-based CRM software with AI-powered lead scoring." Say, "We help sales teams cut the time they spend on admin work by 60 percent, so they can focus on deals instead of data entry."

Follow the outcome with a question that invites them to engage. "Does that sound like something worth exploring?" or "Is that a problem on your radar?" The question should be open enough that they have to think and answer, not a yes-or-no trap that lets them brush you off.

This section should be three to four sentences. If you are still talking after that, you are pitching instead of may have access to.

Handling the most common objections

Write out responses to the three objections you hear most. For most B2B callers, those are: "I'm not interested," "We don't have budget right now," and "Call me back in three months."

For "I'm not interested," do not argue. Instead, ask a clarifying question: "I get that — usually people say that because they either already have a solution in place or they haven't seen the problem yet. Which one is it for you?" This gives them a chance to explain, and you learn whether they are a real no or just a not-yet.

For "We don't have budget," acknowledge it and move the conversation forward: "That's fair. Most of our customers didn't budget for this until they saw how much time it was costing them. Would it make sense to spend 20 minutes next week looking at what that number is for you?" You are not asking them to spend money today — you are asking them to look at data.

For "Call me back later," get specific: "I can do that. When you say later, do you mean next month, next quarter, or next year? And what would need to change between now and then for this to be worth a conversation?" This tells you whether they are genuinely interested or just trying to end the call politely.

The close: moving toward a specific next step

If the prospect is still engaged after your pitch and objection handling, move to the close. The close is not a hard sell — it is a specific proposal for what happens next.

Instead of "Let's set up a call sometime," say: "I have 2 p.m. on Thursday or 10 a.m. on Friday. Which works better for you? And just so you know, we'll spend 20 minutes looking at your current process and where you're losing time." You have given them two options, a specific duration, and a preview of what the meeting covers.

If they say yes, confirm the time, send a calendar invite the same day, and include a one-sentence reminder of what you will discuss. If they say no, ask: "What would make it worth your time to talk?" This gives you information about what they actually care about, and you can use it if you call back later.

Building your first script: structure and examples

A complete script fits on one page and follows this structure:

Section	Length	What it contains
Opening	2 sentences	Reason for the call specific to them
Permission	1 sentence	"Do you have 30 seconds?"
Pitch	3–4 sentences	Outcome + question that invites response
Objection 1	2–3 sentences	Response to "not interested"
Objection 2	2–3 sentences	Response to "no budget"
Objection 3	2–3 sentences	Response to "call me back later"
Close	2–3 sentences	Two specific times + meeting preview

Here is a sample script for a company that sells project management software to mid-market agencies:

Opening: "Hi David, I saw that Acme Agency just won the Coca-Cola account, and we work with agencies ramping up fast to make sure their teams don't drown in project chaos. Do you have 30 seconds?"

Pitch: "Most agencies we talk to are losing 10 to 15 hours a week to status meetings and email chains instead of actual work. We help teams cut that in half by giving them one place to see what's due, who's doing it, and what's blocked. Does that sound like something worth looking at?"

Objection — not interested: "I get that. Usually people say that because they either already use something or they haven't felt the pain yet. Which one is it?"

Objection — no budget: "That's fair. Most of our customers didn't budget for this until they calculated how much those status meetings were costing them. Would it make sense to spend 20 minutes next week running that number for your team?"

Close: "Great. I have 2 p.m. Thursday or 10 a.m. Friday. Which works? We'll spend 20 minutes walking through your current setup and where you're losing the most time."

Adapt this structure to your business by filling in the specific problem you solve, the outcome your customers see, and the objections your team actually hears.

Testing and revising your script

Do not roll out a new script to your whole team without testing it first. Make five calls using the script as written, and take notes on what happens at each step.

Note which lines get pushback. If three out of five prospects push back on your pitch, the pitch is too long or too vague — shorten it and make it more specific to their industry. If most people say yes to the close but then cancel the meeting, your preview of what the meeting covers is not clear enough.

Note which lines move people toward yes. If your opening about a recent company change gets people to listen, keep using that angle. If your question about whether they already have a solution in place gets them talking, use that question in your objection handling.

After five calls, revise the script based on what you learned. Then share the revised version with your team and have them test it with their own five calls. Collect their feedback and revise again. A script that works is one that has been tested and refined, not one that was written in a conference room.

Frequently Asked Questions

Should I memorize the script or read it word for word?

Memorize the structure and the key phrases, but not every word. If you read word for word, you sound like a recording and prospects hang up. If you know the structure, you can adapt the language to fit the conversation while hitting all the important points.

What if the prospect asks a question I didn't plan for?

Answer the question honestly and briefly, then ask a question back to get the conversation moving again. You do not need to have scripted answers for every possible question — you need to know your product well enough to answer most questions in 30 seconds and redirect back to the goal, which is booking a meeting.

How long should the whole call take?

Aim for three to five minutes if they say yes to the meeting, and one to two minutes if they say no. If you are on the phone for more than five minutes, you are having a sales conversation instead of a qualification call. Save the long conversation for the actual meeting.

Should the script be the same for every prospect?

The structure should be the same, but the opening should change based on what you know about each prospect. Spend 30 seconds before the call looking at their LinkedIn, their company website, or recent news about them. Use that information in your opening to show you called them for a reason, not because they were next on a list.

What if my team is resistant to using a script?

Most resistance comes from scripts that sound robotic or that do not match how the caller actually talks. Involve your team in building the script — have them contribute language they actually use, and let them adapt it to their style. A script your team helped build is one they will use.