I know that CitrusDB currently has some kind of open/closed call feature. However I am not sure if I am using it well.
We are a small ISP using your project for our Customer Database. We chose it mostly because it supported call history with customer accounts, and easy to modify the interface without altering the php code. Your database upgrades from 1.0 read in our custom made service package tables just fine. It is also helpful that it can email a call, much like a ticket. Do you believe a trouble ticket style system will start to appear in the project? Currently we use a separate ticket system for this task. Having a single application such as CitrusDB containing our call history, and a separate program for call Ticket history, has always been a challenge that we have never managed to bring together into a common application. (free one at least). So for now, our Call Center just does a copy and paste from the history at the ticket program into the customer history in CitrusDB. This puts the call logs in a common place for our on the road techs and managers to monitor. Rather a headache but it works. Do you have any suggestions for thoughts? -Kreg ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Citrusdb-users mailing list Citrusdb-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/citrusdb-users
