wowprompt

Known bug workaround reply with an update promise

Writes the reply for a customer hit by a bug the team already knows about: an honest acknowledgement, a workaround they can use today and a promise to update them that the team can keep. Use it to answer many tickets about the same fault consistently.

A plain description of the issue, a numbered workaround, a customer reply with an honest update promise, and a follow-up message for when the fix ships
The output this prompt produced, unedited.

The prompt

Fill in these first

  • Customer message: [paste]
  • The known issue in plain words: [what breaks, for whom, since when]
  • Workaround, if any: [steps, or none]
  • Fix status: [being investigated, fix in progress, fix scheduled for a date, no date]
  • How customers will be told about the fix: [ticket update, email, status page, release notes]
  • Anything the customer lost because of the bug: [e.g. a failed payment, lost work, nothing]

Task

Write the reply to this customer and the follow-up message for when the fix is live.

Output format

  1. Reply, 90 to 160 words:
  • confirm the issue and that it is not their fault
  • the workaround as numbered steps, or a plain statement that there is none yet
  • what we will do about anything they lost
  • when and how they will hear from us next
  1. Follow-up message for when the fix ships, under 70 words.
  2. Macro version of the reply with [Name] and [Ticket] placeholders, for the rest of the queue.

Rules

  • Never give a fix date unless one is listed above. "We will update you by [date]" is fine; "it will be fixed by [date]" is not, unless it is confirmed.
  • Do not describe internal causes or name team members.
  • Keep the workaround to steps the customer can safely do; no settings that risk their data.
  • Do not ask the customer to reproduce the bug if it is already confirmed.
known issue replybug workaround supportsoftware bug customer replyproduct issue acknowledgementsupport macrocustomer update

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity