Attn: PCGS_Hy - #146768 Kangaroo Metal Content
oldsmagnet
Posts: 205 ✭✭✭
@PCGS_Hy -- in response to your prior email on this subject. It's no longer possible to respond to the "if you have questions or concerns, please let me know" -- My options are taking a chance on you seeing this here, or dumping it into the "contact us" cesspool link with dwindling hopes that someone will read it within the next five years.
Your solution of disabling the 146768 slot has successfully removed all the cupro-nickel coins from the silver registries. Unfortunately it's also removed the silver coins. Various PCGS and Set Registry officials have been made aware of this for many months now, and this is the first form of action apparently taken.
I've found another user with 887880/43173202, a silver version, with a total population of one. I'm running out of time to delay my next submission, so in the absence of further clarification, that's the spec I'll use when submitting the next batch, with an assumption that all silver variants of 146768 should be reholdered into the 887880 specs, and the 146768's official description changed to Cupro-Nickel. Ideally it would be possible, on the database side, to electronically reclassify the silver 146768s as 887880s until all owners can physically return their slabs. For as long as it took to fix the broken "report a cert", I understand that may be more easily said than done. Regardless, it seems obvious that a fix to this problem won't be in place by the June awards cutoff.
Comments
Hello oldsmagnet,
I apologize that I was not able to respond to you right away. Your case is still open with me and you can reply to the email at any time if you wish to get any updates or want to add any additional information.
It should not be giving you an auto reply stating it is not a monitored email. If it is, this will be fixed. I apologize for any confusion.
I will follow up with you in the email chain shortly.
Best,
PCGS_Hy
PCGS Customer Care Representative
Need Assistance?
Visit our Help & Support page.
Just in case anyone happened to jump in to follow along, this issue has been corrected - thank you to all involved