. First of all, we need to understand the user's motivations. We shouldn’t immediately label him as a liar, even if we are sure that his story is implausible. Sometimes it is enough for a user to experience emotions to believe that he is right (and yes, it's not rational) (, ).
. By immediately stating that the user’s claims are inconsistent, we don’t let the user save his face. We cannot be sure of his motives. Perhaps he simply forgot or misinterpreted something. Thus, all our arguments should be given in stages, with the control of the user's reaction.
. In some cases, the user can tell a non-existent story simply to hide his total incompetence (or the fact of his mistake). Starting with bland “the system itself deleted the file, I never did it,” continuing with many others.
. In cases where the user realizes his mistake, we shouldn’t let him lose his face by offering a placebo in the form of "we will register this incident and conduct appropriate checks." If such problems occur often, we can provide users with some form/button/email address for feedback ().
. Perhaps in our communication, we used stressful wording, which led to the user's anxiety and contacting us.
. The story of our user may be a continuation of some negative episode that happened to him earlier.
. We shouldn't tell the user that the problem is in their thought processes.
#47.What should we keep in mind when reaching out to a user directly?
#51.What causes users to make mistakes when using our product?
#10.Why do users complain about the quality of our support?
#31.How to protect yourself from fake news (or other information warfare)
#38.What to consider when creating moderation/arbitrage features?
#44.What to consider when working with user feedback?