> For the complete documentation index, see [llms.txt](https://kycdocv2.faceki.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kycdocv2.faceki.com/need-help/support/support-ticket.md).

# Support Ticket

## How to Access Tickets

![](/files/F94CVSHbyQY2vSQIw8PY)

Click on 'Tickets' from the menu on the dashboard

## Create New Ticket

![](/files/cfjeJZxr24njG4ZNhcEj)

To create a ticket, click on 'New tickets', then fill up the complaint with a title, category, priority and then your message describing the issue you're facing.

Upon creating a ticket, you can choose one of the following categories: 

* Support - Tickets created for our technical team to verify integration, issues, troubleshoot etc. 
* Billing - Tickets created to our admin and operations stuff to verify billing or subscription information etc. 
* Sales - to contact our sales team, if in need for a quotation, upgrade etc.

## Open Tickets

![](/files/NXVyylxXrzQX9fJ9lRkG)

To find the recently opened or existing tickets, click on 'My tickets', you can click on the title of the ticket to view the ticket details with the replies. You can also view the status of the ticket and the last updated time.


---

# 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://kycdocv2.faceki.com/need-help/support/support-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.