Last week, I asked: “Should WordPress product support be in-house?” And the short version of the conclusion to which I came is simple: Yes. It should be. This still leaves a question about how to handle general WordPress support, though.
Specifically, the problem is when something goes wrong with your product, the general end user doesn’t know if it was your work, the theme, WordPress, or the environment on which all of the software is running.
And if your product is the last thing the user installed, then you’re likely going to be the first person contacted. So let’s say you are running a theme or plugin or WordPress product shop, and your customer has a problem, but it’s not related to the work you’ve done.
In other words, though you do (and arguably should) offer in-house product support, the problem isn’t related to your product at all.
What then?