# Add ticket

Tickets can be created by end-users/requesters through the web portal or mobile app access, via email, or by a technician on a call with the customer. When tickets are created from email, the message's subject line becomes the ticket summary, the message body becomes the description, and the source field is set to Email.

Tickets may also be created by network monitoring systems configured to send problem reports to the system through one of the standard APIs.  In the Event Management module, you can configure the event types that result in a ticket and the event resolutions that result in the ticket's closure.  Refer to the events section for more details.

<figure><img src="/files/oQFUkfDi0h9J342AZh7g" alt="Infraon&#x27;s ITSM Ticket Creation"><figcaption><p>Infraon's Ticket Creation</p></figcaption></figure>

## Pre-requisites <a href="#toc174553190" id="toc174553190"></a>

To add a ticket, the below must be pre-configured:

* **Requester** - the user requesting the service (the user impacted by the ticket)
* **Priority** - priority of the ticket
* **Impact Service** - Service impacted by the ticket
* **Service Classification**, if required.
* **Assignee** - usually the technician assigned to the ticket. Use the 'Take it' option to self-assign.
* **Followers** are users who are notified of the ticket changes. Use the 'Follow' button to follow them directly.
* **Tags** - ticket groupings used for classification
* **Process visibility** - Enhancement of process visibility for service details that enable or disable the process based on the services. Process visibility in a service that is not required, like a ticket, request, change, problem, or release process, can be disabled. The process visibility feature provides control and flexibility to manage the services leading to a better outcome.

## Instructions to Add a Ticket <a href="#toc174553191" id="toc174553191"></a>

* Go to the ticket page.
* Click on the 'New ticket' button.

If requesters are already added, use the search option to find and add the requester. You can also choose whether to search by Requester or Asset using the dropdown. If no requester exists, use the Add a New Requester option. You can select or add a requester from the following page as well.

<figure><img src="/files/Oeu8MLeCdoDTHfglESGh" alt=""><figcaption></figcaption></figure>

### Suggested KB and Add to Resolution

When creating a ticket, the system displays Suggested Knowledge Base (KB) articles and Interaction Details based on the subject entered, allowing you to quickly find relevant solutions and optionally insert KB content directly into the Resolution field.

#### **Suggested KB Panel**

As you enter the Subject, the right panel displays KB articles related to the issue. Each suggestion contains the article reference, a short description, and the “Pin” action.

<figure><img src="/files/0NyL7K2cEbMoiLzoUtUx" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="194.79998779296875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Element</strong></td><td valign="top"><strong>Description</strong></td></tr><tr><td valign="top"><strong>Suggested KB List</strong></td><td valign="top">Displays KB articles similar to the ticket subject.</td></tr><tr><td valign="top"><strong>KB Summary</strong></td><td valign="top">Shows the article title, preview text, and last updated date.</td></tr><tr><td valign="top"><strong>Pin Icon</strong></td><td valign="top">Allow the technician to add the KB content to the Resolution field.</td></tr></tbody></table>

#### **Attaching KB Content to Resolution**

When the technician clicks Pin, a confirmation message appears asking whether to add the KB content to the resolution.

<table data-header-hidden><thead><tr><th width="228.39996337890625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Action</strong></td><td valign="top"><strong>System Behaviour</strong></td></tr><tr><td valign="top"><strong>The technician clicks Pin</strong></td><td valign="top">A confirmation pop-up appears: “Do you want to attach this KB solution as a Resolution?”</td></tr><tr><td valign="top"><strong>Technician selects Yes</strong></td><td valign="top">KB content is added to the Resolution field, and the Submit as New button changes to Save &#x26; Resolve.</td></tr><tr><td valign="top"><strong>Technician selects No</strong></td><td valign="top">KB content is not added, and the ticket continues normally.</td></tr></tbody></table>

#### **Save & Resolve**

Suppose KB content is added, and the technician chooses Save & Resolve. In that case, the ticket is created with status **Resolved by Event**, the KB article is attached automatically, and the action is logged in the ticket’s activity.

**Reverting Submission**

Technicians can switch back to a regular submission at any time:

* If Submit as New is selected, the ticket is created as New and the KB content is not attached.
* If the confirmation pop-up is cancelled, no KB content is added.

#### **Interaction Panel**

The Interaction panel shows recent ticket updates and communication history to help technicians review context before saving the ticket.

To add a ticket, refer to the details in the below table:

<table data-header-hidden><thead><tr><th width="165"></th><th width="235"></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong></td><td><strong>Action</strong></td><td><strong>Description/Example</strong></td></tr><tr><td>Requester*</td><td>Add a new requester or search for an existing requesting requester.</td><td>Requesters are usually users requesting the service.</td></tr><tr><td>Ticket URL</td><td>Easily tracks the progress of requests.</td><td>Receive a ticket URL in the acknowledgment email request and visit the self-service portal to view the ticket status and any updates.</td></tr><tr><td>Reported by</td><td>Use the icon to expand this section. Add the reporter's name and email address, if applicable.</td><td>Reporters are users reporting the service on behalf of the requester.</td></tr><tr><td>Priority</td><td>Select the priority of the ticket using the dropdown menu.</td><td>Priority can be medium, high, or critical, based on the ticket's impact.</td></tr><tr><td>Impact Service</td><td>Select the impacted service.</td><td>If the requester's name is not selected, the impact service field will be blank. Services can be made available to selected users, to suit the organizational needs.</td></tr><tr><td>Service Classification</td><td>Select the classification within the impacted service</td><td>This is used when a specific service has multiple classifications. For example, if the impacted service is email, the classifications can be connectivity, email configuration, and so on. Leave this field blank if no classifications are defined.</td></tr><tr><td>Assignee</td><td>Select a technician to assign the ticket.</td><td>Use the 'Take it' option to self-assign it.</td></tr><tr><td>Email Notification</td><td>Track the Email</td><td>Email notifies the assignee about the ticket creation, our feature allows you to track whether the assignee has read the email. The pop-up notification will be automatically closed when the assignee reads the email.</td></tr><tr><td>Followers</td><td>Select a user to add them as followers.</td><td>Users who must be notified of the ticket or any changes to the ticket can be added as followers. Use the 'Follow' option to self-follow the ticket.</td></tr><tr><td>Tags</td><td>Select a tag to tag the ticket.</td><td>Ticket tags must be predefined in the 'General Settings -> Tag Management module.</td></tr><tr><td>Subject</td><td>Add a subject line for the ticket.</td><td>The subject line can be a short summary of the ticket. For example, Unable to sync email, Keyboard not working, etc.</td></tr><tr><td>Communication/Internal Note</td><td>Use the dropdown to select if the content is a part of the communication or an internal note for the technician.</td><td>If communication is selected, add the email address in the given textbox.</td></tr><tr><td>Message</td><td>Add the ticket description or the note to your team member in detail.</td><td></td></tr><tr><td>Add Attachment</td><td>Use the action icon to add an attachment to the ticket.</td><td>Attachments can include emails, screenshots, etc.</td></tr><tr><td>Add signature</td><td>Customize the signature</td><td>Customize signature to tickets, requests, concerns, transitions, and releases. Customize the new signature by copying and pasting any desired images or text or simply typing on a given space. Option to create multiple signatures and choose the one that meets the requirements.</td></tr><tr><td>IMAP and SMTP</td><td>Choose the IMAP from the drop-down</td><td>Simplified email communication with IMAP integration. Create a ticket, choose the IMAP option in the communication dropdown, and provide a subject. Once the ticket is created, easily reply to emails directly from the IMAP mailbox associated with the ticket, ensuring seamless and convenient communication.</td></tr></tbody></table>

{% hint style="info" %}
**Additional Notes:**

When the requester's name is added, Infraon displays a list of past interactions. Click on the ticket ID to view ticket details.&#x20;

When a ticket title is added, Infraon displays related Knowledge Base articles. If a related resolution is available, the technician can add it to the ticket Resolution and close the ticket directly.&#x20;

Once all details are added, the user can choose to save it either as

* Submit as New - the ticket is saved as a new ticket (new occurring)
* Submit as Pending - the ticket is saved as pending
* Submit as Resolved - the ticket is saved in 'resolved' status.
  {% endhint %}

{% hint style="info" %}
**Ticket Visibility for Impacted Asset Owners**

Users assigned as Asset Owners can automatically view any ticket where their asset is added as an Impacted Asset, even if they are not the requester, assignee, or an admin.

This visibility is system-controlled and edit access still depends on user roles and permissions.

* Asset owners can view tickets linked to their asset as impacted.
* No configuration is required; visibility is automatic.
* &#x20;Tickets appear in the main application only, not in the Self-Service Portal unless the user is the requester.
* &#x20;Viewing is allowed; editing depends on assigned permissions.

{% endhint %}

<table data-header-hidden><thead><tr><th valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Scenario</strong></td><td valign="top"><strong>System Behaviour</strong></td></tr><tr><td valign="top"><strong>Asset owner views tickets with their asset mapped as impacted</strong></td><td valign="top">The ticket appears in the ticket list and the owner can open and view the ticket details.</td></tr><tr><td valign="top"><strong>Asset owner attempts to edit the ticket</strong></td><td valign="top">Editing is restricted unless the user’s role includes edit permissions.</td></tr><tr><td valign="top"><strong>Asset owner logs into Self-Service Portal (SSP)</strong></td><td valign="top">The ticket is not visible unless the user is the requester. SSP only shows tickets created by the logged-in user.</td></tr></tbody></table>

### Self-Service for Requester <a href="#toc174553193" id="toc174553193"></a>

Once a requester has been given access, they can access the requester's portal, raise tickets, change requests, follow up, and communicate about other tickets/requests. Read more about it at the requester Portal Help.

## **Import from CSV**

* In the **Ticket** module, click the **Add Ticket** option in the top-right corner of the page, then select **Import from CSV.**

![](/files/c59781ba2c8be5c208eabfa4e9b00fe6accc46bf)

The **Import Incident from CSV** sidebar opens. The import process is divided into three stages:

* **Upload → Column Matching → Validation**

**Step 1: Upload CSV**

* In the **Upload** tab, select the required **Workflow.**
* Click on **Download sample CSV**file to get the template based on the selected workflow fields.

![](/files/3282177866cda265f5c6e048f521475715974a0b)

* Fill the CSV file with the required incident details as per the defined format.
* Drag and drop the file or click Browse to upload and select the CSV file.
* Click **Next** to proceed to the next stage.

![](/files/90270897efef93324a34e21a23c066d4986824cd)

{% hint style="warning" %}

* Mandatory fields must not be empty (e.g., Subject, Internal Note, Requester Email).
* Phone number should be numeric with a length of 10–15 digits.
* Supported datetime formats:
  * MM/DD/YY HH:MM
  * MM/DD/YYYY HH:MM
  * MM-DD-YY HH:MM
* Impact Service must include the full path (e.g., IT Support / AWS License / Amazon EC2).
  {% endhint %}

**Step 2: Column Matching**

* In the **Column Matching** tab, map the CSV columns to the corresponding Incident fields.
* Mandatory fields are displayed separately and must be mapped before proceeding.
* Optional fields can be mapped as required.
* Use the **Show Only Mandatory** toggle to filter and view only required fields.
* Ensure all mandatory fields (e.g., Subject, Internal Note, Requester Email) are correctly mapped.
* Click **Import** to proceed to validation.

![](/files/e9f32ef30c0cc475fca25b200372ce99bcdb9baa)

**Step 3: Validation**

* In the **Validation** tab, the system validates the uploaded data based on field rules and formats.
* The records are categorized as:
  * **Valid Records** – Records that meet all validation criteria.
  * **Invalid Records** – Records with missing or incorrect data.
* For invalid records:
  * Click **Download** to export and review the errors.
  * Correct the data and re-upload if required.
* Once validation is complete, click **Proceed with valid records** to create the incidents.

![](/files/5efb306e45aca985e8ce2c3fb174b1e39f5b287f)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.infraon.io/infraon-help/infinity-user-guide/ticket-management/add-ticket.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
