![\"Tickets](\"https:\/\/nirohelp.com\/docs\/wp-content\/uploads\/2026\/09\/Tickets-form-field.webp\")
<\/figure>\n\n\n\nEach field is one row, and each row has these columns:<\/p>\n\n\n\n Two things worth noting:<\/p>\n\n\n\n The other four built-ins can be switched off. Their type cannot change – the badge is telling you a fact, not hiding an input.<\/p>\n\n\n\n Add a row and pick a type: text, number, email, long text or dropdown.<\/p>\n\n\n\n For a dropdown, fill Options<\/strong> with one choice per line, written as The part before the colon is stored; the part after it is what the client sees. Three things to expect from custom fields:<\/p>\n\n\n\nColumn<\/th> What it does<\/th><\/tr><\/thead> Enabled<\/strong><\/td> Unticking it removes the field from the form entirely.<\/td><\/tr> Required<\/strong><\/td> Marks the field required.<\/td><\/tr> Label<\/strong><\/td> What the client sees. Change it freely.<\/td><\/tr> Placeholder<\/strong><\/td> Hint text inside the box.<\/td><\/tr> Type<\/strong><\/td> A badge for built-in fields, because their type is fixed. A dropdown for your own fields.<\/td><\/tr> Options<\/strong><\/td> For dropdown fields only. One choice per line.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n The six built-in fields<\/h2>\n\n\n\n
Field<\/th> Default label<\/th> Type<\/th> Required by default<\/th><\/tr><\/thead> Subject<\/td> Subject<\/td> text<\/td> yes<\/td><\/tr> Description<\/td> Description<\/td> rich text<\/td> yes<\/td><\/tr> Product<\/td> Product<\/td> product picker<\/td> no<\/td><\/tr> Reason<\/td> Topic<\/td> reason picker<\/td> no<\/td><\/tr> Urgency<\/td> Urgency<\/td> urgency picker<\/td> no<\/td><\/tr> Order<\/td> Order<\/td> text<\/td> no<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n \n
Adding your own fields<\/h2>\n\n\n\n
value:Label<\/code>:<\/p>\n\n\n\nrefund:Refund request\nbilling:Billing question\nother:Something else\n<\/code><\/pre>\n\n\n\n\n
The embeddable form is different<\/h2>\n\n\n\n