Redialing nondialable status's

[umop3plsdn]

What would cause a campaign to redial a SALE disposition if it is not defined as a dialable status in the campaign and not set for lead recycling. here's an example:

CALLS TO THIS LEAD:
# DATE/TIME LENGTH STATUS TSR CAMPAIGN LIST LEAD
1 2007-11-01 18:29:02 25 SALE 408 NUWAVE_B 120 17727
2 2007-11-01 18:18:24 4 SALE 408 NUWAVE_B 120 17727
3 2007-11-01 18:14:36 3 SALE 408 NUWAVE_B 120 17727
4 2007-10-31 12:55:46 337 SALE 408 NUWAVE_B 120 17727

RECORDINGS FOR THIS LEAD:
# LEAD DATE/TIME SECONDS RECID FILENAME LOCATION TSR
1 17727 2007-11-01 18:28:59 28 17657 408_NUWAVE_B_20071101-172857_6624348800 408
2 17727 2007-11-01 18:18:20 8 17642 408_NUWAVE_B_20071101-171819_6624348800 408
3 17727 2007-11-01 18:14:32 7 17634 408_NUWAVE_B_20071101-171430_6624348800 408
4 17727 2007-10-31 12:55:48 335 16956 408_NUWAVE_B_20071031-115547_6624348800 408

Also, I noticed when I looked at the lead it was still set as 'A' even though the rep dispositioned it as a sale multiple times. It does not appear in any other lists either.

[umop3plsdn]

Sorry for the false alarm... Ended up being a PBKC error! Silly reps writing down phone numbers on paper and manually dialing them and dispositioning them as a sale repetitively.

[scottgutman]

what is a PBKC error?

[okli]

Problem Between Keyboard & Chair

[scottgutman]

sounds Like an ID 10 T Error. Thanks for the info.

[heinz]

OK - whats an ID 10 T?

@umop3plsdn: I am always dealing with that same thing. Customer complains that he got called multiple times - check the agent_log: oh - manual dial. But it's so easy to prove...

[scottgutman]

ID 10 T = idiot!

i like simplicity.