# Request types and common fields

This page provides information about the types of service requests you can open using the Pismo Service Desk.

## Request types

> 📘 Operational Level Agreements
>
> Each request type has an Operational Level Agreement (OLA) that defines the expected resolution time based on the issue's nature and urgency.

The following table describes the different types of requests and their OLAs.

**Note:** Table entries marked **N/A** indicate **Not Applicable**.

<Table align={["left","left","left","left"]}>
  <thead>
    <tr>
      <th>
        Request type
      </th>

      <th>
        Description
      </th>

      <th>
        Operational Level Agreement (OLA)
      </th>

      <th>
        Comments
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Incident
      </td>

      <td>
        A service, system, or application has failed or is not functioning correctly.
      </td>

      <td>
        **Acknowledgement**: 15 minutes.

        **Mitigation**: Up to 4 hours for critical incidents; up to 3 business days for lower-priority incidents.
      </td>

      <td>
        **Impacted**: Number of affected users.

        **Severity**: Severity of the incident (refer to
      </td>
    </tr>

    <tr>
      <td>
        Occurrence/Event
      </td>

      <td>
        Occurrence is the record of a bug, error, or suspected failure that requires IT support, without causing a broad or generalized service outage.\
        It may involve impact to specific functionalities, access channels, or defined groups of users or clients.
      </td>

      <td>
        3 business days
      </td>

      <td />
    </tr>

    <tr>
      <td>
        Sandbox
      </td>

      <td>
        An issue is occurring in a sandbox or testing environment.
      </td>

      <td>
        7 business days
      </td>

      <td />
    </tr>

    <tr>
      <td>
        Question
      </td>

      <td>
        You have a general question or need clarification.
      </td>

      <td>
        7 business days
      </td>

      <td>
        Describe the issue as best you can. This is the most important form field (refer to [Describing an issue](https://developers.pismo.io/pismo-docs/docs/describing-an-issue)).
      </td>
    </tr>

    <tr>
      <td>
        Projects
      </td>

      <td>
        You are suggesting an improvement, a new service, or new feature.
      </td>

      <td>
        Varies according to prioritization and analysis.
      </td>

      <td>
        **Scope**: Project objectives or functional specifications about the improvement/new feature.

        **Priority**: Priority of this project/new feature.
      </td>
    </tr>

    <tr>
      <td>
        Performance Test
      </td>

      <td>
        Refer to [Request a performance test](https://developers.pismo.io/pismo-docs/docs/requesting-a-performance-test).
      </td>

      <td>
        N/A
      </td>

      <td />
    </tr>

    <tr>
      <td>
        Deployment Window
      </td>

      <td>
        You have a request related to the deployment window.
      </td>

      <td>
        N/A
      </td>

      <td />
    </tr>

    <tr>
      <td>
        Settings/Configuration
      </td>

      <td>
        You have a request pertaining to existing programs in production, such as those affecting business rules, changing rates, spending controls, and so on.
      </td>

      <td>
        10 business days
      </td>

      <td>
        Select your configuration category and subcategory.
      </td>
    </tr>
  </tbody>
</Table>

# Common fields

The following fields are common to most service request types:

* **Summary**: Provide a high-level issue description.
* **Description**: Describe the issue with as much detail as possible. This is the most important form field. For more information, refer to [Describing an issue](https://developers.pismo.io/pismo-docs/docs/describing-an-issue).
* **Category** (and sub-category): Select an issue category, such as Credit, Digital Account, and so on. The adjacent column is then populated with a sub-category drop-down menu for you to choose from.
* **Share with**: Choose the company that this request pertains to.
* **API**: Select an affected API.
* **X-CID**: This is a correlation identifier field used internally by Pismo to link related API requests and events.