Prompt: Build a Sales Script

Sales scripts get a bad reputation because most of them sound like scripts. Robotic openers, forced transitions, and objection handling that reads like a decision tree. Real conversations do not work that way.

This prompt builds a sales framework that guides the conversation without making your team sound like call center operators. Use it to prompt build sales script ai output that balances structure with flexibility.

The Prompt

Build a sales call script for the following:

PRODUCT/SERVICE: [What you sell]
PRICE RANGE: [Approximate pricing]
CALL TYPE: [Discovery call, demo, closing call]
PROSPECT PROFILE: [Who they are, what they care about]
TOP 3 OBJECTIONS: [What prospects push back on most]
DESIRED OUTCOME: [What counts as a successful call]
CALL DURATION: [Target length]

Structure the script as:

1. OPENING (30 seconds)
   - Pattern interrupt that avoids "how are you today"
   - Set the agenda and get agreement on call structure
   - Frame: "By the end of this call, you will know [outcome]"

2. DISCOVERY (40% of call time)
   - 5-7 questions that uncover their situation, pain, and desired outcome
   - For each question: the question itself, what you are listening for, and what a good answer sounds like
   - Transition phrases between questions so it flows naturally

3. PRESENTATION (30% of call time)
   - How to connect their answers to your solution
   - Key talking points (not a monologue, bullet points to reference)
   - Proof point to drop for each talking point (specific result, case study, or data)

4. OBJECTION HANDLING
   - For each of the top 3 objections:
     * Acknowledge the concern (show you heard them)
     * Reframe (put the concern in context)
     * Evidence (specific proof that addresses it)
     * Bridge question (move back to the conversation)

5. CLOSE (10% of call time)
   - Summary of what they told you and how you solve it
   - Clear next step with specifics (not "let me follow up")
   - If they need time: set a specific follow-up date and commitment

Rules:
- Write it as talking points, not word-for-word scripts
- Include transition phrases between sections
- Discovery questions should feel like genuine curiosity, not an interrogation
- Objection handling should be conversational, not combative
- No manipulative tactics (false urgency, guilt, or pressure)
- Include "if they say [X], pivot to [Y]" branching points

The Right Way to Use a Script

A script is a map, not a GPS route. Your team should know the structure and key points by heart. They should never read from it during a call.

Practice until the talking points feel natural. Role-play the objection handling until the responses are automatic. The script succeeds when it disappears into a natural conversation.

Iterating Based on Calls

After every ten calls, review what worked and what fell flat. Update the script. Add new objections you heard. Replace proof points that did not land. The script is alive. Treat it that way.

Build These Systems

Ready to implement? These step-by-step tutorials show you exactly how:

• How to Automate Cold Call Preparation with AI - Give sales reps AI-generated call prep with prospect insights and talking points.
• How to Build an AI Pricing Objection Handler - Generate tailored responses to pricing objections using deal context.
• How to Create an AI Sales Call Prep System - Give reps AI-generated briefings before every sales call.