Two points on this, one a question and the other an implementation suggestion: 1. is there some reason you're not using time-boxed ACW, which sets a hard cap complete with an in app countdown timer in order to limit ACW? This can be varied on a queue by queue basis, which seems to meet your initial requirements reasonably well, but there may be some other factor I'm not aware of that makes this infeasible. 2. This seems like an ideal use case for a client app, which can register for conversation events and be used to fire off in app toast notifications; this seems to more directly address your use case, while also avoiding some of the potential limitations of triggers (particularly the fact that they're not guaranteed to fire in real time and rate limits on workflow invocations). There is good information (and an example toast app) found here: https://developer.genesys.cloud/platform/integrations/client-apps/.
------------------------------
Richard Schott
Product Manager
------------------------------
Original Message:
Sent: 11-19-2024 08:32
From: Adrian Rodriguez
Subject: Alert Rules - Limit - Alternatives
Hi Christoph,
I have a workflow wich is triggered by notification topic (v2.detail.events.conversation.{id}.acw) in this flow i made the logic, to obtain the queue and de wrapup duration.
In this flow i can use a native send notification (email) but i want to use alerts in app, like alert rules and i think that is not posible.
So i tried to make a data action to send message (like chat) to the specific agent, but as far i know, this is not possible, i mean make that data action with these endpoint, because you need to manage the authentication.

Thanks for your time
------------------------------
Adrian Rodriguez
Original Message:
Sent: 11-19-2024 08:07
From: Christoph Domaschke
Subject: Alert Rules - Limit - Alternatives
Hi Adrian,
to make a long story short: You can use Alerts to trigger e-mail-flows. In that flows you can call every API you want via data action. And you can create a logic in that flow to check the parameters you mentioned.
I use an e-mail-flow that distributes alert-emails to users depending on certain circumstances. It works pretty well. Only problem is, that you will have to put every user as an recipient for the forwarding of the alert-email. Depending on the sizes of your teams thats maybe no acceptable.
------------------------------
Christoph Domaschke
Leiter Service Center (Cronbank)
Original Message:
Sent: 11-18-2024 05:25
From: Adrian Rodriguez
Subject: Alert Rules - Limit - Alternatives
Hi,
We have the following scenario.
We have 55 agents and 2 queuees (A and B)
We want to alert our agents when their acw time goes up to XXX it depends the queue, 1,5 min for queue A and 2,5 min for queue B.
With alert rules, we can manage one of the alerts but no both, because genesys has a limit to 100 alert rules per user.
So, we created a trigger and a workflow flow, to make the logic for the queues, in this flow we only can manage send email but no send alert (built in alert)
We tried to create a data action to send a message like chat but no is possible with this way.
Someone can help my with any suggestion?
BR.
#API/Integrations
#ArchitectureandDesign
#Implementation
#Reporting/Analytics
------------------------------
Adrian Rodriguez
------------------------------