Phone support script
Professional structure: role, context, objective, details, steps, format, criteria and self-check. Designed for better results, not guaranteed ones: always review the answer.
Never use real personal data. If you need to, run it through the data cleaner.
## Role Act as a contact centre trainer. ## Context I want a script to handle calls consistently without sounding robotic. ## Objective Create a flexible script in blocks with answers to the most common situations. ## Details (fill in what is in square brackets) - [type of calls: information, complaints, bookings] - [services] - [most frequent questions] - [company rules] ## Step-by-step instructions 1. Write the greeting and how to identify the need. 2. Create blocks per type of query with key questions. 3. Add answers to the five most common objections or situations. 4. Write a close with a summary and next step. ## Output format Script in blocks with suggested phrases and notes for the agent. ## Quality criteria - Phrases sound natural out loud. - It says when to escalate to a manager. - It asks for no more personal data than needed. ## Self-check Before answering, check every quality criterion. If information is missing, ask me instead of making it up, and at the end state what you have assumed.
Objective
Create a flexible script in blocks with answers to the most common situations.
When to use it
This prompt is ideal for building consistency across your support team, ensuring everyone handles enquiries with the same level of professionalism while still retaining their own voice. It works best for structured environments like customer service centres or service-based businesses. However, it is less useful if your team needs to handle highly complex, unique technical troubleshooting where a rigid flow might actually hinder the resolution process. Use this when you need a reliable framework to reduce call handling times.
Worked example: input (fictional data)
Worked example: full response
Variants
Short and snappy
Strip out the conversational filler. Focus purely on bullet points that an agent can scan in under three seconds. Remove the long greeting and focus exclusively on the core information exchange needed to move the call along rapidly. Ensure the agent can read it and act within 30 seconds.
Empathetic tone
Rewrite the script blocks to prioritise empathy and active listening. Ensure the agent acknowledges the caller's frustration before trying to solve the problem. Use softer language for objections and ensure the agent confirms the customer feels heard and understood before moving to the next step of the process.
Technical escalation focus
Refocus the script on identifying when a call has moved beyond general enquiry into technical troubleshooting. Add specific criteria for when the agent must stop and escalate to a manager or a specialist technician. Ensure the transition to the specialist sounds helpful rather than dismissive of the customer's time.
Common mistakes
- Reading the script word for word.
- Not updating it when services change.
- Failing to leave space for the agent to express their own personality. How to avoid it: Include placeholders in your script where agents are encouraged to use their own conversational style.
- Forcing agents to follow the script even when the customer is angry. How to avoid it: Add a rule that permits agents to abandon the script to prioritise active listening during conflicts.
- Using overly formal language that sounds unnatural to your specific customer base. How to avoid it: Review your draft aloud and swap any stiff or corporate jargon for everyday conversational English.
- Neglecting to include a clear 'if this, then that' logic for complex queries. How to avoid it: Map out the decision tree clearly so agents know exactly which block to choose next.
Related guide
- AI in customer service: fast answers, a person available
- AI for hair and beauty salons: social media and bookings
General and assistant-specific tips
Getting the most out of it
- Paste the prompt as is and only replace what is in [brackets].
- If the answer does not fit, do not start over: ask for “shorter”, “more formal” or “as a table”.
- Always review the result before using it: AI can get facts, dates or names wrong.
Before you paste it: quick checklist
- Don’t paste real customer data or full invoices.
- Describe your business in one sentence: trade, type of customer and area.
- Ask for gaps in [brackets] so you can fill in real data yourself.
- Check any tax or legal obligation on the relevant official website.
How to adapt it to your assistant
The template works the same in ChatGPT, Gemini, Copilot or Claude because it only uses plain language. If your assistant supports fixed instructions (custom instructions, Gems or projects), you can store your preferred tone and format there and paste only the variable part. On a free plan, split long requests into two or three shorter messages.