Dependent fields in Service Support forms

I'd like to have the option of creating dependent fields in Support Forms. This is a "must have" if the support form will bring any value to us. I really hope this function becomes available sooner rather than later Smiley Happy

 

It would also be beneficial with more than to levels of dependencies.

12 Replies
Occasional Contributor

I fully agree on this. The Support form is extremely limited and does not at all meet our requirements. 
I can not really see why we need a dedicated support form at all - the support forms should be designed as the rest of the forms. 

And please also consider making more levels of dependencies - I want my dependencies to have a next level of dependencies. 

New Contributor

I agree this should be added.

 

My use case for this is that we provide support for users trialling the three different software products we sell. Each product has different versions and different categories of problems. It would be good to have a "Select Application" field and then based on the option selected the correct pair of Software Version and Issue Category field would be presented to the user completing the ticket.

Occasional Contributor

When will this be added? It makes no sense that it the ticket properties don't appear in the dependent field selector?

New Contributor

Hi team, 
I totally agree with the comments above; 

for our support channels we definitely needs some funneling and the contact form is 1 of them. 

So looking forward to hear if/when the dependent fields in the support form will be added.

Thanks!

New Contributor

Am I alone in thinking it is ridiculous that this simple functionality doesn't exist?

Spoiler
I am beyond frustrated.
From a code standpoint this is simple; please hotfix it ASAP.

 

Regular Contributor

I really support this idea, have seen may other many other support ticket platforms that do provide this and have worked with them in the past.

New Contributor

Just to add my voice to this conversation.  This functionality has been around for a long time in the other sections of the platform, why not this one? 

Also it is now August 2, 2019 and no response at all from any community professional or manager!

New Contributor

Can we get an estimate on this feature?

New Contributor

I am setting up my companies supprt pipeline, and this functionality is crucial. We have many complicated robotic platforms, and depending on which you select and what issue is selected, there is a need for particular properties to become mandatory before a ticket can be closed. I hope this gets added soon.

Occasional Contributor

we need this very bad. there are many ticketing systems out there and all include this feature in their most basic edition.  

Occasional Contributor

Please, we need this so bad. Smiley LOL Smiley LOL

Occasional Contributor

This is really a must have. We try to make an efficient ticketing system, but right now we have to bend over backwards to make this works using special workflows etc. And still, it is not working as it should, as we cannot make fields required if a previous answer is yes or no. When a field is not required, it does not automatically show up in the required fields to fill out when you move a ticket from status A to status B, so you keep clicking, making mistakes, triggering a special 'check inputs' workflow.

 

Come on guys. Hubspot is great in many things. I love the marketing part, the sales part, but the service part needs attention. And not in the knowledge base section but in the 'general things'. I will not invest time in making a knowledge base section if I am not convinced that this system is doing all the basic stuff just right.