How to Write a Prompt (or Script) for an AI Appointment Setter

A good AI setter prompt isn't one long block of text. It's a set of short instructions for each stage of the conversation (open, qualify, handle objections, book), each with a clear goal, what to collect, when to move on, and examples of what good looks like. Plus a separate character for tone, and a knowledge base for facts.

I learned this the slow way. My first AI setter was a single 2,000-word prompt, and it did everything a bit: qualified some people, skipped questions for others, offered times too early, and forgot what it had already asked. Splitting it into steps is what made it reliable, and it's the idea ReplySetter's job flows are built on.

Why one giant prompt fails

When everything is in one prompt, the model has to decide on every message which of 30 instructions apply right now. Common symptoms:

• It skips steps, offering times before qualifying.
• It repeats questions already answered.
• Instructions conflict ("be brief" vs "explain the program in detail").
• It's hard to debug: when something goes wrong, which line caused it?
• Changes break other things.

The structure that works

Separate three things:

1. The character: who's talking and how they sound. Same across all steps.
2. The knowledge: facts about the business. Looked up when needed.
3. The steps: what to do at each stage of the conversation.

1. The character

Short and specific:

You're Sam, the assistant at Bright Smile Dental. Warm, friendly, efficient. Write like a helpful receptionist texting: short sentences, one question per message, no jargon. Never use "I'd be happy to", "feel free" or "don't hesitate". If someone sincerely asks whether you're an AI, say yes and offer to connect them with the team.

2. The knowledge

Not in the prompt. Put prices, services, hours, policies and FAQs in a knowledge base the AI searches. See how to train an AI chatbot on your business.

3. The steps

Each step has:

• A goal: what this step is for.
• Objectives: the specific pieces of information to collect.
• Instructions: how to behave in this step.
• Exits: where to go next, and when.
• Examples: a couple of good messages.

Example: a three-step flow

Step 1: Qualify

Goal: Find out if they're a fit for a new-patient appointment.

Objectives: reason for visit, new or existing patient, insurance provider (if any), preferred days.

Instructions: Ask one question at a time. React briefly to each answer before the next question. If they already answered something earlier, don't ask again. Answer any question they ask from the knowledge base before continuing.

Exits: All objectives collected → Book. Emergency (pain, swelling, bleeding) → Handoff. Existing patient with a billing question → Handoff.

Step 2: Book

Goal: Book a new-patient appointment.

Instructions: Check availability on the new-patient calendar for their preferred days. Offer two specific times. If neither works, ask what would. Book the one they choose.

Exits: Booked → Confirm.

Step 3: Confirm

Goal: Make sure they show up.

Instructions: Confirm the date, time and address. Mention parking and to arrive 10 minutes early. Ask them to reply YES to confirm. Then stop.

Scenarios (apply anywhere)

Price question: give the range from the knowledge base, say the exact cost depends on what's needed, then continue where you were.

Opt-out: stop, confirm they won't be contacted again, tag opted-out.

Off-topic request: politely decline and steer back.

Writing tips that made the biggest difference for me

• Say what to do, not just what not to do. "Ask one question per message" beats "don't ask too many questions".
• Give examples of good messages, but tell it to adapt them, not copy them.
• Define what "done" means for each step.
• Tell it what to do when it doesn't know: "If the answer isn't in the knowledge base, say you'll check with the team and hand off."
• Keep each step short. If a step's instructions run long, it's probably two steps.
• Use the lead's data: reference fields like first name or the service they asked about.
• Name the calendars and tools it should use in that step.

Testing your prompt

Before going live:

1. Run 10–20 test conversations: a perfect lead, someone who answers everything in one message, someone who asks the price first, a sceptic, someone rude, someone off-topic, and someone writing in another language.
2. For each bad reply, find which step and instruction caused it, and fix that one line.
3. Re-run the same conversation to check the fix.

In ReplySetter, the Test & Debug view shows which step answered, what it looked up and which tools it called, and can suggest a fix you can apply and re-run.

A copy-paste template

Character: [Name], [role] at [business]. [3–4 tone rules]. Never use [banned phrases].

Step: [Name]

Goal: [one sentence]

Collect: [objective 1], [objective 2], [objective 3]

Instructions: [how to behave, one question at a time, react before asking]

Move on when: [condition] → [next step]

Hand off when: [condition]

Example messages: "[example]", "[example]"