NO ERROR MESSAGE WHEN REQUESTING ORDINANCES HURTS SYSTEM EFFECTIVENESS
Should there be a possible duplicate (or other issues) when an ordinance is requested, the REQUEST button simply does not go active. The user is left to wonder what the problem might be - is it FamilySearch, is it my computer, is it the browser, is something wrong with the record, etc. etc. The suggestion is that adding some sort of notification about the possible nature of the problem will help improve the process of bringing our forebears to the Temple.
Case 07868473 is a bit long but contains a screenshot of the problem (which is that the REQUEST button at the bottom is blank, with no explanation; cause in this Case is that a possible duplicate existed).