PlaybookPrompts

Write a known-issue status update for waiting customers

Customer Support known-issuestatus-updatebug-communication

When a bug or outage is known but not yet fixed, support teams need to update waiting customers without overpromising a timeline. This prompt drafts a credible, calm update that holds customers without losing them.

Prompt
You are a support communications writer drafting an update for customers waiting on a known, unresolved issue.

Issue description (internal): {{INTERNAL_ISSUE_DESCRIPTION}}
What customers are experiencing (from their perspective): {{CUSTOMER_FACING_SYMPTOM}}
Current status of the fix: {{FIX_STATUS}} (e.g., root cause identified, fix in testing, awaiting deployment)
Estimated resolution window (if known): {{RESOLUTION_ESTIMATE}}
Workaround available (yes/no and details): {{WORKAROUND_DETAILS}}

Write the customer-facing update using these steps:
1. First sentence: confirm you are aware of the issue and that it matches what the customer is experiencing — use their language, not engineering language.
2. State the current status of the fix honestly. If a timeline is not confirmed, say that directly rather than giving a range that you cannot stand behind.
3. If a workaround exists, describe it in plain numbered steps. If no workaround exists, say so and validate that the inconvenience is real.
4. Tell the customer exactly how they will hear from you next: will you email them when it's resolved, post to a status page, or reply to their ticket?
5. Close with one sentence — no filler phrases.

Edge cases: If the fix status is unknown, omit step 2's status detail and focus on the workaround and next contact point. Never give a resolution estimate that engineering has not confirmed.
Variables to fill in
  • {{INTERNAL_ISSUE_DESCRIPTION}}
  • {{CUSTOMER_FACING_SYMPTOM}}
  • {{FIX_STATUS}}
  • {{RESOLUTION_ESTIMATE}}
  • {{WORKAROUND_DETAILS}}

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: {{INTERNAL_ISSUE_DESCRIPTION}}{{CUSTOMER_FACING_SYMPTOM}}{{FIX_STATUS}}{{RESOLUTION_ESTIMATE}}{{WORKAROUND_DETAILS}}.
  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.