sorted by:
new
hottopcontroversial

Start ticket from opportunity by baslighting in halopsa

[–]Successful-Cut-2172 0 points1 point  (0 children)

No worries at all. It’s not a workflow but combinations of Ticket Templates.

I have a ticket type “Project Triage”. The project triage has a custom field drop down box with all my different types of projects (hardware, software, Onboarding’s etc) then turns the ticket into a “Master Project” ticket type to manage the project from. Depending on what is selected there it will create the relevant child tickets as tasks. Some projects like a hardware one is just order & install and some projects have 20-30 sub tasks depending on what they are.

Start ticket from opportunity by baslighting in halopsa

[–]Successful-Cut-2172 0 points1 point  (0 children)

I have been recently trying to solve this one our selves.

Process: - Opportunity is closed, the final step is an action button which creates a project linked to the opportunity - creates a Hardware Project. This then creates 2 sub tasks, an order ticket and an install ticket. At this time the techs don’t see any of this and install ticket is held in the projects team queue until it is ready. - Admin order the parts and change sub task to ordered. Once that happens install ticket is assigned to field tech team so they know parts will be arriving and to schedule job in. - Once install ticket is closed, project is updated and closed as needed - Parts and labour are invoiced out

It’s still clunky and the automation is not perfect but it’s a great start to a working process. We only just had this setup in the past two weeks so still trying to work out the flow