Limitations of Support Triggers for Zendesk Chat Routing
What are the limitations of using Support triggers for chat routing in Zendesk?
Support triggers have limitations when it comes to chat routing in Zendesk because they only activate after a ticket has been created. This means that the chat routing process, which begins before the ticket creation, is already underway, potentially leading to confusion.
While Support triggers can change the group on a chat ticket, the routing process has already started, making Chat triggers a more effective choice for routing in Agent Workspace.
More related questions
Should I use Support triggers or Chat triggers for routing chats in Zendesk Agent Workspace?
For routing chats in Zendesk Agent Workspace, you should use Chat triggers. Chat triggers can set the department for a chat before the visitor reaches out, ensuring the chat is routed to the appropriate group from the moment the ticket is created….
How do Chat triggers work for routing chats in Zendesk?
Chat triggers in Zendesk are designed to set the department for a chat before the visitor even reaches out. This proactive approach ensures that the chat is routed to the correct group as soon as the ticket is created. By using Chat triggers, you…
Can I use the department's API endpoint for chat routing in Zendesk?
Yes, if your chat routing needs are more complex than what Chat triggers can handle, you can use the department's API endpoint along with custom code for routing in Zendesk. This method, like Chat triggers, sets the department on chats before a…
What should I consider when routing live chats in Zendesk Agent Workspace?
When routing live chats in Zendesk Agent Workspace, it's important to use Chat triggers to set the department before the visitor reaches out. This ensures efficient routing from the moment a ticket is created. If your routing needs are more…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
