Home     Contact Us    
Main Board Job Seeker's Board Job Wanted Board Resume Bank Company Board Word Help M*Modal Nuance New MTs Classifieds Offshore Concerns VR/Speech Recognition Tech Help Coding/Medical Billing
Gab Board Politics Comedy Stop Games Faith Board Prayer Requests Health Issues

ADVERTISEMENT



Company Board Today's Top Viewed: Knee surgery help needed.. (Views: 38)

timed - Grandy

Posted: Mar 14th, 2019 - 8:57 am In Reply to: Timed - Peaceout

So, according to you, it is okay for a transcription to be "checking in" 24/7, in order to find 8 hours of work? Yeah, that is working out great for Proscript transcriptionists, especially when they have to deal with QA picking at every "the, an, a, um, nose snort, throat clear, etc., when they hear one thing and the corrupt QA staff claim to hear something else. They cannot re-listen to what they typed to see if they or the corrupt QA staff is correct, because they are not allowed to re-listen. Someone in "management" is always willing to "re-listen" for them, though, and always claim that the QA staff was right. Furthermore, these are NOT critical errors, they are nitpicking used to force transcriptionists to quit or to terminate them for "unacceptable QA scores." All this while transcriptionists have to re-type a large percentage "VR" lines, even for good dictators, because the Proscript system keep producing things that were not dictated, incorrect, misspelled, etc. It is a great way for transcriptionists to earn money, NOT, not unless you are the "in favor" who are assigned the best dictators and all the "template" reports. Proscript is as crooked as they come. Again, check the archives, there are few people who have anything decent to say about that company, except, of course, when Proscript management, like you, chime in. Tell me exactly why you believe it is acceptable for Proscript QA to nitpick and change QA score to faile transcriptionists.


ADVERTISEMENT


Post A Reply Reply By Email Options


Complete Discussion Below: ( marks the location of current message within thread)