Services for multiple ticket apps.

Currently I have 3 ticketing apps on my platform. The powers at be would like to do a type of 'contact us' service because they didn't want to do the 'questions' area. Is there a way to make a service that would wait until an attribute has been satisfied before it sends it off to one of the three applications? 
Currently because forms are per ticketing application I don't think its possible but I thought I would reach out to see if there is a way or a better solution. 

Thank you

Asked by Justin Goode on Wed 11/8/23 3:29 PM
Sign In to leave feedback or contribute an answer

Answer (1)

This answer has been marked as the accepted answer
Mark Sayers Wed 11/8/23 3:49 PM

A service is tied specifically to a ticketing application, so this wouldn't be possible on the creation action per se, no. You *could* I guess have it execute a workflow where that workflow has a web service step to move the ticket to another app if the person indicates some value on the request.

Mark Sayers
Sr Support Consultant, CS

No feedback
Would I need to make the form in each ticket app to avoid issues? - Justin Goode Wed 11/8/23 4:08 PM
You could make Service offerings per ticket app on that service potentially. That could do this without the need for a workflow to move the ticket out of a primary/main application. - Mark Sayers Wed 11/8/23 4:26 PM
I ended up linking to a KB that then had general phone information and a "contact us" type form for each ticket application. Thanks. - Justin Goode Mon 11/13/23 11:58 AM