called_count & maximum dial attempts
Posted: Thu Oct 07, 2010 6:21 pm
My understanding of how vicidial operates is that a list is created, leads are added to this list and all leads are dialed until the list has been called through. If you want to dial the leads a second time the list needs to then be reset.
According to the manuals it states that in lead recycling only Busy status should be used in here. It seems this is so it will call busy numbers over and over even though the list has not been reset manually.
Resetting the list changes the leads called_since_last_reset back to 'N' and when recycled leads are dialed we find Y1, Y2, Y3....
vicidial_list.called_count field appears to only be referenced a few times in the source and the main function of this appears to be with the ordering of the leads UP or DOWN the list based on their called_count desc or asc.
---------------
Is there a max attempts setting per campaign? So that even if the list is reset it checks the called_count so that a lead hitting MAX_ATTEMPTS calls will be given a final status such as NO CONTACT and the lead will then die?
We are trying to maintain lists that will have real time leads inserted into the vicidial_list table directly and then sucked into the hopper based on filter criteria. We then want to dial those leads up to MAX_ATTEMPTS no matter what the disposition is other than a final status like SALE or NOT INTERESTRED without manual intervention of resetting the list.
In order to do this now it appears that we will have to run a job/script every number of minutes that will check called_count and force a status on leads where called_count >= 6 and reset called_since_last_reset back to 'N'. With this script running we will add all statuses like answering machines, busy, no answers, and everything else into lead recycle so that the leads will be pulled in and dialed based on recycle rules and the leads last call status and we will continue to call until called_count >= 6 which will take a higher priority than called_since_last_reset field.
TL;DR - Is there a MAX_ATTEMPTS setting for dialing leads by campaign?
Thanks!
According to the manuals it states that in lead recycling only Busy status should be used in here. It seems this is so it will call busy numbers over and over even though the list has not been reset manually.
Resetting the list changes the leads called_since_last_reset back to 'N' and when recycled leads are dialed we find Y1, Y2, Y3....
vicidial_list.called_count field appears to only be referenced a few times in the source and the main function of this appears to be with the ordering of the leads UP or DOWN the list based on their called_count desc or asc.
---------------
Is there a max attempts setting per campaign? So that even if the list is reset it checks the called_count so that a lead hitting MAX_ATTEMPTS calls will be given a final status such as NO CONTACT and the lead will then die?
We are trying to maintain lists that will have real time leads inserted into the vicidial_list table directly and then sucked into the hopper based on filter criteria. We then want to dial those leads up to MAX_ATTEMPTS no matter what the disposition is other than a final status like SALE or NOT INTERESTRED without manual intervention of resetting the list.
In order to do this now it appears that we will have to run a job/script every number of minutes that will check called_count and force a status on leads where called_count >= 6 and reset called_since_last_reset back to 'N'. With this script running we will add all statuses like answering machines, busy, no answers, and everything else into lead recycle so that the leads will be pulled in and dialed based on recycle rules and the leads last call status and we will continue to call until called_count >= 6 which will take a higher priority than called_since_last_reset field.
TL;DR - Is there a MAX_ATTEMPTS setting for dialing leads by campaign?
Thanks!