Quick connect scenarios for transferring contacts

Publisher

Amazon Web Services

URL

https://docs.aws.amazon.com/connect/latest/adminguide/how-quick-connects-work.html

Published

unknown

Updated

unknown

Accessed

2026-09-07

HTTP status

200

License

Proprietary. (c) Amazon Web Services Inc. AWS Site Terms. No license notice printed in the fetched body.; no-redistribution; short excerpts and locators only

Claims citing this source

• For all three quick connect types, the contact that the transferring agent was working on hears the Default customer hold flow while the quick connect is in progress unless a different customer hold flow is specified. fact in context
• A phone number quick connect invokes no flow at all; the call is connected directly to the destination, so the outbound caller ID cannot be set and the caller ID configured on the queue is used. fact in context
• Once a transferring agent is connected to the destination agent through an agent or queue quick connect, the Contact Control Panel offers Join to conference all parties, Hold all, holding the destination agent, or End call which leaves the destination agent and the customer connected. fact in context
• Amazon Connect exposes no single warm transfer primitive; a warm transfer is composed from a quick connect that runs a transfer flow plus the agent's subsequent choice of Join, Hold all or End call on the Contact Control Panel. inference in context

Cite this source record

APA

WarmTransfer. (2026, September 7). Quick connect scenarios for transferring contacts. WarmTransfer. https://warmtransfer.net/knowledge/sources/aws-connect-how-quick-connects-work

BibTeX

@misc{warmtransfer-aws-connect-how-quick-connects-work,
  title  = {Quick connect scenarios for transferring contacts},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/aws-connect-how-quick-connects-work},
  note   = {Amazon Web Services, accessed 2026-09-07}
}