Version 5.1.1 Redial

Human dial attempts with RA (Remaining Attempts) greater than 1 will force a complete pass before allowing a second attempt. This includes all locked records.

For center databack upload records that are non-callable, they are marked as "processed" to prevent them from being pulled for SMS sending or loading into the dialer.

When redial targets are reached, all human dialed queues with the same target records that are available to dial are marked as "target locked".

When enabling a queue target goal, the target locks are re-calculated on that queue.

When changing goal target values, the target locks on all human queues are re-calculated.

For redial on predictive projects:

  1. Records that have passed the redial delay, have been called, have less than the total allowed attempts, are downloaded=1 (processed), and have a callable code, are moved to downloaded=0 (available).
  2. Records that are downloaded=0 (available) will be loaded into the dialer in attempt order, with the least attempts first.

For redial on human projects:

  1. The queue's current attempt count is set to 1 to start.
  2. Records that are downloaded=0 (available) are allowed to be human dialed.
  3. Records that have passed the redial delay, have been called, have less than the queue's current attempt, are downloaded=1 (processed), and have a callable code, are moved to downloaded=0 (available).
  4. When human dial reaches no available records, it will find the max attempts and set the current attempt to max+1.

The downloaded record codes are:
DOWNLOADED_AVAILABLE = 0
DOWNLOADED_PROCESSED = 1
DOWNLOADED_AGENT_LOCK = 2
DOWNLOADED_IN_DIALER = 3
DOWNLOADED_TARGET_LOCKOUT = 5