• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 26 subscribers
  • Views 594 views
  • Users 0 members are here
Options
Related
This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Is there a way for the client to change Request Type after the ticket is created?

Peter_2022

We are using WHD slightly "off-label" for processing various service requests, not just IT help. There is considerable back-and-forth communication with our clients. Based on the Client's responses we route tickets to different Tech Pools and tickets often go Client-Tech1-Client-Tech2-Client-Tech3 before being closed.  As the subject says, is there a way for the Client to change the Request Sub-Type after the ticket is created? Our current work-around is to have a Custom Field which is a drop down that mimics a list of request sub-types. The Client can change the selection and then a set of Action Rules checks for each value in the Custom Field and updates the Request Type.

While this does work, it is getting somewhat complicated to follow as out business processes grow and expand.  Currently, for each Parent Request Type, I need a CustomField_SubType (but labeled something user friendly) and then an additional set of rules to update the sub-type.

Parents
  • +1

    So you are wanting the Client to drive the re-assignment of Technicians on the Ticket Request?

    This is not normal as the Technicians will normally escalate to a higher level within the Tech Group or reassign to a different Tech Group.

    If you want them to have control then Action Rules are probably the only solution.

Reply
  • +1

    So you are wanting the Client to drive the re-assignment of Technicians on the Ticket Request?

    This is not normal as the Technicians will normally escalate to a higher level within the Tech Group or reassign to a different Tech Group.

    If you want them to have control then Action Rules are probably the only solution.

Children
  • 0 in reply to pabely

    Thank you for the prompt reply and Correct; we rely on the Client to identify the scope of what is required. A single request may have multiple components but we have standardized our processes and are somewhat agnostic with regards to which individual Tech works a particular task, provided it is worked by the correct group, as the groups have different training.
    While every request has a Start and End, the client may require none, some, or all intermediary steps and if they indicate the Request is Started (but not finalized) we can't route it anywhere other than back to the client for more information. (The Client usually knows at the beginning of the process which steps they will need, but when they are ready for them can vary and the intermediary steps are not necessarily dependent on prior steps. In most cases it is not practical nor desirable to wait until the full process can be determined before starting to work the ticket.)

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.