My First Structured Prompt: Creates a email summarizing tickets

I just applied the five-part framework to a prompt I needed, and here's how I structured it:

You are acting as an IT Technician working with residential customers who are not technical experts.

Please read over my technical notes on how I troubleshot these specific issues, whether it be hardware failure, network issues, or software configuration. Afterwards, please use abstraction to summarize these notes in a way someone who knows nothing about technical terms or concepts can understand.

Do not assume that they understand technical abbreviations, and do not explain all parts of my troubleshooting. The prompt should explain "I troubleshot <Issue> and resolved it via <solution>

Make the email no more than two paragraphs for this closure email. Include a professional and friendly tone.

I added Identity/Task/Constraints/Output because I wanted a very deliberate and structured prompt that I could reuse across multiple tickets

The structured version got me a much friendlier and customer-facing email that also explained technical terms in an understandable manner. The framework made me think through what I actually needed.

1 comment

My First Structured Prompt: Creates a email summarizing tickets