How You Control Availability for Your Applications, Teams, and Associates
You can configure availability at the application, team, and associate level; to control when the Oracle Live Experience widget is displayed to your customers; and how Live Experience routes incoming engagements.
It's likely that your company has core business hours during which one or more associates answer customer engagements. Outside of those business hours, you want to avoid customers encountering unstaffed call queues.
Use team-level availability to control Live Experience engagement routing. Outside the programmed availability, Live Experience won't route calls to unavailable teams.
When working with application and team availability in combination, it's important to avoid unwanted behavior. For example, if an application is available from 8am to 5pm, and a team is available from noon to 5pm, your customers will be able to use the widget from 8am until noon, when no associates are available to answer.
Similarly, if an application is available from noon to 5pm, and a team is available from 8am to 5pm, your customers won't be able to use the widget from 8am until noon, when your associates are available to answer.
When combined with routing rules, you can fine-tune the availability of your associates.
Your associates can also control their availability in the Live Experience Associate Desktop, in case they have to take a break or tend to other business. When an associate is away, Live Experience knows not to route calls to them under any circumstances.