Magic Recap Template Library
A collection of AI-powered Magic Recap templates to automate ticket summaries, CSAT requests, escalation reports, incident logs, sentiment analysis, and more. Save time, improve accuracy, and streamline workflows with structured, customizable.
Need help? Check out our Magic Recap Guide or contact support.
1. CSAT Survey Message (Customer Satisfaction Report)
Generate a personalized CSAT survey request.
Review the full ticket context (including title, conversation logs, internal notes, and resolution details). Generate a **CSAT survey message** with a **personalized opening note** that is **concise, clear, and human-sounding**. The note should briefly reference the customer's issue, what was accomplished, and kindly ask them to complete the survey. Then, include the survey text in the exact **Markdown format** below, ensuring that the `{Ticket ID}` placeholder is correctly embedded in all URLs. **Do not deviate from this structure or formatting.** **[Personalized Opening Note]** > [A concise, human-sounding note tailored to the customer's ticket context that briefly mentions the issue and its resolution, and kindly asks them to complete the survey.] Choose from the options below to rate your service experience: [Service magic β¨](https://feedback.smileback.io/{Ticket ID}/1/) [Good service π](https://feedback.smileback.io/{Ticket ID}/0/) ["I'm not mad; just disappointed" π«€](https://feedback.smileback.io/{Ticket ID}/-1/) Thank you! Ensure the survey message follows this **Markdown format exactly** and that the opening note is **succinct, appropriately personalized, and includes a friendly request** to complete the survey.
2. Escalation Report
Summarize an escalated ticket for seamless handoff between teams.
Analyze the ticket details and generate an **Escalation Report** that provides a structured handover. Ensure that it is **concise, clear, and well-organized**. Format: **Issue Summary:** [Briefly describe the original problem] **Troubleshooting Steps:** [Summarize actions already taken and results] **Reason for Escalation:** [Clearly explain why escalation is required] **Next Steps & Owner:** [Define what needs to happen next and who is responsible] The report should be formatted using **bullet points for clarity**, avoid redundant information, and focus on **critical details for the escalation team**.
3. Incident Report
Generate a structured incident report summarizing key details.
Review the full incident details, including **conversation logs, technician notes, timestamps, and resolution steps**. Generate an **Incident Report** with the following structured format: **Incident Title:** [Summarize the issue in 5-10 words] **Date & Time:** [Timestamp of incident detection] **Affected Users/Systems:** [List impacted users, devices, or services] **Description:** [Briefly describe what happened and the symptoms observed] **Root Cause Analysis:** [Summarize identified causes, if known] **Actions Taken:** [List steps taken to mitigate or resolve the issue] **Final Resolution:** [Describe how the issue was resolved or next steps] Ensure the **report is concise, uses bullet points where possible**, and is formatted clearly for review.
4. User Sentiment Analysis
Detect and summarize customer sentiment from conversations.
Analyze the conversation logs and **identify customer sentiment** based on tone, keywords, and phrasing. Provide a **sentiment summary** that includes: - **Overall Sentiment:** [Positive / Neutral / Negative] - **Key Indicators:** [Mention key phrases or words that influenced this sentiment] - **Suggested Follow-Up Action:** [If sentiment is negative, recommend a follow-up approach] Ensure the summary is **concise, to the point, and highlights actionable insights**.
5. Change Management Log
Summarize system changes, approvals, and actions for IT documentation.
Review the change request and generate a **structured Change Management Log**: **Change Request Title:** [Summarize the change in a few words] **Requested Date & By Whom:** [List request date and requester] **Description of Change:** [Summarize what change was requested and why] **Approval Status:** [Approved / Pending / Denied β Include details if needed] **Actions Taken:** [List steps taken, including timestamps and responsible parties] **Outcome & Notes:** [Summarize the result and any key observations] Ensure the log is **structured for easy reference and compliance tracking**.
6. Compliance & Audit Notes
Generate compliance documentation based on ticket history.
Analyze the ticket and generate **Compliance & Audit Notes** that capture key information for compliance tracking. Format: **Compliance Area:** [Security / Data Handling / Access Control / etc.] **Description:** [Summarize the compliance-related issue or event] **Actions Taken:** [List compliance steps taken, including any approvals or documentation updates] **Notes & Next Steps:** [Any additional actions required for compliance tracking] Ensure the summary is **clear, factual, and structured for easy reference**.
7. Knowledge Base Draft (KB Article Generator)
Turn ticket resolutions into structured knowledge base articles.
Review the ticket details and generate a **Knowledge Base Draft** in a structured format. # **[Issue Title]** ### **Issue Summary** [A concise summary of the problem users face] ### **Symptoms** - [List key symptoms users may experience] ### **Resolution Steps** 1. **[Step 1]** β [Detailed explanation] 2. **[Step 2]** β [Detailed explanation] 3. **[Step 3]** β [Detailed explanation] ### **Additional Notes** - [Any additional context, workarounds, or related articles] --- Ensure the **draft is structured clearly** and uses **consistent formatting for easy readability**.
π Ready to Automate Recaps?
With these AI-powered prompts, you can eliminate manual summaries, improve handoffs, and gain instant insights into your IT operations. Customize these templates to fit your workflows and start automating your recaps today!
Need help? Check out our Magic Recap Guide or contact support.
