PlaybookPrompts

Rewrite an auto-reply for a high-volume support event

Customer Support auto-replyhigh-volumecustomer-communication

Generic auto-replies during outages or product launches frustrate customers who know something unusual is happening. This prompt writes an auto-reply that acknowledges the event and sets real expectations.

Prompt
You are a support communications writer. Draft an auto-reply for a period of unusually high ticket volume caused by: {{VOLUME_CAUSE}} (e.g., product launch, known bug, marketing campaign, service disruption).

Expected wait time before a human responds: {{EXPECTED_WAIT_TIME}}
Self-service resources available: {{SELF_SERVICE_LINKS_OR_STEPS}}
Topics this event does NOT affect (to narrow scope for customers): {{OUT_OF_SCOPE_TOPICS}}

Write the auto-reply using these steps:
1. First line: acknowledge that the customer's message arrived and that wait times are longer than usual right now — say why in one plain sentence.
2. Give the specific expected wait time. Do not use vague language like 'as soon as possible'.
3. If the customer's issue might be resolved by a self-service step, list 1 to 3 options with links or brief instructions.
4. Tell the customer what not to do (e.g., do not send a follow-up ticket, as it will delay their place in queue).
5. Close with a single sentence confirming a human will follow up — no sign-off cliches.

Keep the total message under 120 words. Write at a 7th-grade reading level.

Edge cases: If the cause of high volume is a security incident, do not mention specifics in the auto-reply — use neutral language and link to a status page instead.
Variables to fill in
  • {{VOLUME_CAUSE}}
  • {{EXPECTED_WAIT_TIME}}
  • {{SELF_SERVICE_LINKS_OR_STEPS}}
  • {{OUT_OF_SCOPE_TOPICS}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{VOLUME_CAUSE}}{{EXPECTED_WAIT_TIME}}{{SELF_SERVICE_LINKS_OR_STEPS}}{{OUT_OF_SCOPE_TOPICS}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.