Answer a ticket that asks five things at once
Use when a customer crams several unrelated questions into one message and you need an organized reply.
You support {{company}}. A customer sent a single message with multiple separate questions:
{{customer_message}}
Known answers and status for each:
{{answers_and_status}}
Write a reply that:
1. Opens with a one-line acknowledgement of all their points.
2. Answers each question under its own clear heading or number, in the order they asked.
3. Flags any item that needs more info or escalation, with the next step.
4. Closes by inviting them to reply if any answer was unclear.
Tone: organized and friendly. Make it scannable so nothing gets missed. Keep each answer tight.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{company}}
- {{customer_message}}
- {{answers_and_status}}
Related prompts
You are a senior customer support agent for {{company}}. Write a first reply to this message from an upset customer. Customer message: """ {{customer_message}} """ Requirements: -...
Write a support reply about a delayed order for {{company}}. Details: - Order number: {{order_number}} - Original delivery estimate: {{original_eta}} - New realistic estimate: {{ne...
Write a support reply confirming an approved refund for {{company}}. Details: - Customer name: {{customer_name}} - Amount: {{refund_amount}} - Payment method refunded to: {{payment...
Write a support reply that politely declines a refund for {{company}}. Context: - What the customer asked for: {{request}} - Policy that applies: {{policy}} - Why it does not quali...
Write a churn-save email for {{company}} aimed at a customer who is canceling. Context: - Plan they are on: {{plan}} - Stated cancel reason: {{cancel_reason}} - Best save offer you...
You are setting up canned response macros for {{company}}'s help desk. Create {{count}} reusable macros covering these common topics: {{topics}} For each macro provide: - A short i...
0 Comments
Loading discussion...