> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/incidents/dashboard-actions/report-an-incident-by-email-pagerduty.md).
# Report an Incident by Email (PagerDuty)
The following procedure describes about how report an incident by sending an email when you have the PagerDuty account integrated on Sprinto as your incident ticket management option. You can send email defining the incident details in the mail, this will log the incident ticket on the Sprinto Platform.
**Note:** The tickets created via email cannot be tracked on Sprinto.
### **Prerequisites**:
* Logged in on Sprinto’s employee portal.
* Configured PagerDuty account on Sprinto. Refer to
[Configure PagerDuty for Incident Ticket Management](https://sprinto.freshdesk.com/a/solutions/articles/72000602993)
### **Procedure**:
Step 1: Click on **Report Incident**.
Step 2: Click on **Send Email**.
**Note**: This will prompt an email message window.
Step 3: Write the email. Describe the incident in brief, and send it.
**Note**: This mail will create a incident with the details mentioned in the mail and ticket title as email subject.
### **Result**:
This will create the incident ticket on the registered PagerDuty account.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sprinto.com/data-library/incidents/dashboard-actions/report-an-incident-by-email-pagerduty.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
