Indeed you should be recording them in the system and in case its not practiced then its good to start off.
In my past was part of a product team and we were on the beta release of a new product and at times we occasionally found bugs which at that point we used to note them down and mailed to the respective persons handling the modules (we had a bug tracking system but didn't think of pushing them there). Later on when days went by the items in the mail started to get ignored because of other priorities and that eventually lead to some sleepless nights.
Then bang one day Nirvana ! why are we not using the bug tracker, even if you found something which seems like a bug and could be possible that it ain't one(your thought about the process is wrong/flawed) it atleast makes up on the list which could then be tested and most important of all a feedback as to why its critical or on the flip side it is perfect and thats how it should work coz of reasons 1... 2....
Now you have the list and also for those have misunderstood some parts of the application they have the feedback based on which they can clarify their thoughts. A win win situation.