---
title: Getting ready for Triage
excerpt: ''
deprecated: false
hidden: true
metadata:
  title: ''
  description: ''
  robots: index
next:
  description: ''
---
## Getting ready for Triage

In preparation for enabling Triage, one of the first steps is to train a supervised deep learning model. This involves feeding data to a machine learning algorithm to facilitate its learning process and enable it to make reliable predictions. The quality of the data used for training is very important. It is essential to ensure that the model is trained on good data, as training it with low-quality data could negatively affect its performance.

As a starting point, Triage models depend on data that includes specific fields and meets certain requirements, as outlined in the example below. Although there may be minor differences in naming conventions based on the ticketing system utilized, the fundamental requirements remain consistent across systems.

While exceptional cases ***may*** require additional fields, the following set of fields is generally adequate for the majority of models.

> 📘 Triaging between Incident and Request
>
> If you are using a model to triage between Incident and Request, this does not require feeding data, and can leverage Global Moveworks models.

**Desired Output:** A .csv with the following columns - 

* Data Column, e.g. `ticket_id`
* Example, e.g. `INC123456`

<Table>
  <thead>
    <tr>
      <th>
        Data Column
      </th>

      <th>
        Example(s)
      </th>

      <th>
        Description
      </th>

      <th>
        Required?
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Ticket ID
      </td>

      <td>
        ° INC123456\
        ° 12389234
      </td>

      <td>
        Unique identifier of each individual ticket.
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        Ticket type
      </td>

      <td>
        ° Incident\
        ° IT Help
      </td>

      <td>
        The classification or categorization of a ticket
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        Created at
      </td>

      <td>
        ° 12/7/22 15:59
      </td>

      <td>
        Ticket creation time
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        Predicted field
      </td>

      <td>
        ° assignment\_group\
        ° category\
        ° component
      </td>

      <td>
        The field Triage will be predicting
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        Display name
      </td>

      <td>
        ° Help Desk - 1\
        ° SAP Support
      </td>

      <td>
        The displayed name of the predicted field. **This concept of display name vs internal name only applies to ServcieNow customers.**
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        Internal Name (of Display Name)
      </td>

      <td>
        ° er2d29f29249fh93498h
      </td>

      <td>
        A system-generated alphanumeric value that uniquely identifies a particular record, such as an incident, task, or any other entity within the ServiceNow platform.
      </td>

      <td>
        If applicable
      </td>
    </tr>

    <tr>
      <td>
        Short Description
      </td>

      <td>
        ° I need help with my VPN
      </td>

      <td>
        Ticket Short Description
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        Description
      </td>

      <td>
        ° I need help. My VPN doesn’t seem to be working.
      </td>

      <td>
        Ticket Description
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        Contact type / Route
      </td>

      <td>
        ° Bot\
        ° Self-service\
        ° email
      </td>

      <td>
        The channel or method through which a ticket is received or routed within the system. **Triage accepts only digital channels (email, self service, bot, etc).**
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        State
      </td>

      <td>
        ° Closed\
        ° Resolved
      </td>

      <td>
        Indicates the state of progress or resolution of the ticket. **Triage models are exclusively trained using tickets that are no longer open or require resolution.**
      </td>

      <td>
        Yes
      </td>
    </tr>

    <tr>
      <td>
        Reassignment Count
      </td>

      <td>
        ° 0\
        ° 2
      </td>

      <td>
        The number of times a ticket has been reassigned to a different assignee or group.
      </td>

      <td>
        If applicable
      </td>
    </tr>

    <tr>
      <td>
        Initial group
      </td>

      <td>
        ° Help Desk - 1\
        ° SAP Support
      </td>

      <td>
        First assignee group or team that is initially responsible for handling a ticket.
      </td>

      <td>
        If applicable
      </td>
    </tr>

    <tr>
      <td>
        Location
      </td>

      <td>
        ° San Francisco\
        ° EU
      </td>

      <td>
        Geographical location associated with a ticket
      </td>

      <td>
        If applicable
      </td>
    </tr>
  </tbody>
</Table>