![]() # This script limits the number of altered leads to 1 per instance and it will # This script is part of the API group and any modifications of data are # which contain the statuses for which the process should be run. # sale_status field is a list of statuses separated by three dashes each '-' # in order to change it's list_id to whatever new_list_id is set to. # It should take in the lead_id to check for the same lead_id # or in-group (although it can also be used in the "No Agent Call URL" field). # This script is designed to be used in the "Dispo URL" field of a campaign There is already a Dispo Call URL script (dispo_move_list.php) that can move a lead based on it's called count If you need any extra info please let me know. Here is a link to the output of AST_ -debugXĪny input or a direction to look would be more than helpful. However I don't know if any of that is what is making us go over the max. We are also using the state dial restrictions. Auto Hopper level is set, with a minimum of 500 and a multiplier of 1, auto trim hopper is also enabled. We are using list order of random, with List Order Randomize turned on. Reading through other posts about the Call Count Limit, I have disabled all the lead recycling. Currently it is set at a limit of 12, however I've seen many in the hopper with a call count way over the limit at times. So here is what is up, we are trying to utilize the fancy new Call Count Limit feature. ViciBox Redux v.3.1.15 release | Vicidial 2.4-360a BUILD: 120221-0054 | Asterisk 1.4.38-vici | 3 Server Cluster 1 Dialer, 1 Web, 1 Database All ViciBox 3.1.15 | No Digium/Sangoma Hardware | No Extra Software After Installation Sadly I come to you today with a problem. You guys have made my life sooooo much easier. First off I want to thank everyone who has put time into ViciDial. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |