Custom fields are collected only by a create-ticket Action. Tickets from the Chatbase Live Chat Action, tickets a teammate creates in the Helpdesk, and tickets created through the API don’t collect fields.
Anatomy of a field

Field types
Subject and Description are built in. Every ticket has them, and you can’t create a field with either name.
Create a field

1
Open Custom fields
Go to Settings → Custom fields for your AI agent.
2
Add the field
Click New field, fill in the internal and customer-facing labels, and pick the type. Pick carefully, because existing ticket values depend on the type and it stays fixed while the field is in use.
3
Add a collection instruction (optional)
Tell the AI agent how to get the value, for example “Ask for the order number from the confirmation email, not the tracking code.”
4
Add options (Dropdown only)
Type an option and press Enter to add it. Options have their own internal and customer-facing labels, and you can archive an option to stop offering it without losing the tickets that already carry it.
Collect fields when creating tickets

1
Open the create-ticket Action
In your AI agent’s Actions, open a Create ticket Action. The Collect additional details section lists the fields this Action collects.
2
Add fields
Search your fields and add the ones this Action should collect. You can create a new field from here too. Two fields with the same customer-facing label can’t be collected by one Action, since the customer couldn’t tell them apart.
3
Set how each field is collected
Click a field’s Required or Optional badge, or its gear, to open its settings for this Action. The ticket is only created once every required field has a value. Optional fields can stay empty. Fields are added as required.
4
Customize the instruction (optional)
In the same settings, you can give the field its own collection instruction for this Action only, or add one when the field has none. The field and your other Actions keep the original. Changes apply when you save the Action.

Field values on the ticket

- Edit or clear a value inline from the details panel. Values are rendered by type: dates as dates, Dropdown values as their label, images as attachments.
- Follow the history in the ticket timeline. Each edit is recorded as changed Order number from A to B, with who made it.
- Filter the inbox by a field’s value, from the Filter button or in a saved view. Operators follow the field’s type, see Filters.
Tickets without a field form
A ticket only has fields to edit when a create-ticket Action collected them. Tickets created any other way, such as Chatbase Live Chat tickets, show only values already stored on them, read-only, and you can’t add fields to them by hand. When you merge tickets, custom field values stay on the merged ticket. They aren’t copied to the ticket you keep.Where custom fields work
Archiving fields
To retire a field, archive it. Historical ticket data keeps its meaning, because a field that holds values is never deleted or retyped.- Archiving a field stops the AI agent from collecting it. Values already on tickets stay visible.
- If the field is still on any create-ticket Action, you’ll be asked to confirm. It stays listed there, marked Archived and not collected, until you remove it from the Action.
- Labels stay reserved while a field is archived. To bring a field back, restore it instead of creating a new one. A restored field reconnects to all of its historical values.
Delete or change the type of an archived field
Once a field is archived and no ticket holds a value for it, you can open it from Settings → Custom fields to change its type or delete it. A value cleared from a ticket no longer counts.- Changing a Dropdown to another type deletes its options.
- Deleting a field also removes it from every Action that still lists it.
- Deleting can’t be undone.
Limits
Frequently asked questions
Can teammates fill in custom fields by hand on any ticket?
Can teammates fill in custom fields by hand on any ticket?
Only on tickets whose create-ticket Action collects those fields. There, teammates can edit or clear each value inline in the ticket details panel. Tickets created any other way show stored values read-only, and fields can’t be added to them.
Can I use custom fields in triggers?
Can I use custom fields in triggers?
Yes, as conditions. They appear in their own Custom fields group in the condition picker. Triggers can’t set a field value, and fields can’t be inserted as placeholders in trigger emails or Slack messages.
Can I show a custom field as a column in the ticket list?
Can I show a custom field as a column in the ticket list?
No. The ticket list columns are fixed. You can filter on a field in a saved view, or export tickets to get one column per field.
Is there a multi-select field type?
Is there a multi-select field type?
No. The field types are Text, Number, Boolean, Date, Email, Image and Dropdown, and a Dropdown holds one option.
Are custom fields returned by the Helpdesk API?
Are custom fields returned by the Helpdesk API?
Not on the ticket itself: ticket responses don’t include field values. The ticket timeline includes a change event, keyed by field ID, each time a field is edited.