Hi @HVA
Greetings from the Freshworks community!
Unfortunately, we only support the following customer fields in Freshdesk. We certainly agree that it would be helpful to have dependant and dynamic sections under customer fields.
We already have a feature request in place for this. In general, the requests will be processed based on the number of users who've requested them and based on the priority and current schedule of the feature request queue. Please have a look at our Ideas page, and post your ask here. We will look into this and take this up from our end.
When organizing contact fields, it’s best to divide them into clear sections for easier navigation and usability. Start with basic personal details such as name, phone number, and email address. Next, include a section of roadhouse texas menu for address information, covering street, city, state, and postal code. If relevant, add a professional details section for job title, company, or department.
I don’t think Freshdesk currently supports fully conditional customer fields the way you described. A workaround I’ve seen is to break them into separate groups and use tags or automation rules to show/hide info.
It’s kind of like how streaming apps organize movies and shows by genre and categories - you don’t see everything at once, only what’s relevant. Freshdesk could benefit from a similar layered approach so agents aren’t overwhelmed by too many fields on one screen
Dividing contact fields into sections helps organize information clearly and enhances the user experience. By grouping related fields—such as personal details, communication preferences, and address information of mi portal fone sev nómina—users can navigate forms more easily and complete them faster. This structure also minimizes confusion and reduces errors, as it guides users step by step through each category.
