by prolixus » Sun Oct 07, 2007 10:00 pm
first we have two options to leads or numbers:
option 1: system uploaded numbers
these numbers are provided by the company for the agents to
call or dial next numbers using manual mode of dialing.
option 2: agent generated number
is also a form of manual dial which our call center requires so
they enter numbers and dial regardless whethere its dnc or not.
I was able to upload the california state do not call (DNC) list which should be blocked by the system (in any case that an agent would be able to dial a number inside that table). from what ive noticed, here is the flow of the vicidial system, from vicidial_list in which leads and numbers are placed, it will passed by the vicidial_hopper for them to be able to dial the numbers, after that when the call needs to be tagged as DNC, the agent will tag it as dnc, from there, that number will be recognized by the system as a dnc number which is blocked already, take note, that number before it was called was clean, meaning it can be dialed, but since it was tagged as dnc, it is now blocked.
Another instance, i have 16M++ dnc numbers, i wanted all those numbers to be recognized by vicidialer that is coming from that table vicidial_dnc, all those numbers will prompt same message as that to the first situation i gave, but my problem, i tried to do back-end uploading of the whole dnc, but all numbers based on my review should be tagged before the pop-up message appears on the side before we have it tagged, we should be able to dial the numbers in which should not be done anymore since they DNC numbers, so how can i solve this challenge in terms of what the movements or flows of calling and tagging and validation to DNC?
here are the suspected tables used when dialing, validating, scrubbing, and recording leads and calls:
call_log
vicidial_agent_log
vicidial_list
vicidial_log
vicidial_dnc
thanks!
Jett from Prolixus