# Custom Ticket Fields: Setup Guide

***

## Steps to setup custom ticket field

Setting up custom ticket fields is simple and can be done quickly. Here’s a step-by-step guide:

{% stepper %}
{% step %}
**Go to Ticket Field Settings:** Access the settings menu in your CRM and navigate to the "Custom Fields" section.
{% endstep %}

{% step %}
**Create a New Field:** Click on "Add New Field" and choose the type of field (text, drop-down, checkbox, etc.) that suits your needs.
{% endstep %}

{% step %}
**Define Field Attributes:** Enter a clear and descriptive name, provide a field description, and set default values or options if applicable.
{% endstep %}

{% step %}
**Save and Publish:** Save your new custom field and publish it to make it available for use in ticket forms and views.
{% endstep %}
{% endstepper %}

**Refer to the following link for a detailed step by step guide:**

<https://limechat.clueso.io/guide/custom-ticket-fields>

***

## Best Practices

* **Easy-to-Use Fields:** Make fields easy to understand and use to avoid data entry errors.
* **Keep Custom Fields Relevant:** Regularly review and update fields to ensure they remain relevant to current business needs.
* **Train Teams on Field Usage:** Ensure all users understand the importance and correct usage of custom fields.
* **Test Fields Before Deployment:** Ensure the new field works as intended without causing confusion or errors.
* **Communicate Changes to Your Team:** Inform agents and managers about new fields and provide training if necessary.

***


---

# 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://limechatai.gitbook.io/limechat-product-guide/helpdesk/settings/custom-ticket-fields-setup-guide.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.