Is it possible to create a trigger for the routing functionality in Hubspot based on a specific pipeline and status?
Right now, we can only trigger the routing when a new ticket enters our helpdesk. Ideally, we want to evaluate the ticket manually, and only when the ticket gets moved to a specific pipeline and status, the routing should be triggered based on the rulesets that we created. Is this possible?
Yes, very possible. Your enrollment criteria would be that a Property Value Has Changed (Ticket Status). You can further refine that if needed, but essentially it would enroll after the evaluation and new ticket status is set.
You would then create branches for each of your rulesets. Based on the appropriate ruleset (branch) you would then assign the appropriate owner, or rotate between owners if more appropriate. Check out the screenshot below:
Thanks for the response! I think this could work for us. There is also a routing functionality integrated in the helpdesk, which allows you to route tickets. Would we also be able to trigger this when a tickets get to a specified satus and pipeline?
I mean this functionality: Route tickets in help desk based on agent skills
Hi @lindahouben, thank you for posting in the community ! Right now, we can only route tickets in Help Desk based on user availability or agent skillset: Automatic ticket assignment. I do understand the benefits of being able to route tickets based on ticket pipeline and status directly through Help Desk. Have you considered adding this feature request to our Ideas Forum ? Our Product Team actively monitors this forum to plan for Product Updates and tons of features have been delivered from these request.
Yes! Rather than relying solely on new ticket creation, you can create a ticket-based workflow that enrolls tickets when they move into a specific pipeline and status, and then use actions within that workflow to route the ticket according to your rulesets.
To do this, navigate to Automation > Workflows, create a new workflow of type “Ticket-based,” set the enrollment trigger to fire when Ticket Pipeline is your chosen pipeline AND Ticket Status is the status you want, and then add branching logic or ticket assignment actions (such as “Rotate record to owner” or “Set ticket owner”) based on your existing routing rulesets.
This way, tickets only enter the routing logic after you’ve manually evaluated and moved them to the correct pipeline and status