BoldDesk Custom Fields and Their Applications
Custom fields in BoldDesk offer a flexible way to tailor your support system to meet specific business needs. These are user-defined data fields that can be added to various forms to capture additional, relevant information beyond what system-defined fields provide. You can create custom fields for:
- Tickets Form – to capture issue-specific or brand-specific data
- Agents Form – to track agent-related attributes
- Contacts Form – to store customer-specific details
- Contact Groups Form – to manage group-level information
Custom fields complement System Fields (which are predefined and non-editable) by allowing you to collect and organize data that’s unique to your workflows, products, or customer segments.
Applications of Custom Fields in BoldDesk
- Enhancing Ticket Forms - Add brand-specific or condition-specific fields to capture detailed issue information, ensuring tickets are accurately categorized and routed.
- Streamlining Ticket Management - Align ticket workflows with organizational processes to reduce manual effort, improve consistency, and boost operational efficiency.
- Storing Customer-Specific Data - Use custom fields in contact profiles to retain key customer details, enabling personalized support and better context during interactions.
- Advanced Search and Filtering - Enable precise ticket searches and filtering based on custom field values, making it easier to locate, prioritize, and manage specific cases.
- Dynamic Field Visibility - Show or hide fields based on user input or predefined conditions, creating a cleaner, more intuitive experience for both agents and customers.
- Supporting Automation Workflows - Use custom fields as triggers for automation rules, SLAs, and webhooks to streamline ticket handling, enforce service standards, and ensure timely responses.
Supported Field Types
| Field Type | Purpose |
|---|---|
| Textbox (Single-line) | Captures short text inputs like names, titles, or short descriptions. Max supports 255 characters. |
| Textbox (Multi-line) | Captures long text entries. Max supports 1,500 characters. |
| Checkbox (Yes/No) | Binary choice field. Can be set to Yes/No or Checked/Unchecked. |
| Date | Select a calendar date. |
| DateTime | Select both date and time. |
| Numeric | Accepts whole numbers like age, quantity, or number of users. |
| Decimal | Accepts decimal numbers like pricing, ratings, or percentages. |
| Dropdown (Single-select) | Choose one option from the list. |
| Dropdown (Multi-select) | Choose multiple options from a list. |
| Regex | Validate input using a regular expression. |
| URL | Accepts a valid URL. |
| Lookup | Create a dropdown linked to other entities. |
| ePHI | Captures electronic Protected Health Information (ePHI) designed with features that align with HIPAA compliance requirements, like patient registration number, lab test results, etc. This field is only available when HIPAA compliance is enabled. |
Creating and Managing Custom Fields
To create a custom field:
-
Go to Agent Portal > Admin Module > Fields and Forms > Ticket Fields.
-
Click on Add Ticket Fields.
-
Choose the field type (textbox, dropdown, checkbox, date, regex, etc.).
-
Configure:
- Labels for Agent and Customer Portals
- API Name (for integrations)
- Note Message (tooltip or inline help)
- Visibility and Edit Permissions
- Mandatory Status
- Display Conditions (show/hide based on other field values)
-
Click on Add field to create the custom field.
- Placeholder customization applies exclusively to custom fields in both the customer and agent portals within BoldDesk.
- System fields do not allow placeholder editing for the agent portal label; therefore, their default text remains unchanged. However, placeholders in the customer portal can be modified for both system and custom fields according to your preferences, including adjustments for your specific language.
Learn more on How to Activate, Deactivate and Delete Custom Ticket Fields.
Use Case: Tracking Incident Tickets
BoldDesk uses tickets for all support requests. To track Incidents separately, teams can label tickets using custom field, Type, or a Category with a value such as Incident.
- Make the field visible on the ticket creation form.
- Use Advanced Filters (for example, Custom field = Incident) to create a dedicated Ticket View.
- Use the same field in Reports to monitor incident trends and SLAs.
Result: Incidents are managed as regular tickets but can be easily filtered, viewed, and reported separately—without a separate incident ticket type.
Field Display Conditions
Field display conditions can be used to hide or show a field in a form based on certain specified conditions. When the conditions are met, the field will be displayed; otherwise, the field won’t be displayed in the form. Learn more on how to Dynamically show or hide fields in form using field display conditions.
Field Dependency
Field dependency creates a parent-child relationship (cascading effect) between two fields. With Field Dependency, you can set up a cascading dropdown where a field appears only after a selection is made in another field. Learn more on How to Use Field Dependency for Creating a Cascading Dropdown.
- After a custom field has been created, it is not possible to modify its field type.
- Explore more on
Frequently Asked Questions
-
Can I edit the field type after creating a custom field?
No. Field types are fixed once created. -
Are custom fields available in all forms?
Yes. You can add them to ticket, contact, agent, and contact group forms. -
Is ePHI data secure in BoldDesk?
Yes. ePHI fields are designed for HIPAA compliance and are only available when HIPAA mode is enabled. -
Can I use custom fields in automation workflows?
Absolutely. Custom fields can trigger SLAs, webhooks, and automation rules. -
Can I control the date‑picker behavior in BoldDesk to ensure a selected date cannot be reused in another date field on a related ticket?
BoldDesk currently allows you to create custom date fields and use them in automation workflows, but it does not provide any native feature that prevents a date selected in one field from being reused in another related ticket field. The platform supports creating custom fields—including date fields—and using them in rules or validations, but there is no built‑in mechanism for enforcing cross‑field date uniqueness.
Related Articles
- How to Add a New Custom Field to a Ticket Form in BoldDesk
- How to Activate, Deactivate or Delete a Ticket Custom Field
- How to Add a New Custom Field in a Contact Group Form
- How to Add a New Custom Field in a Contact Form
- How to use agent custom fields in Automation
- How to Manage User Fields in BoldDesk