Hi Peter,

There is a limit to the number of Interaction Widgets allowed on an org. I'm not sure what the limit is off the top of my head, but there is a limit.

Instead of creating an interaction widget per queue, I'd create a single interaction widget for all queues. When the interaction widget loads it will receive the conversation id as a query parameter. Use that conversation id to call GET /api/v2/conversations/{conversationId} then inspect the returned JSON to find the last participant where purpose=ACD and that should give you the queue name. From there your code can then load the appropriate UI for that queue, or redirect to a queue-specific URL. If you implement things this way you won't run into a limit and configuration shouldn't be a nightmare either.

Hi,

Does anyone know how many Interaction Widgets can be added to 1 Genesys Org? I have a unique requirement for a customer that I'm working on where each queue needs their own Widget.. and they have a lot of Queues

I don't see it on the limits page, so I figured I'd check here.

Thanks,
Peter