![]() ![]() If you click Reset to Default, it removes all your custom settings and goes back to the default Post Processing.By default, the agent's status changes to Busy when a call is transferred to the agent unless this option is disabled by the tenant administrator inside the Phone script IVR. Note: The agent's idle timer is reset at the end of a non-busy Direct Agent Routing (DAR) call. These changes are immediate and do not require agents to log out and log back in. Select the transitions for which you want the timer to reset. Log in to 8x8 Configuration Manager, go to Home > Agent’s Idle Timer tab.To enable the supplementary settings for agent's idle timer: An agent with a higher skill level takes precedence over any lower-skill-level agent with a more recent status transition that has reset their timer. Agent skill level is a default behavior.Calls that are excluded from the reset, such as manual dials and agent-to-agent calls, remain excluded. This additional configuration does not change the interactions that reset in the default behavior, or inbound and outbound that are system-generated.An example is when the agent returns from On Break to Available or from Login to On Break each morning. This additional configuration does not change the underlying default behavior, it simply adds an overlay and when selected they additionally update the timer setting when an agent changes status.For example, in addition to the default reset, you can configure the idle timer to reset when agents change their status from On Break to Available. To supplement the default behavior, we have now introduced a tenant-wide setting which allows resetting the idle timer when agents transition from one status to another. Agent-initiated interactions do not reset the idle timer. This reset persists until the same scenario is repeated. The agent’s idle timer is reset every time they end post processing of a system-delivered interaction. ![]() When multiple agents with the same queue and skill level assignments are idle, the system routes the call to the agent who has been idle the longest. By default, an agent is considered idle from the time he ends post processing of a system-delivered interaction and becomes available. Multiple timers can be simulated with variables which record the time at the beginning of the session.In 8x8 Contact Center, idle time refers to the length of time agents have been idle and is measured for each agent by the agent's idle timer. Wait (.1) seconds //wait a small amount of time Repeat until > or > //since the button has been held longĬhange by (1) //add points faster When this sprite clicked //when the button is clickedĬhange by (1) //first incrementation Reacting to the length a button is held down by changing a variable faster:.Checking if an amount of time is acceptable for advancing to another stage of the project.When I receive //the variable timer is showing Showing how long a Scratcher is taking in a project (a variable can also be used for this, but it is not as accurate).Tracking time duration in One Sprite One Script Projects instead of using the Wait () Seconds block - in One Sprite One Script projects, in order to keep it Single Frame (scroll to see the whole script).This value can be made more precise by making a script that constantly sets a variable to the timer. ![]() This block can be displayed as a Stage monitor, though it will only display intervals of 0.1. This block is almost always used with the Reset Timer block - usually the timer must be reset at the beginning of a project for the Timer block to hold the right value. The Timer block is a sensing block that reports the amount of time since the project was loaded or the timer was last reset. For more information on the value this block holds, see Timer (value). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |