Query process
ideas pool
R
Rob K
Would it be possible within the section where you reply to a query (decide if you are changing your score and type up and comments) that you have the option of selecting from a list of categories as to why when a query was overturned it was.
It is usually viewed that when a query is overturned that it is due to the auditor marking the call incorrectly, however there can be numerous reasons as to why the score was changed e.g. new evidence was provided, there had been a change to process or the advisor was given incorrect information from their manager etc. As a result, this means the % edited column within the queries tab on the evaluators performance page can be taken that the auditor was wrong X% of the time unless you go into each query separately to get an understanding of that situation.
What would be great is if these categories could be added so that we could delve into that % edited column to see the make up of that overall score e.g. 25% Error in scoring, 25% Additional information provided and 50% Change in process. Then if one of those categories was of interest, you click on it and it pulls up all the queries that relate to that category.
Finally another feature my team would find very beneficial would be if in the query reporting it showcased the questions that have been queried most frequently and then subsequently changed. This would allow us to identify potential knowledge gaps within our team with regards to questions being marked incorrectly and then fix this to reduce the number of queries being generated to begin with. It would also be great that if the query categories could be implemented, that it would link into this request too so that questions scored incorrectly could be specifically targeted.
I have already spoken all the above through with Reg at Evaluagent and he has suggested highlighting my request here to gauge the appetite of the wider Evaluagent audience.
Hope this all makes sense, feel free to get in touch if you want me to elaborate on anything
Jon (Product Manager @Evaluagent)
added to product backlog
Jon (Product Manager @Evaluagent)
good idea
Jon (Product Manager @Evaluagent)
under consideration
James (Software Developer @ EvaluAgent)
backlog
Jon (Product Manager @Evaluagent)
planned
Added to our product backlog for development in the near future. No timelines or delivery dates set yet
R
Rob K
Hi James, if I could add to one of the points I have raised in the above post (paragraph 3) on the ability to categorise why a query was over turned. Could we please ensure that if a query has more than one line item being queried that we have the ability to categorise each of the line items as one could be overturned to to an error in scoring but the other could be for another reason like the manager provided the advisor with incorrect information. For this to work I think we would also need to be able to report on number of queries received and also number of line items queried too as you could have a query with 2 line items queried and 1 was overturned but the other wasn't.
R
Rob K
Hey James,
Has it been confirmed if this suggestion is moving forward?
Thanks
James (Software Developer @ EvaluAgent)
Rob K: Hello Rob,
I'm hoping to be able to update you in the coming week. We're all hands to the pump on a major project at the moment that has put some delay into our Canny work, but we've recently expanded team that builds Canny request from yours truly to three of us!
James (Software Developer @ EvaluAgent)
Rob K: As an aside, this kind of submission is going to be highlighted in a blog post about how we're approaching user suggestions going forward as a 'best practice' in terms of detail provided by the user.
James (Software Developer @ EvaluAgent)
initial review
Hello all,
I think we may be moving this idea forward. I will confirm tomorrow!
C
Claire M
This is exactly the type of insight needed when changing decisions, in our business this data is currently held in a separate log.
N
Nydia J
Great idea.
Load More
→