Zendesk uses web cookies to collect information about you when you visit our Site. This information might be about you, your preferences, or your device. At Zendesk, we may use this information for purposes that include ensuring basic functionality of our Sites; remembering user preferences, including your cookie preferences; measuring the effectiveness of our Sites, marketing campaigns, and email communications; and personalizing online content.
Please review the different category headings below to learn more and adjust the cookie settings on your current device. Please note that you will need to ensure that each web browser is adjusted to reflect your preferences if you use different computers or mobile devices.
For more information about how Zendesk uses web cookies, please see our Cookie Notice.
16 comments
Travis Tubbs
This is a major limitation for us current as well. We want certain triggers and automations to only occur when the (Current User) or (Requester) is a light agent. But since light agents are considered "agents" in the conditions made available, this is not possible currently.
Agents and Light Agents need to be separated out and not be considered the same when it comes to triggers and automations.
6
Ahmed Esmat
Strongly need to build triggers around light agents actions.
2
Iliyan Ganev
That would be a very useful feature indeed
1
Tracy Leighton
Strongly agree that light agent restrictions are not clearly aligned with most support cases we have. Allowing them to be in a trigger or automation would help.
2
Marleen de Smet
We need this feature as well. Since light agents forward e-mails to our CS mail adresses we would like the ticket to re-open as soon as an e-mail has been received. Light agents only consult the tickets and do not work in Zendesk. They use their Outlook to respond to an e-mail that was send through a pro-active ticket.
2
[VI] Julia Laars
"Can't: Be used as conditions in business rules: For example, you can't create a trigger that emails the agent assigned to the ticket when a user who is a light agent comments on it." (Understanding and setting light agent permissions – Zendesk help)
This is exactly what we want to do. It doesn't make any sense that this is not possible as you can select any other agents.
We need this please!
3
Leigh KELSEY
Here to add another +1 to this request.
3
Joel Mayer
+1 If a Light Agent has updated a ticket with information that's relevant to a ticket, how then should an Agent know that the information is available on the ticket?
I agree with Tyler Tew that being barred from all triggers and notifications is a step backward from simply being CCd. A better option would be to allow limited ability to facilitate internal team processes at least to the level of what a CCd individual can do.
3
Stacy Robinson
I understand limiting the light agents activity, but I don't think it is unreasonable for admins to be able to create triggers/automations to improve workflow for the light agents. It would make the agent's lives better as well.
1
Lynn Voie
+1 I am in total agreement with what everyone has stated here. This is really needed for our work flow.
1
Danny Grabacki
I am in agreement with the larger group here as well! I can't understand why light agents should be restricted targets in triggers. All I want to do is add a simple notification email when they are "@" mentioned on tickets that pops an alert into their inbox. Going to do some digging and see if I can figure out a workaround, but hopefully Zendesk takes action on this!
1
Shona
Any comment on this from a Zendesk Rep???
There seems to be a bit of engagement on this topic. And I am also interested
2
Tarandeep Gohlar
We thought it would be a good idea for our CSMs to be made light agents in Zendesk (to see and add internal comments to tickets should there be a need).
It was recently found that having them as light agents in Zendesk caused problems with ticket submission and ticket update flows and triggers.
Examples:
A decision therefore has been made to downgrade them back to End users.
Side note based on our experience: If you are a full agent (paid license), the above limitations are not experiences.
1
Francesca Roig
Tarandeep Gohlar
![](/hc/user_images/01HG8GM522G966EHR672ZTNRJC.png)
Both these issues can be worked around with triggers. I haven't done one for the first case, but for the second, here is how I handle it:
1
Tarandeep Gohlar
Thanks for your feedback Francesca Roig
I solved the second case with a similar trigger set up as below.
![](/hc/user_images/01HG8SDCGFB70GGW8FTTVD5CYH.png)
I haven't been able to solved the first case but you've "triggered" me to want to re-visit it again before end of year :)
1
Shawna James
Hey everyone, thank you for taking the time to provide us with this feedback. We apologize for the delay on our end in providing you with a response to your feature request.
I have touched base with the product team that owns this area and wanted to let you know that at this time we are not able to commit to building this feature. We understand this may be frustrating but wanted to ensure we closed this loop to remain transparent.
At this time we are going to close this post for comment and mark it as “not planned”. If you are interested in learning more about this and other features being built please make sure to check out and follow our Community events, What’s New Community Topic, and Zendesk Updates. Again, we apologize for our delay and appreciate you being a valuable Zendesk Community member.
0