When a work item is routed to a queue or at least one skill, Omni-Channel can estimate the customer's wait time (in seconds) before an agent becomes available. For instance, if a call is sent to a queue, Omni-Channel can calculate the time the call might spend in the queue before an agent picks it up. The estimated wait time appears for Messaging for In-App and Web sessions and Voice calls, and can be retrieved by the Check Availability for Routing action in an Omni-Channel flow.
To estimate the wait time for the current work item, Omni-Channel uses the actual wait times of up to the last 10 accepted work items in the last 10 minutes. To estimate the wait time when routing work to a skill, during the calculation, we use only recently accepted work items that match the same required skills. The additional skills are ignored.
To calculate the estimated wait time (EWT), Omni-Channel uses a weighted average, where the more recently added work weighs heavier than the older work. Specifically, it uses this formula to calculate EWT.
EWT = (10n_wait_time * 10 + 9n_wait_time * 9 + 8n_wait_time * 8 + … + 2n_wait_time * 2 + 1n_wait_time * 1 ) / (10 + 9 +...+ 2 + 1)
If only 3 work items are accepted, Omni-Channel calculates EWT using this formula.
EWT = (3n_wait_time * 10 + 2n_wait_time * 9 + 1n_wait_time * 8) / (10 + 9 + 8)
Omni-Channel includes only primary work items in these calculations. It excludes interruptible work.
See Also
Salesforce Help: Configure Estimated Wait Times for Queues
Salesforce Help: Show Customers an Estimated Wait Time in the Messaging Window
Salesforce Help: Make Smarter Routing Decisions by Checking Agent Availability
Developer Doc: Using Estimated Wait Time Instead of Queue Position for a Chat Session (Beta)
003817179

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.