--- title: "Incident Report Generation" slug: "incident-report-generation" updated: 2026-03-20T08:32:03Z published: 2026-03-20T08:32:03Z canonical: "help.symphonysummitai.com/incident-report-generation" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Incident Report Generation **What if incidents reports came to you—before you even opened a dashboard? With conversational reporting.** IT Analysts can simply ask for incident data and receive instant, ready-to-use reports sorted by the latest activity. Generate real-time incident reports through chat—just ask, and get accurate, sorted ticket insights instantly. Enables IT Analyst Agents to instantly generate incident reports through a conversational chatbot interface. The system aggregates incident data and uses AI to detect reporting intent from analyst chat messages. When a request includes simple parameters (e.g., incidents by stauts), the chatbot automatically generates a structured, list report with accurate ticket data, sorted by the most recent incidents. ****Use Case**** It’s Monday morning. An IT Analyst is preparing for a weekly ops review and needs a quick snapshot of recent incidents. Instead of navigating through multiple dashboards, applying filters, and exporting reports, they simply type: “Show me incidents by status” Within seconds, the chatbot understands the request. No clicks. No filters. No delays. A clean, structured report appears—listing all relevant tickets, accurately filtered and sorted by the latest incidents. What used to take minutes now happens in moments. The analyst walks into the meeting with real-time insights, ready to act—not just report. ### View Incident Reports The analyst enters a query in the chatbot, where AI detects the reporting intent and extracts parameters. The system then fetches aggregated incident data and generates a structured report, displaying tickets sorted by the latest created date. To view the incidents reports based on the provided intent, perform the following steps: 1. Log in to the Application as an Analyst. 2. Prompt the analyst agent with query such as “show me a list on incidents by status”. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-LBYY341L.png?sv=2026-02-06&spr=https&st=2026-11-10T23%3A57%3A06Z&se=2026-11-11T00%3A57%3A06Z&sr=c&sp=r&sig=BlLwowhh5vyscE3szO2u9jrmmJIkRw7eVpnd0EkObws%3D) Figure: Incidents by Status - Prompt 3. Agent provides the list of incidents by status in the following chatbot. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-P2XAXP6I.png?sv=2026-02-06&spr=https&st=2026-11-10T23%3A57%3A06Z&se=2026-11-11T00%3A57%3A06Z&sr=c&sp=r&sig=BlLwowhh5vyscE3szO2u9jrmmJIkRw7eVpnd0EkObws%3D) Figure: List of incidents updated last 7 days The following incidents reports are supported via AIW. ****Supported Incidents Reports**** 1. Response SLA by Analyst 2. Response SLA by Workgroup 3. Response SLA by Category 4. Response SLA by Priority 5. Response SLA by Location 6. Response SLA by Classification 7. Resolution SLA by Analyst 8. Resolution SLA by Workgroup 9. Resolution SLA by Category 10. Resolution SLA by Priority 11. Resolution SLA by Location 12. Resolution SLA by Classification 13. Open Incident Aging by Analyst 14. Open Incident Aging by Workgroup 15. Open Incident Aging by Category 16. Open Incident Aging by Classification 17. Open Incident Aging by Priority 18. Open Incident Aging by Location 19. Resolved Incident Aging by Analyst 20. Resolved Incident Aging by Workgroup 21. Resolved Incident Aging by Category 22. Resolved Incident Aging by Classification 23. Resolved Incident Aging by Priority 24. Resolved Incident Aging by Location 25. Incident Status by Analyst 26. Incident Status by Workgroup 27. Incident Status by Category 28. Incident Status by Classification 29. Incident Status by Priority 30. Average SLA time by Analyst 31. Average SLA time by Workgroup 32. Average SLA time by Category 33. Average SLA time by Priority 34. Average SLA time by Location 35. Average SLA time by Classification 36. Average Clock time by Analyst 37. Average Clock time by Workgroup 38. Average Clock time by Category 39. Average Clock time by Priority 40. Average Clock time by Location 41. Average Clock time by Classification 42. Incidents by Medium 43. MTTR for Incidents by Analyst 44. MTTR for Incidents by Workgroup 45. Incident Volume Trend Report by Classification 46. Major Incidents Report 47. Incident by Priority 48. Incident by Status 49. Top 10 categories 50. Incident Logged vs Resolved Few samples are shown below: ****Resolved Incident by Priority**** It displays the incidents resolved by Priority. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Resolved indicent by priority.png?sv=2026-02-06&spr=https&st=2026-11-10T23%3A57%3A06Z&se=2026-11-11T00%3A57%3A06Z&sr=c&sp=r&sig=BlLwowhh5vyscE3szO2u9jrmmJIkRw7eVpnd0EkObws%3D) Figure: Resolved Incidents by Priority ****Incident Status by Priority**** It displays the incidents status by priority. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Incident_Status_by_Priority.png?sv=2026-02-06&spr=https&st=2026-11-10T23%3A57%3A06Z&se=2026-11-11T00%3A57%3A06Z&sr=c&sp=r&sig=BlLwowhh5vyscE3szO2u9jrmmJIkRw7eVpnd0EkObws%3D) Figure: Incident Status by Priority ****SLA by Classification**** It displays incidents with resolution SLA by Classification. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/SLA_by_Classification.png?sv=2026-02-06&spr=https&st=2026-11-10T23%3A57%3A06Z&se=2026-11-11T00%3A57%3A06Z&sr=c&sp=r&sig=BlLwowhh5vyscE3szO2u9jrmmJIkRw7eVpnd0EkObws%3D) Figure: Resolution SLA by Classification **Combination of two parameters such as **Resolved Incident Aging by Priority** and **Resolved Incident Aging by Priority**** It displays the incidents with two filter criteria such as **Resolved Incident Aging by Priority** and **Resolved Incident Aging by Priority** ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Combination1.png?sv=2026-02-06&spr=https&st=2026-11-10T23%3A57%3A06Z&se=2026-11-11T00%3A57%3A06Z&sr=c&sp=r&sig=BlLwowhh5vyscE3szO2u9jrmmJIkRw7eVpnd0EkObws%3D) Figure: Combination Parameters ## Error Handling Currently, the feature supports the Incident module only. For queries related to other modules (e.g., service requests), the chatbot responds with an appropriate message to inform the analyst. In cases where the query or summarization fails, the bot notifies the analyst with a relevant fallback message. **User prompt**: Display the Service Requests updated in last 7 days. **Agent**: Currently, I can generate reports only for Incident Management. Please try requesting an incident-related report. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-4T710JE2.png?sv=2026-02-06&spr=https&st=2026-11-10T23%3A57%3A06Z&se=2026-11-11T00%3A57%3A06Z&sr=c&sp=r&sig=BlLwowhh5vyscE3szO2u9jrmmJIkRw7eVpnd0EkObws%3D) Figure: No Service Requests