Skip to main content
Closed for Voting

Ticket Fields and Rules

Related products:Freshdesk
  • February 23, 2012
  • 4 replies
  • 46 views

Hi

I'm currently trialing Freshdesk - and have been looking at it with a view to solving specific areas for our small business.

Critical for us is the ability to set custom tickets based on what our customer actually wants from us.  An example - we have customers who have different systems under agreement with us.  We offer both reactive and preventative maintenance.  The questions we ask to support say "Fire Alarm Maintenance" would be very different from those we ask to support "Burglar Alarm Fault" - in the former case, we'd ask things like "When would you like this done" and "Are any faults apparent on the system" - whereas for the latter, we'd want to collect information such as "What does the message on the keypad say" or "Are there any lights on the display", and other such questions.

All of the questions we normally ask are set on two key fields - Reason for Call and then System Type.  Those two fields set everything about our response.  They set not only the questions we then ask, but also response times, advice given, and more.  It's kind of critical to us that we ask the right questions, so as not to let our customers down - I'm not at all sure I can trust the ticket we're given to do any of that, as it's so inflexible.  

I can't find any way to remove some of the "default" fields either - "Subject" is no good to us, for example, and while I can hide it from customer portal view, I can't clear it from the ticket design window, and it's very cluttered - I have no idea at a glance what will appear on my ticket and what won't.  

Is there any chance that this kind of conditional field functionality will be available soon, even if it were to allow us to present different sub forms based on a couple of initial answers?  


4 replies

  • Contributor
  • February 24, 2012
Hi Bill

Yes, we have plans for Nested Ticket fields, that will allow you to bring in Ticket Fields -->> Sub Fields and based on that Tickets can be created by users. You cannot remove some default fields like Subject/Descriptions etc. We will be bringing the Nested Fields features soon

regards
Vijay

  • Community Debut
  • February 21, 2014

I have a similar requirement to Bill, and Dependent Fields only partially help.


We have customers on different SLAs and want to restrict the type of tickets customer can raise based on their SLA (as in some cases this defines the parts of our platform that they're entitled to use). Associating a condition with a Dependent Field so that values were displayed only if the condition was met would be a great way to achieve this.


It would also be great to be able to use SLA as a condition in Dispatch'r rules, as I'd like to be able to set the priority based on their SLA - for example customers on our most basic SLA would only have their tickets categorised as Medium or Low priority.


I realise I could set the basic SLA up so it's Urgent priority had a response time equal to that of Medium in our higher SLAs (for example), but I'd rather avoid the confusion of having multiple resolution times for "Urgent" tickets by setting the priority appropriately in the first place.


Are there any techniques to achieve this at the moment, or is anything in the roadmap?


Thanks


Greg


  • Community Debut
  • July 3, 2015

Also this will be very useful for us!


aravind.sundararajan
Skilled Expert
Forum|alt.badge.img+12

Hello,


Dynamic forms allows you to display relevant fields in the ticket form based on the user input. You can nest several fields together as a dynamic section and then display it to the user only when he/she chooses a specific value. The dynamic forms can be set based on the default type field or any custom dropdown field.


Cheers!