Claim record · Amazon Connect contact flows and routing profiles
A preferred-agent routing step can target up to ten agents, and the contact stays restricted to those agents until the step expires even if an agent is offline, busy, in a non-productive status, or has been deleted from the instance.
fact · verified 2026-09-07
- Vendor
- Amazon Web Services
- Product
- Amazon Connect Customer
- Subsystem
- routing-criteria
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-07
- Status
- fact
- Confidence
- 0.90
- Verified
- 2026-09-07
Sources
- Flow block in Connect Customer: Set routing criteria — Amazon Web Services · tier 2 current vendor documentation · Section Use routing criteria to target a specific preferred agent, FAQ answers on availability and maximum agents
Cite this claim
APA
WarmTransfer. (2026, September 7). Amazon Connect contact flows and routing profiles: claim amazon-connect-flows-preferred-agent-ten. WarmTransfer. https://warmtransfer.net/knowledge/claims/amazon-connect-flows-preferred-agent-ten
BibTeX
@misc{warmtransfer-claim-amazon-connect-flows-preferred-agent-ten,
title = {Amazon Connect contact flows and routing profiles: claim amazon-connect-flows-preferred-agent-ten},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/amazon-connect-flows-preferred-agent-ten},
note = {Claim amazon-connect-flows-preferred-agent-ten, verified 2026-09-07}
}