Independent study lab

This is an independent, free, learning-only student project. It respects every company and vendor. Trademarks belong to their owners. It is not affiliated with or endorsed by Amazon Web Services, Cisco, Genesys, Salesforce, Twilio, or any other company. If you have a concern, the page will be removed or corrected promptly through the contact form. Nothing here is sold. There are no ads. The author is happy to volunteer for any organization.

Contact: https://cyphermonkeylabs.com/#contact

Routing criteria, expiry, and a preferred agent — Learn it in 5 minutes

About five minutes of reading

Set routing criteria does nothing until Transfer to queue, and it does nothing inside an agent queue.

The block puts an ordered list of steps on a contact of any channel. Each step is one or more requirements. You can use the block in an inbound flow, a customer queue flow, a transfer-to-agent flow, or a transfer-to-queue flow. After every timed step expires, Connect offers the contact to the longest available agent who has that queue on a routing profile.

A step can name preferred agents by user ID, up to 10. The contact stays limited to those agents until the timer ends, even if an agent is offline, busy, in a custom status, or deleted. After a Customer Profiles lookup you can point a step at $.Customer.CalculatedAttributes._last_agent_id.

Number on this page: Preferred 10. Maximum agents in one preferred-agent step

Sources and go deeper

sources.json