On the Roster Admin page there is a checkbox attribute called Pointer. If this attribute is selected, the roster becomes a pointer list with the being pointer used to determine who is called first on callouts.
Pointer
The Pointer "holds" the place in a callout list where the last callout ended, using a specific list and where the next callout will begin. There are two version of the Pointer method: Last Called Attempted and Last Accepted.
When using the Last Called Pointer Method, a P displays on the Roster List Maintenance page to denote the current location of the pointer. The pointer can be moved to another employee on the Roster List Maintenance page, if required. The Callout Roster Report prints the roster order sequence according to the position of the current pointer.
When a callout occurs, ARCOS begins calling the roster at the last location of the pointer. When the callout is done or stopped, the pointer is adjusted.
Note: On the Roster Maintenance page, the pointer can be moved to another employee by clicking on the Pointer (Ptr) column of the target employee. This means that the pointer can be adjusted if needed. This can only be done for Pointer-based rosters. Click here to view how to reset all pointers for a location.
The Last Called/Attempted Pointer functions as described below.
The pointer moves to the employee after the last employee is called. Assume the Roster contains employees: A, B, C, D, and E.
Example 1: Pointer is assigned to C. When a callout occurs, C is the first employee called (and then D, E, A, B). A callout is initiated and C, D, E, and A are called and A accepts, then when the callout is done, the pointer moves to B.
Example 2: Pointer is assigned to C. A callout is initiated; C and D are called and are not home. E is called and at the same time C calls into inbound. E does not accept and C is then offered the job via inbound. Since C accepted, the callout is filled. The pointer then moves to A since E was the last person called (even though C accepted).
Example 3: Pointer is assigned to C. A callout is initiated; C and D are called and are not home. E is skipped because he is on vacation. A is called and accepts. Since A accepted, the callout is filled. The pointer then moves to B since A was the last person called (even though E was skipped because of vacation). Even if E comes off of vacation 1 minute after the callout is complete, the pointer does not move back to him.
Example 4: Pointer is assigned to C, and A is on vacation. A callout is initiated; C and D are called and are not home. E accepts the callout. Since E accepted, the callout is filled. The pointer then moves to A since E was the last person called. Even though A is on vacation, the pointer is positioned on A because ARCOS does not know what the schedule status of A will be at the next callout. When the next callout occurs, ARCOS begins the callout with A and determines if A is still on vacation.
Note: If an employee is on schedule exception or work exception at the time of the callout and is skipped, the pointer still adjusts past them. That is, if the employee is called or skipped, the pointer still moves. At the end of the callout if the pointer moves to an employee on an exception (working or schedule exception), the pointer remains on that employee and does not move past that employee.
Comments
0 comments
Please sign in to leave a comment.