A single appointment setting script is not enough for a high-performing BDC. Your reps face dozens of distinct scenarios — different lead types, different customer mindsets, different call purposes — and a one-size-fits-all script either does not fit most situations or has to be generic to the point of ineffectiveness.

A script library solves this. It is a curated collection of scripts and script components for every major BDC scenario, maintained and updated as your processes evolve.

What a Script Library Is (and Is Not)

A script library is not a collection of word-for-word speeches that reps recite verbatim. That approach produces robotic-sounding calls that customers immediately identify as scripted.

A script library is a collection of:

• Call structures (what to cover and in what order)
• Key phrases that have proven to be effective
• Objection response frameworks
• Opening and closing options for different scenarios

Reps use the library as a foundation. The exact words adapt to the conversation. The structure and the key moments stay consistent.

The Core Scripts Every BDC Needs

1. First Contact: Fresh Internet Lead (Sales)

Purpose: First outbound call to a new internet lead within five minutes of receipt.

Structure: Identify → Purpose → Quick qualification → Value bridge → Appointment ask

Key elements:

• Reference the specific vehicle they inquired on
• One qualifying question (not three)
• A specific value bridge tied to today's inventory or incentive
• Two specific day options for the appointment ask

Notes for reps: This call needs to be under four minutes. You are not presenting — you are establishing interest and getting the appointment. Everything else happens in person.

---

2. First Contact: Fresh Internet Lead (Used Car)

Purpose: Same as above, but the unique inventory dynamics of used cars require a different approach.

Structure: Same as new car, but value bridge and urgency language are stronger.

Key elements:

• Lead with the specific vehicle and its specific attributes
• Use genuine scarcity language ("this one specifically has had a lot of interest")
• Qualifying question includes mileage tolerance and timeline
• Two specific day options

Notes for reps: Used car customers who do not hear from you within 30 minutes are calling the next dealer. Speed is even more critical than on new car leads.

---

3. Day 3 Follow-Up Call

Purpose: Outbound call to a lead that was not reached on day one or two.

Structure: Identity → New angle → Quick ask

Key elements:

• Do not repeat the same approach as the first call
• Introduce a new piece of information (inventory update, incentive change, a different comparable vehicle)
• Make the appointment ask but be prepared for a quick interaction — these calls are often very short

Notes for reps: The day three follow-up should feel different from the day one call. If you say the same thing, you give the customer the same reason to not respond.

---

4. The Confirmation Call

Purpose: Call the day before a booked appointment to confirm and re-engage.

Structure: Identity → Confirmation with details → Preparation instructions → Any changes?

Key elements:

• Call the afternoon of the day before (not morning of)
• Reference who the customer is meeting with
• Give preparation instructions (bring license and insurance)
• End with a brief excitement note ("I'll have [vehicle] pulled aside for you")

Notes for reps: This is not just a reminder call. It is a final urgency and commitment moment. Do it with energy.

---

5. No-Show Follow-Up Call

Purpose: Call within 30 minutes of a missed appointment.

Structure: Warm check-in → Explain → Reschedule ask

Key elements:

• Lead with concern, not accusation
• Accept any explanation without judgment
• Move directly to reschedule after acknowledgment
• Two specific new appointment options

Notes for reps: The tone on this call is everything. If you sound irritated, the customer will be defensive and will not reschedule.

---

6. The Voicemail

Purpose: Leave a message when the customer does not answer.

Structure: Identity → Specific hook → Phone number × 2

Key elements:

• Under 25 seconds total
• One specific reason to call back (not "just checking in")
• Phone number spoken slowly, repeated twice

Notes for reps: Record yourself leaving a practice voicemail and listen back. Time it. If it is over 25 seconds or you rush the number, do it again.

---

7. Service Appointment Scheduling

Purpose: Inbound call from a customer needing service.

Structure: Acknowledge → Brief qualification → Offer specific options → Confirm and set expectations

Key elements:

• Do not rush to scheduling without acknowledging the issue
• Ask one to two diagnostic questions
• Offer specific appointment times, not open-ended "whenever works"
• Set expectations on time and process before ending the call

---

8. Long-Term Nurture Call (90+ Day Lead)

Purpose: Outbound call to a lead that has been in the pipeline for more than 90 days without converting.

Structure: Low-pressure check-in → New information → Permission ask

Key elements:

• Acknowledge the length of time without making it awkward
• Introduce something new (model update, incentive change, inventory addition)
• Ask if they are still in the market or if their situation has changed
• Accept either answer gracefully

Notes for reps: Do not use the same urgency language you would with a fresh lead. Respect their timeline while keeping the door open.

---

Objection Response Modules

In addition to full call scripts, the library should include standalone objection response frameworks that snap into any call at the appropriate moment.

Each objection module includes:

• The trigger phrase
• The psychology behind the objection (why the customer says it)
• Two to three response options
• The return-to-ask after the response

Objections to include in the library:

• "What's the best price?"
• "I'm just browsing"
• "Can you send me information?"
• "I already spoke with someone there"
• "I'm not ready to come in"
• "I need to think about it"
• "I was quoted less at another dealer"
• "I'm waiting for [model year/color/feature]"

Maintaining the Library

A script library that is not maintained becomes outdated and stops getting used. Assign maintenance responsibility:

Quarterly review: Does any script reflect outdated process, pricing, or inventory approach? Update it.

After major changes: New model year launch, incentive structure change, process update, major CRM or DMS change — any of these may require script updates.

After call recording review reveals a gap: If your team is consistently encountering a scenario that does not have a script, add it.

After competitive changes: If a competitor launches a new program or pricing structure that customers are referencing, add a response module.

Using the Library in Training

The script library is a training tool, not just a reference document.

Week 1 of onboarding: Give new reps the library and walk through every script with rationale for why each element exists.

Weekly drills: Use specific scripts as the basis for morning drills. "Today we're drilling the confirmation call" — pull that script, run the drill.

Call recording review: When reviewing recordings, cross-reference what the rep said against the library. Did they hit the key moments? Where did they deviate and why?

Peer comparison: When a rep consistently outperforms on a specific call type, review their calls against the library to understand whether they are using it effectively or have adapted it in a way that improves it. Good adaptations should be incorporated into the library.

DealSpeak uses your call scripts as the foundation for AI practice scenarios. Reps practice against the specific scripts in your library and get feedback on whether they are hitting the key moments. This closes the gap between having a library and actually using it.

Frequently Asked Questions

How many scripts should be in a library? Start with eight to ten core scripts. A library that grows to 30+ becomes unwieldy and stops getting used. Prioritize the scenarios that account for 80% of your call volume.

Should scripts be updated top-down or can reps contribute? Both. Managers own the official library and approve changes. Reps can propose additions or improvements, especially from frontline insights that managers may not have. High-performing reps' adaptations are often the best source of script improvement.

How do you handle reps who deviate from the scripts? First, understand why. Is the deviation working better? Incorporate it. Is the deviation hurting performance? Coach specifically on the departure and why the library version works.

Should scripts be available on-screen during calls? During training and early tenure, yes. After six to eight weeks, reps should be delivering from memory (internalized framework), not reading. Scripts on-screen too long create reading-dependent reps who sound scripted.

The Library Is a Living Document

Build it well, maintain it actively, and use it in training consistently. A script library that is published once and forgotten does nothing. A script library that is trained against, referenced in coaching, and updated regularly is one of the most valuable assets in your BDC.

See how DealSpeak integrates with your BDC script library to create AI practice scenarios that match your specific scripts and processes.