Not everything can be answered with a predefined reply. It’s easy to leave a bad reply, and it’s often difficult to find the right language to explain a technical problem in non-technical terms, which applies both to those asking questions on the forum and those offering solutions. Take a moment to understand the real issues, including any underlying ones, and respond accordingly.
Understanding the issue a user faces is only part of the fix and of the interaction. Get to know how technical the user is. Is he/she a new or experienced user?
The thing is everybody is welcome to the forum and often enough we can help them all but in order to do this as fast as possible and as least frustrating as possible it is a good idea to know the technical level of an user and he’s/she’s willingness to add/edit code. This way you won’t lose time writing lines of codeLines of CodeLines of code. This is sometimes used as a poor metric for developer productivity, but can also have other uses. to an user that won’t use them.