Prompt chains for summarizing customer engineering tickets

Here’s a prompt chain that could be helpful for summarizing customer engineering tickets:

1. Ticket Overview
   Prompt: “Please summarize the main issue described in the following customer engineering ticket. Focus on key details such as the nature of the issue, affected systems, and any actions taken so far.”

2. Customer’s Request/Inquiry
   Prompt: “What specific request or inquiry did the customer make in this ticket? Mention any clarifications or resolutions they’re seeking.”

3. Technical Analysis
   Prompt: “Based on the description in the ticket, what possible technical causes can be inferred? Are there any troubleshooting steps that should be considered?”

4. Status Update
   Prompt: “What is the current status of the issue according to the ticket? Has any progress been made or are there any ongoing challenges?”

5. Next Steps/Action Items
   Prompt: “What actions need to be taken next to resolve the issue described in this ticket? Include any follow-ups, tests, or customer communication required.”

6. Impact Assessment
   Prompt: “What is the potential impact of the issue on the customer’s operations? How critical is it to their business?”

7. Ticket Resolution or Closure
   Prompt: “Has this ticket been resolved or closed? If so, summarize the solution provided. If not, outline why it remains open and what is pending.”

This chain can help break down a ticket and provide a structured, concise summary of the information within. Would you like more details or refinements on any of these?