Recent searches


No recent searches

Workflow: Route tickets to groups based on support address



Edited Mar 07, 2025


2

20

21 comments

Hi 6805523272602 -

 

If support.fr@ is a support address that is associated with your channel > email, you should have received from support.fr@ as a Trigger condition.  If you've recently added the support address, you may need to refresh or clear your cache.  Keep us posted!

 

Brandon

0


Hey team, 

We have several alias email addresses that we are pulling into ZD and I'm trying to create the trigger that can move them into the correct view, example 

Support.fr@ needs to be visible in the France Ticket view 

When I'm building the trigger I'm unable to select the above email, is there a way around this?

0


Hi Zachary, 
 
Thanks for reaching out! 
 
I just wanted to confirm your last statement "When the ticket is created, is there a way to tie it back to the requester?" are you referring if the created tickets from the routed tickets will still be the requestors email address? If yes, then the answer is Yes, it will still be the requestor's email address. If not, can you please expound on that please? 
 
 
Cheers! 

0


Hello, 

I have this set up for one of our businesses workflow and it's working great! 

 

When the ticket is created, is there a way to tie it back to the requester?

0


Hey Magnus,
 
I've updated the link so you should now have access. Thanks for bringing this to our attention!

0


Step 2 is a broken link

0


Hi Danyal,

You can use triggers to create an automated workflow to push tickets to your agents. You can set up triggers to route tickets based on a number of ticket criteria, including support addresses, ticket forms, or SLAs. You can also use event-based triggers to assign tickets to a specific agent or group of agents. See Setting your routing goals.

It appears that you already raised a ticket mentioning this, kindly check your email for more information.

0


Is there a way that we can do the routing based on requests as the end_user can only create requests.

0


Hi 1263792640530 - 

Thanks for reaching out.  If you stack your actions as

Group > Group B

Assignee > Agent Name

This should resolve your concern.

Hope this helps!

Brandon

0


Hi Support, I have an agent in two different Groups, is there any way to automatically assign the ticket to that agent WITHIN an specific group?

Let's say, Agent Belong to GROUP A and GROUP B, I need any tickets with "something" on the summary to be assigned to "GROUP B/AGENT's NAME".

I haven't seem to be able to do this, I wonder if maybe using an specific order on "group -> GROUP B" and then "assignee -> Agent's name" , or the other way around it would work.

Any input would be appreciated.
Thanks in Advance 


0


Sign in to leave a comment.