---
name: customer-support-script-builder
description: "Writes a ready-to-use support response script for one scenario, in the right tone and channel, with dynamic fields and an escalation path support agents can follow. Use when a support lead needs a reusable agent script for a recurring scenario such as a lost parcel, refund request, or delayed order. Do not use for writing a one-off reply to a single customer or a full support playbook. Related topics: business, customer service, management."
---

# Customer Support Script Builder

Writes a ready-to-use support response script for one scenario, in the right tone and channel, with dynamic fields and an escalation path support agents can follow.

## When to use

Use this skill when a support lead needs a reusable agent script for a recurring scenario such as a lost parcel, refund request, or delayed order. Do not use it for writing a one-off reply to a single customer or a full support playbook.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Define the scenario's outcome the company can offer and any limits on what agents may promise.
3. Write the opening acknowledgement, the resolution, and the close in the shape of the chosen channel.
4. Insert the chosen dynamic fields as clearly marked placeholders in the right places.
5. Add the escalation trigger, owner, and handover details if requested.
6. Reread in the chosen tone and cut anything an agent could not say in one breath.

## Inputs

- **Support scenario** (longer free text)
- **Company name** (free text, e.g. "Company name")
- **Channel** (choose one: Email, Live Chat, Phone Call, Social Media)
- **Agent tone** (choose one: Empathetic and Apologetic, Fast and Efficient, Friendly and Casual, Formal)
- **Dynamic fields to include** (choose any: Customer Name, Order Number, Refund Amount, Tracking Link)
- **Include an escalation path** (choose one: Yes, No)

## Output

A script in the channel's format with marked placeholders and an optional escalation section, followed by two lines of agent guidance.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Customer Support Script

Draft a standard response script for one support scenario that an agent can use immediately.

- Support scenario: {{Support scenario}}
- Company name: {{Company name}}
- Channel: {{Channel}}
- Agent tone: {{Agent tone}}
- Dynamic fields to include: {{Dynamic fields to include}}
- Include an escalation path: {{Include an escalation path}}

Write the script in the shape of the channel: short lines for chat, a subject line and sign-off for email, spoken phrasing and pauses for phone. Open by acknowledging the problem, state what the company will do and by when, and close by confirming the customer is satisfied. Insert the chosen fields as curly-brace style placeholders in plain words, for example the customer name in capital letters, so agents can see what to replace. If an escalation path is requested, say when to escalate, to whom, and what to hand over.

Return the script, then two lines of guidance for the agent on tone and what not to promise.

## Pitfalls

- Promising refunds or timings the company has not authorised agents to give.
- Using a chat-length script for a phone call, where it sounds robotic.
- Leaving the escalation trigger vague so agents escalate too late or too often.
