The One Call per CO Main callout rule prevents ARCOS from calling an employee more than once if his name appears in more than one sub-callout of the main callout, or co main. If an employee is called on one sub-callout of a callout and his name appears on another sub-callout, he is not called a second time. However, if the employee's name appears in another roster in the chain of lists, he will receive another call. In other words, if an employee is called on the first attempt of sub-callout A, he is not called on any attempt of sub-callout B or other subsequent sub-callouts for the given callout, or co main, unless the employee is on another roster in the chain of lists for sub-callout A.
Note: The One Call per CO Main callout rule does not apply to chained lists.
Bypassing the One Call per CO Main
Several companies have taken the One Call per CO Main callout rule a little further with a couple enhancements to better fit their needs. For example, a callout has been setup with two sub-callouts with an employee who appears in both sub-callout A and B. If the employee is called on A and given a result other than Accept or Decline (i.e. Answering Machine) and the sub-callout ends up going to a Stop or Done status, the employee is flagged as wanting to work if he calls Inbound to respond before his name comes up on sub-callout B.
Callout Statuses
Status |
Explanation |
Closed |
A callout that has either been manually closed from the View Open Callouts page or all employees that accepted the callout have been released. Employees calling Inbound will be told there are no pending callouts. |
Delay |
This allows the operator to take some sort of action between chained lists being called. Can also be used during an All Hands on Deck to set time between calling the first and second time, if a second time is needed. Employees calling Inbound in response to this callout will still be offered an open position. |
Done |
The callout stopped running after the requested quantity was filled. |
Edit |
Accessed from the View Open Callouts page, you can perform Rollover, Resubmit, Resume, Edit Quantity, and Stop actions. Employees calling Inbound in response to this callout will still be offered an open position. |
Hold |
A callout is not currently making calls because there are employees who have been skipped because J/A Rule or serial calling has been enabled for the callout. Employees calling Inbound in response to this callout will still be offered an open position.
If Serial Calling is enabled for a callout and the first sub-callout is still making calls, all other sub-callouts will be in Hold status. |
New |
The callout definitions, roster, and quantity were chosen, but the callout was not submitted. This only happens when you get to the Manual Bypass screen but then go to a different page and do not actually submit the callout. |
Pager Delay |
The length of time that ARCOS waits after calling an employee's pager and the next device to be called. |
Paused |
The callout is in a Running status but was manually paused by the operator. Calls will resume again at the same place in the roster when the operator manually un-pauses the callout. Employees calling Inbound in response to this callout will still be offered an open position. |
Pending Pop-up |
Notification, in the form of a pop-up, to the dispatcher or operator that an employee cannot be contacted by ARCOS for a callout has occurred. This may happen when a callout is made for a time in the future for Fill Shift, Travel, or Mutual Aid and the employee, while available for the date and time of the callout, is not currently available to be called. The employee must be called or radioed manually and the results entered manually into the system. |
Pending Run |
The callout has a Run Time selected that is in the future. Once the current time matches the selected Run Time of the callout, the callout will go to Running status. |
Queued |
Another callout is already actively calling the selected roster. The queued callout has to wait until the other callout is finished calling that roster. |
Running |
ARCOS is currently making calls to the selected roster(s). |
Stop |
The callout was stopped by the operator before the requested quantity was filled. This could be before or after the callout reached a Wait status, i.e. went all of the way through the roster. Employees calling Inbound will be told there are no pending callouts. |
Stopping |
An operator has stopped the callout and there are outbound calls in progress. The callout remains in stopping status until all outbound calls have completed. No additional outbound calls are started and employees calling inbound will be told they have no pending callouts. |
Submitted |
ARCOS is in the process of generating the list of people to be called. This status transitions automatically into Running. |
Wait |
All eligible members of the roster were called but the requested quantity was not filled. ARCOS is waiting on the operator to decide whether to resubmit or to stop the callout. Employees calling Inbound in response to this callout will still be offered an open position |
Doing this effectively bypasses the callout rule and the employee is called on sub-callout B. If the employee does not call Inbound before his name is reached on sub-callout B, then he is not called and is given a result of Not Called - Called in Sibling Callout, which is the prime functionality of the One Call per CO Main callout rule.
If an employee is not called on all of his devices, the One Call per CO Main rule does not prevent him from being called on a subsequent sub-callout. An employee with uncalled devices and a "Not Called - Callout ended" call result will be called on a subsequent sub-callout, bypassing the Sibling Callout Rule. However, if an employee has an accept or decline on his first or other device, the remaining uncalled devices will not be called on subsequent sub-callouts. If all of an employee's devices have been called for one sub-callout, he will not be called for subsequent sub-callouts.
Sibling Callout Rule Roster Preference
If you do not want to use the Sibling Callout Rule for your entire company, you can opt to use the Sibling Callout Rule (SibCR) roster preference instead. Click here to learn more about SibCR.
*Note: ARCOS documentation is a living document. For inconsistencies or missing features, contact ARCOS Support. Not all companies have all items in the Online Help.
Comments
0 comments
Please sign in to leave a comment.