> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/utilities/tickets/how-do-i-log-a-ticket.md).

# How do I log a ticket?

The Ticketing Centre is your go-to portal for any form of support, help, or enhancements needed beyond what you can find on the Xoro Help portal. When you're in need of further assistance, then you can log a ticket to reach out to our support team.

### Logging a ticket

Logging a ticket is a straightforward process. It involves entering the important details about the issue, such as apt description of the issue, severity, type of assistance needed, and  the module corresponding to the issue.

{% hint style="info" %}
To log a ticket, go to **Menu > Utilities > Tickets > Ticket**
{% endhint %}

**Ticket Details Fields**

<table><thead><tr><th width="184">Field</th><th>Description</th></tr></thead><tbody><tr><td>Subject</td><td>Provide a clear and concise title for the issue.</td></tr><tr><td>Sequence</td><td>Input the sequence or order of the ticket, if applicable.</td></tr><tr><td>Is Onboarding Ticket?</td><td>Select this option if you are logging in an onboarding ticket.</td></tr><tr><td>Is Article Ticket?</td><td>Select this option if you are logging in an article ticket.</td></tr><tr><td>Severity</td><td>Select the severity of the issue. The available options are:<br>- <strong>Low</strong>: Indicates a non-urgent issue. Tickets with low priority are placed lower in the resolution queue.<br>- <strong>Normal</strong>: These tickets are added to the queue and are prioritized above low priority tickets.<br>- <strong>High</strong>: Use this for issues or concerns that need timely attention from our team.<br>- <strong>Urgent</strong>: Reserved for “Mission Critical” errors or issues causing significant operational disruption. These tickets are given top priority.</td></tr><tr><td>Type</td><td>Select the type of the ticket. This depicts the kind of issue you are facing. <strong>Please Note:</strong> Choosing the correct 'Type' is crucial for a swift resolution, as it dictates how your ticket gets routed within our system.</td></tr><tr><td>Module</td><td>Specify the primary module the issue pertains to, such as Data Uploads, Sales, Purchase, Inventory, etc.</td></tr><tr><td>Sub Module</td><td>Indicate a more specific area within the selected module that the issue is related to. For example, within the Sales module, this could be Invoice, Sales Receipt, Estimate, Customer, etc.</td></tr><tr><td>Requester</td><td>Select the requester of the ticket from the available users in the system.</td></tr><tr><td>Watchers</td><td>List the users in the system who should be notified about updates on the ticket. These users won't be the primary contacts but will be kept in the loop.</td></tr><tr><td>Enable email notification for watcher(s)</td><td>If this option is selected, a notification email will be sent to all watcher(s) email for any status change or comment added to the ticket.</td></tr><tr><td>Description</td><td>Provide a detailed explanation of the issue, including any steps to reproduce it, errors encountered, and the expected versus actual results. The more detailed your description, the easier it will be for the support team to diagnose and address the issue. Use the "Drag and drop images/documents below" option to add images or any other documents to the ticket description.</td></tr></tbody></table>

Once all details are filled, click ‘Submit’ on the top right corner of the page to log a ticket into the system.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.xorosoft.com/xoroerp-1/utilities/tickets/how-do-i-log-a-ticket.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.