![]() |
Originally Posted by Redbird611
(Post 3657073)
I'm considering putting in a blanket green slip with do not call hours during the evening when I really don't want to be teased, say 2300-0600 for example. I would then have a second green slip at lower priority with auto-accept "Yes" and auto-acknowledge "No", likely with some trip parameter restrictions. I'm thinking that should allow me to look at proffers during the daytime but limit being bothered needlessly at night.
|
Originally Posted by Bucking Bar
(Post 3657050)
Looking forward to NuGuy's input on this. I use the Do Not Call line to blank out the hours my wife sleeps during the school year (say 23:00 to 07:00). I go into great granularity on the overnights, hours, credit, etc for trips that I desire. The variable that I cannot control for is if the company uses ARCOS to cover the rotation. Often ARCOS screws up on acknowledgement where I get skipped because the acknowledgment was not logged or scheduling immediate calls to confirm the acknowledgment and find out "when will you be at the airport."
|
Originally Posted by Bravix
(Post 3657118)
That's a good idea, might have to model something similar. That said, I hate doing greenslips every month. I already have 4 I do (in base, out of base, conflicts for both). Having to put more detail and additional slips in will be annoying. Would be nice if we could build defaults/presets that we could apply every month.
You can. PCS>Standing request qualifiers. Things like layover avoids, etc. It will copy to every GS, causing you to have to delete anything you don’t want to keep. |
Sched Alert 21-06...
Titled "ARCOS Update" explains the Auto-Accept & Auto-Acknowledge Options as well as some Do Not Call (DNC) Between Considerations
|
Sched Alert 21-01
Originally Posted by Bravix
(Post 3657118)
That's a good idea, might have to model something similar. That said, I hate doing greenslips every month. I already have 4 I do (in base, out of base, conflicts for both). Having to put more detail and additional slips in will be annoying. Would be nice if we could build defaults/presets that we could apply every month.
Originally Posted by FangsF15
(Post 3657290)
You can. PCS>Standing request qualifiers. Things like layover avoids, etc. It will copy to every GS, causing you to have to delete anything you don’t want to keep.
|
If there a rule against putting your LEC Reps phone numbers in ARCOS so they get the calls when CS lets the 05:00 - 06:00 trips sit until 2am and then run batch sizes (twice) of 100 so pilot #7 can get the trip?
|
Originally Posted by Bucking Bar
(Post 3657562)
If there a rule against putting your LEC Reps phone numbers in ARCOS so they get the calls when CS lets the 05:00 - 06:00 trips sit until 2am and then run batch sizes (twice) of 100 so pilot #7 can get the trip?
|
If we auto-accept, how long do we have to manually acknowledge before they move on to another pilot in the coverage sequence? If I'm missing something from a notepad or previous post, please berate accordingly with references.
|
Originally Posted by Gunfighter
(Post 3657573)
If we auto-accept, how long do we have to manually acknowledge before they move on to another pilot in the coverage sequence? If I'm missing something from a notepad or previous post, please berate accordingly with references.
" Upon notification of an award, a pilot will have 12 minutes in which to accept the award of the rotation being offered (“award window”). Acceptance of the award may be submitted either via telephone or through the ARCOS application.Note one: For a rotation that is scheduled to report 12 or more hours from the time of notification, a pilot, at their option, may elect to automatically acknowledge the award window notification without the need to take any additional action. A pilot who elects to do so will not be contacted by telephone and will be obligated to fly the rotation if awarded" |
Originally Posted by Tropical
(Post 3657569)
Sounds like harassment.
It is harassment. |
| All times are GMT -8. The time now is 01:33 AM. |
Website Copyright © 2026 MH Sub I, LLC dba Internet Brands