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.
Redialing nondialable status's
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
7 posts
• Page 1 of 1
Redialing nondialable status's
by umop3plsdn » Thu Nov 01, 2007 6:01 pm
- umop3plsdn
- Posts: 72
- Joined: Wed Jul 26, 2006 9:47 am
- Location: Maine
by umop3plsdn » Thu Nov 01, 2007 7:40 pm
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.
- umop3plsdn
- Posts: 72
- Joined: Wed Jul 26, 2006 9:47 am
- Location: Maine
by scottgutman » Fri Sep 11, 2009 11:48 am
what is a PBKC error?
Dialer-Vicidial 2.2.0-250_100116-0709, Asterisk 1.4.21.2, Intel Quad Q6600 2.4G x64/8G Ram
Web-Apache/2.2.3, PHP 5.2.10, eAccelerator v0.9.5.2, AMD 9950 Quad 2.6G x64/4G Ram
DB-MySQL 5.0.45, 2xAMD 2.6G i386/4G Ram
OS-CentOS 5.3-2.6.18-128.1.16.el5
Web-Apache/2.2.3, PHP 5.2.10, eAccelerator v0.9.5.2, AMD 9950 Quad 2.6G x64/4G Ram
DB-MySQL 5.0.45, 2xAMD 2.6G i386/4G Ram
OS-CentOS 5.3-2.6.18-128.1.16.el5
- scottgutman
- Posts: 75
- Joined: Mon Mar 23, 2009 4:17 pm
by scottgutman » Wed Sep 16, 2009 3:52 pm
sounds Like an ID 10 T Error. Thanks for the info.
Dialer-Vicidial 2.2.0-250_100116-0709, Asterisk 1.4.21.2, Intel Quad Q6600 2.4G x64/8G Ram
Web-Apache/2.2.3, PHP 5.2.10, eAccelerator v0.9.5.2, AMD 9950 Quad 2.6G x64/4G Ram
DB-MySQL 5.0.45, 2xAMD 2.6G i386/4G Ram
OS-CentOS 5.3-2.6.18-128.1.16.el5
Web-Apache/2.2.3, PHP 5.2.10, eAccelerator v0.9.5.2, AMD 9950 Quad 2.6G x64/4G Ram
DB-MySQL 5.0.45, 2xAMD 2.6G i386/4G Ram
OS-CentOS 5.3-2.6.18-128.1.16.el5
- scottgutman
- Posts: 75
- Joined: Mon Mar 23, 2009 4:17 pm
by heinz » Thu Sep 17, 2009 9:25 am
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...
@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...
- heinz
- Posts: 106
- Joined: Mon Oct 08, 2007 1:30 am
- Location: South Africa
by scottgutman » Thu Sep 17, 2009 5:45 pm
ID 10 T = idiot!
i like simplicity.
i like simplicity.
Dialer-Vicidial 2.2.0-250_100116-0709, Asterisk 1.4.21.2, Intel Quad Q6600 2.4G x64/8G Ram
Web-Apache/2.2.3, PHP 5.2.10, eAccelerator v0.9.5.2, AMD 9950 Quad 2.6G x64/4G Ram
DB-MySQL 5.0.45, 2xAMD 2.6G i386/4G Ram
OS-CentOS 5.3-2.6.18-128.1.16.el5
Web-Apache/2.2.3, PHP 5.2.10, eAccelerator v0.9.5.2, AMD 9950 Quad 2.6G x64/4G Ram
DB-MySQL 5.0.45, 2xAMD 2.6G i386/4G Ram
OS-CentOS 5.3-2.6.18-128.1.16.el5
- scottgutman
- Posts: 75
- Joined: Mon Mar 23, 2009 4:17 pm
7 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 88 guests