Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. DelatCL

    Not Ready Code use per skillset

    Quote by Tontas: "However we are now connecting via ODBC via an access dB and when i pull the view of the not ready reason codes table there is no difference between an Activity code, wrap code or Nr reason code.. E.g it is dependent on what state the agents phone is in when the input the...
  2. DelatCL

    Not Ready Code use per skillset

    Coolicepbx - You are spot on with regards to your idea about different NR codes for each skillset not being pretty. I can understand that it might work in a small enterprise, but on our site we have 11 standard NR codes, and currently 34 running skillsets. I don't fancy having to deal with data...
  3. DelatCL

    Not Ready Code use per skillset

    Wow - Old thread! In the time between posting my first question and now - coming up on two years - I learnt a fair bit, and this may help you out. As far as I can see, the nearest thing Symposium has to an agent wrap state is something called post call processing time, which can be found in...
  4. DelatCL

    Not Ready Code use per skillset

    Damn...can't edit. I do mean not ready codes rather than activity codes. Even now I know what the answer is gonna be, but I had to ask anyway... How is wrap dealt with in your company?
  5. DelatCL

    Not Ready Code use per skillset

    After struggling with this for a while, and believing it to be impossible with the data tables as they are, I was wondering whether anyone had come up with a solution? Is there any way I can work out the amount of time a specific not ready/activity code has been used on calls for a specific...

Part and Inventory Search

Back
Top