Write a known-issue status update for waiting customers
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.
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. {{INTERNAL_ISSUE_DESCRIPTION}}{{CUSTOMER_FACING_SYMPTOM}}{{FIX_STATUS}}{{RESOLUTION_ESTIMATE}}{{WORKAROUND_DETAILS}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{INTERNAL_ISSUE_DESCRIPTION}}{{CUSTOMER_FACING_SYMPTOM}}{{FIX_STATUS}}{{RESOLUTION_ESTIMATE}}{{WORKAROUND_DETAILS}}. - Paste it into one of the recommended tools below.
- 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.
Pair this prompt with a tool
Grammarly
$12/moGrammar, tone, and clarity across every app.
Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.
Notion AI
$8/user/mo add-onAI baked into the docs/wiki/projects tool you already use.
Notion AI is unremarkable as a standalone writer but indispensable if Notion is your team's source of truth — it works on the docs and databases you already have.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
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.