Enabling use of Light Agents in Triggers
Our org has recently started using light agents, and the restrictions really don't make sense.
Light Agents should be eligible for triggers and automations. By this I mean, they should both be targetable by role, and eligible in broader triggers as well.
Per this article, Light agents can not be used as conditions in triggers/automation.
This seems like an unnecessary restriction and is also not accurate. Per my own experience, and confirmed by support, it seems that in reality, light agents are actually ignored by all triggers unless they are cc'd on the ticket.
Stepping up an employee from end-user to light agent should only grant additional features/options, not impose new restrictions.
Use-case example:
We would like to be able to automatically apply certain tags or set specific field values in cases where an email-to-case was submitted by a light agent.
Today, this is not possible.
Additionally, when our Light Agents use an email-to-case support address to submit cases on behalf of their customers, we would like to send them a specific notification, but can not do so.
-
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.
-
Strongly need to build triggers around light agents actions.
-
That would be a very useful feature indeed
-
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.
Please sign in to leave a comment.
4 Comments