thinkhard.SI

Prompt repository Customer support & success

Write a call script for a common customer call

You need a short script with branches for calls like renewals, reminders or payment follow-ups.

Registry no.
SUP-018
Collection
Customer support & success
Laid out for
Any chat model
Score
10 out of 10
Blanks to fill
7
Added

Customer support & successAny chat

The prompt

Score 10 of 10, Excellent

Use it when You need a short script with branches for calls like renewals, reminders or payment follow-ups.

  • {{call_type}}
  • {{caller_role}}
  • {{company}}
  • {{call_goal}}
  • {{call_facts}}
  • {{call_rules}}
  • {{common_responses}}
Full prompt and why it works
Prompt
Write a phone script for {{call_type}} calls that our {{caller_role}} make to customers of {{company}}. Different people will use it on many calls, so it must be easy to follow while talking, sound natural rather than read aloud, and cover the turns a call usually takes.

Why we are calling and what a good outcome is: {{call_goal}}

Facts and options the caller can offer (terms, dates, amounts, choices):
"""
{{call_facts}}
"""

Required steps and rules for these calls (identity checks, disclosures, things never to say):
"""
{{call_rules}}
"""

What customers usually say on these calls: {{common_responses}}

Use this structure, with short labeled sections:
1. Opening: greeting, name, company, any identity check the rules require, and the reason for the call in one sentence, all within the first 20 seconds.
2. Main conversation: the key message and one question that moves toward the outcome.
3. Branches: for each common response above, plus "the customer is upset" and "the customer asks something the caller cannot answer", a heading such as "If they say they already paid:" followed by two or three lines to say.
4. Close: a recap of what was agreed, the next step and its date, and a thank-you.
5. Voicemail: under 30 seconds (about 70 words), with no account details beyond what the rules allow.

Keep the whole script to one or two pages. Write lines the way people talk, with contractions and short sentences.

Use only the facts and options above. Do not invent offers, discounts, deadlines or consequences, and never use threats, pressure or false urgency. Follow every required step in the rules, in the order given.

If the call is about money owed, the rules on what callers may say vary by place, so add a note at the top that the script needs checking by whoever owns compliance before anyone uses it. If a common response has no approved answer in the facts, write "Say: I'll check and call you back by [time]" for that branch and flag it at the end as a gap to fill.

Variables

{{call_type}}
The kind of call, for example "renewal reminder", "overdue payment follow-up" or "appointment confirmation".
{{caller_role}}
Who makes the calls, for example "account managers" or "front desk staff".
{{company}}
Your company or organization name.
{{call_goal}}
Why you are calling and what a good outcome is, for example "confirm the renewal or book a review call".
{{call_facts}}
The facts and options callers can offer: terms, dates, amounts and choices.
{{call_rules}}
Identity checks, required disclosures and anything callers must never say. Check these with whoever handles compliance, or write "none".
{{common_responses}}
What customers usually say on these calls, for example "not a good time", "I already paid", "I want to cancel".

Why it works

  • Format. Short branches for the usual replies, including an upset customer and a question the caller cannot answer, let the caller find the next line mid-call.
  • What to avoid. No invented offers, threats or false deadlines, and every required step in your rules is kept, which matters most on payment calls.
  • If unsure. A reply with no approved answer gets an honest call-back line and is flagged as a gap, so callers never improvise a promise.

How to use it

  1. Press Fill in variables and type your details into each blank. What you type stays in this browser.
  2. Copy the filled prompt into the AI tool you already use, such as ChatGPT, Claude or Gemini, or open it in the Grader or the Prompt Tester here.
  3. Before you rely on it, try it on three or four real examples. The Prompt Tester runs them all at once and shows which ones go wrong.