2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
I had the same issue, as some point AWS reduced the concurrent calls service quota to 1 although the service quota portal said 10. Once I raised a ticket to increase this value the problem was solved.
con risposta 2 anni fa
0
I've not run into this and I would tend to believe it's a configuration issue.
- How is the quick connect configured?
- How's the flow configured?
- How's the Q you're transfering to configure?
david
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
I am pretty familiar with Connect, so i stripped this back to the basics and also created a new instance and used out of the box contact flows. But still had the issue. I also found a similar issue on this forum. you may be right about configuration as we are using SCPs on the account but looking at the configure nothing seems it would impact Connect, but does