Page 1 of 1

Contribution - Vicidial Outbound Report v2.0

PostPosted: Sun May 15, 2011 2:47 am
by chrism
Hi All,

I've been a huge fan of open source for many years now and have been using Vicidial for a couple of years. We needed a report that would give the leads that had 'ASETs' but showed the call pattern of how each caller would make calls. I'm just hoping this can help others as much as it has helped us get a better grasp of how our callers are making calls from day-to-day (and even week-to-week).

This is version 2.0 because version 1.0 was used for the last 3 months in-house to be customized to our own needs. Therefore, it has been pretty well tested already. However, any suggestions or contributions are always appreciated.

Screenshot:

Image

>>Link to Download<<

Like to have:

For those of you that like to dabble with the code a bit, you'll notice that I was trying to put in some 'hover' code in the tables to allow more data to be presented to the user on each of the cells. After debugging it for several hours, I couldn't get it to work, so I just commented out the code. I'd love to see if anyone can modify this current report to allow a mouse-over to quickly show statistics for each call directly inside of the table that gives a quick context of what is going on. Perhaps even some unique symbols or something.

Please post any questions or suggestions on this thread. Thanks!

PostPosted: Sun May 15, 2011 8:27 am
by mflorell
Wow, that's pretty cool!

I do have some suggestions if you are open to them:
- Make "ASET" a variable you could configure
- Change $vicidial_url be an optional variable(since you can get the admin path from the system_settings)
- You use standard HTTP authentication, but your comments say cookies are required, and I couldn't find anywhere cookies are being set?
- You should put a copyright notice and an email address for yourself
- I ran against some sample data and got the following two warnings:

Warning: Invalid argument supplied for foreach() in /usr/local/apache2/htdocs/vicidial/vicidial_outbound_report.php on line 692

Warning: Invalid argument supplied for foreach() in /usr/local/apache2/htdocs/vicidial/vicidial_outbound_report.php on line 720


Thanks again for posting this!

thanks

PostPosted: Sun May 15, 2011 12:29 pm
by brett05
can you please explain me the color in call patern ?

PostPosted: Sun May 15, 2011 10:29 pm
by chrism
Under 10 calls = red
between 11 and 20 calls = orange
21+ calls = blue

I'm open for suggestions on alternative implementations. The colors just make it easier to visualize the calls per hour.

PostPosted: Wed May 18, 2011 10:36 am
by KDell
Is it possible to expand this to also show disposition codes per hour? That would rock!

PostPosted: Wed May 18, 2011 4:41 pm
by chrism
Yeah, shouldn't be a problem. Just need some help with the javascript 'hover' code on the cells to provide those kind of details. I haven't really had a chance to dive into it yet.

PostPosted: Thu May 19, 2011 10:11 am
by KDell
This is super awesome! I'm excited to see what this can do fully up and runing!

PostPosted: Thu May 19, 2011 7:16 pm
by chrism
Would love to hear if anyone is using it and able to successfully install.

PostPosted: Fri May 20, 2011 9:48 am
by KDell
We've added it in, it throws up a couple of little errors:

Warning: Invalid argument supplied for foreach() in /var/www/vicidial/vicidial_outbound_report.php on line 692

Warning: Invalid argument supplied for foreach() in /var/www/vicidial/vicidial_outbound_report.php on line 720

PostPosted: Fri May 20, 2011 1:02 pm
by chrism
hrmmm...

Line 692:

Code: Select all
foreach($display_campaigns[$user_key_id]['call_times'] as $call_time){


That is a loop to iterate through all of the call times for that particular user. Do you have a user that did calls, but didn't actually register any?

Hrmm... without actually seeing the error running and having the data to debug it with, I'm not sure what else to say.

PostPosted: Fri May 20, 2011 3:14 pm
by KDell
Could it have anything to do with manual calls or even monitoring? If so, was probably me - otherwise I can do a little research on it tonight - we've got about 65 agents running today.

The error does not show up after selecting variables in the meu at the top - if I select a random user or a new date range, this goes away.