Write a bug escalation with repro steps and a clean environment

About this exercise

Write an escalation for engineering with these labeled lines: Summary:, Steps:, Expected:, Actual:, Environment:, Impact:. Steps are exactly 3 numbered lines. For Environment use what the agent reproduced, not what the customer guessed. Leave out customer names and emails. Plain text, under 120 words.

Common mistakes when you ask AI for this

• Using the customer's guess. The customer blamed Chrome 118 and the AI takes that as the environment. Try: Say: "Environment = the agent's repro, not the customer's guess."
• Leaving out the scale. The AI describes one booking and misses 14 customers and the v3.2.1 link. Try: Ask: "Impact: how many customers, how long, which version."
• Free-form story. The AI retells the ticket in paragraphs. Try: Name the six labels and make Steps exactly 3 numbered lines.
• Getting markdown back. AI adds bold and headings by default, which show up as stray symbols where this is pasted. Try: Say "plain text, no bold, no headings, no asterisks".
• Trusting the AI to count words. AI is bad at counting and usually runs long, so a vague "keep it short" lands well over the limit. Try: Cap each part instead of the total, for example "each line under 15 words".

What a strong prompt includes

• Asks for plain text
• Sets a length limit
• Names the labels
• Chooses the repro environment

Practice this now ↑

Related exercises

• Accept a job offer and confirm the exact terms (Writing AI · Job seekers)
• Acknowledge an executive escalation within the hour (Customer Support & Success AI · Executives)
• Age a returns queue in business days and flag the ones over the limit (Customer Support & Success AI · Customer support teams)
• Allocate shared rent by headcount using the right roster (Finance AI · Accountants)
• Announce a feature sunset with the notice period worked out (Customer Support & Success AI · Customer success managers)