Already Offered Vacancy

Definition: This rule is used to stop candidates from being contacted based on given criteria. Returns people with a True or False value. True means the person has been extended an offer for the target position.

Return value: Values of type Boolean

Source: Contact Log

Pick List: This base rule affects the Pick List if it runs with For this %Position% = NO; otherwise, no impact.

From: This field is required if Timeframe too = YES. It defines the start of the time frame in which to look for previous offers.

Through: This field is required if Timeframe too = YES. It defines the end of the time frame in which to look for previous offers.

Sorting: If this base rule is used for sorting in a List Target or a List, then people with a True return value are preferred (sorted to the top) if the sort is ascending; otherwise, they are pushed behind the other candidates in a descending sort.

Arguments Value
For this location Controls whether or not this base rule can act on offers for this specific location.
  • YES- stops future offers for this position (default), but if Station is selected then this stops future offers for the target station - including nested units and positions for that station. (Note: This is generally true, but outcome also depends on whether the other arguments allow it, see Ignores Offer if argument on this table). For example, suppose you have position A and position B, where A and B are the same job title. Both positions start at 8AM, and run for 24 hours on Station 1 > Unit 1. Suppose the system offers you position A, and you reject the position, if YES is selected you will not be offered position A again using this base rule and List. If set to NO, you will be offered this position again if available. If set to Unit, you will not be offered position A or B.
  • NO - previous offer for any position.
Strategy %gray number% Controls which List to evaluate. This base rule returns a specific List, or any list.
  • <NOTHING>- blank means do not limit by List (strategy).
  • <INTEGER> - previous offer from a specific List (strategy) identified by its Unique Identifier.
  • 0- previous offer from the List (strategy) that this rule is attached to.

For example, suppose Already Offered Vacancy X is attached to the Volunteer List, and the Call Everyone List in the Hire List Chain. Both Lists contain a zero in the Strategy. Suppose the system calls Bob, offers position A using the Volunteer List, and he rejects the offer. The Call Everyone List then calls Bob, and he rejects it. If no one accepts the offer Bob will be called again using the Volunteer List, and if no one accepts the offer Bob will be called again using the Call Everyone List and as you can see you’re in a call loop because the Volunteer List doesn’t see the last rejection in the Call Everyone List (last list). Reason being, the Volunteer List is set to zero meaning self. To prevent this call loop use two separate rules, one rule looks at rejections to gray number zero, and set the other rule to blank so it looks at any rejections.

Timeframe too? Defines whether this rule should act on offers based on the same timeframe as the last offer it has results for.
  • YES- previous offer during the time frame specified by the From or Through fields. For example, suppose position A and position B both start at 8AM and run for 24 hours on Unit 1. The system offers Bob position A and he rejects the offer, this means Bob will not be offered position B.
  • NO - do not limit by time frame.
Ignore offers if Defines which specific results to act on, and which to ignore - meaning ignore offers for the target person if the following result is met.
  • ALL - ignore all offers. This option only makes sense if the base rule is qualified by position, list, or time frame.
  • ACCEPTED- ignore only the offers that have been accepted.
  • REJECTED - ignore only the offers that have been rejected. For example, suppose the target List contains the Already Offered Vacancy rule and Ignore offer if is set to REJECTED. This target list offers Bob position A on Unit 1, and he rejects the offer for position A. If no one accepts the offer, the system will offer position A to Bob again because the rule is set to ignore REJECTED results.
  • REMOVED- ignore only the offers that were staffed and then removed.
  • ALT-ACCEPTED - used with multiple offers. Ignore other offers that were accepted by someone else.
  • ALT-REJECTED- Ignore other offers that were rejected by the person in a multiple offers scenario. This could also mean the person accepted a position other than the target position being filled. For example, suppose the system calls and offers Bob position A, and he rejects position A. Then the system calls Bob again, and offers position B. Bob does not answer the call. The system will record this as ALT-REJECTED in the Contact Log for position B - because Bob accepted or rejected another offer.
  • OFFERED AGAIN- ignore only the offers identified as ‘Offered Again’ in the Contact Log.
  • STANDARD ERRORS - ignore standard dialing errors such as Busy, Operator Error, No Ring...
Unexpired Only This argument stops an offer based on whether or not the target person has offers in their queue.
  • YES - consider only offers that have not expired, yet. This option is used if For this %Position% indicates No.
  • NO - consider all offers. This option is commonly selected if For this %Position% indicates Yes.

For example, suppose the system could offer Bob position A and position B in this order. The system first offers Bob position A with a reserved period. If Unexpired Only is set to No, then Bob can receive the position B offer during position A’s reserve period. If Unexpired Only is set to Yes, then Bob will not receive an offer for position B because the reserved period for position A has not expired.