Source note · Amazon Connect contact flows and routing profiles
Queue priority in a routing profile governs which queue an individual agent is searched against, not which of several available agents receives a contact; routing always attempts the longest-available agent first.
Checked 2026-09-07
- Vendor
- Amazon Web Services
- Product
- Amazon Connect Customer
- Subsystem
- routing-engine
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-07
- Checked
- 2026-09-07
Sources
- Queue priority and delay examples to help you load balance Connect Customer contacts — Amazon Web Services · tier 2 current vendor documentation · Example 6: Different routing profiles, same queues, different priorities
Cite this note
APA
WarmTransfer. (2026, September 7). Amazon Connect contact flows and routing profiles: source note amazon-connect-flows-priority-not-agent-selection. WarmTransfer. https://warmtransfer.net/knowledge/claims/amazon-connect-flows-priority-not-agent-selection
BibTeX
@misc{warmtransfer-claim-amazon-connect-flows-priority-not-agent-selection,
title = {Amazon Connect contact flows and routing profiles: source note amazon-connect-flows-priority-not-agent-selection},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/amazon-connect-flows-priority-not-agent-selection},
note = {Source note amazon-connect-flows-priority-not-agent-selection, checked 2026-09-07}
}